smithery Safe content atomic mcp-remote

Beacon GoM — Gulf of Mexico Safety Intelligence

Query BSEE offshore safety data for Gulf of Mexico oil and gas operations. Search incidents by operator, area, and date range. Get operator safety summaries including incident counts, injuries, fatalities, and violations. Access raw public data from the Bureau of Safety and Environmental Enforcement (BSEE). Built by AiGNITE Consulting LLC, Houston, TX. Category: Data & Analytics / Energy / Compliance Endpoint: https://publicmcp.beacongom.com/sse Auth: None required (public tools) Tools: ToolDescription public_search_incidentsSearch BSEE incident records by operator, area, date range. Returns incident type, injuries, fatalities, location. public_get_operator_summaryGet total incidents, injuries, fatalities, violations, and active platform count for any Gulf of Mexico operator.public_list_recent_incidentsList the most recent BSEE incidents across all operators. Configurable time window and result limit. Example queries: "How many incidents has Shell had in the Gulf of Mexico?" "Show me recent offshore safety incidents" "Search for BP incidents in the Vermilion area" "What's the safety record for Murphy Exploration?" Website: https://aigniteconsulting.ai

Cognium trust score

50%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: data-analytics
Source: Smithery
Author type: human
Updated: 2026-05-13

View source Find related skills

MCP

Resolve Beacon GoM — Gulf of Mexico Safety Intelligence from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"