Beacon GoM — Gulf of Mexico Safety Intelligence

Queries the Bureau of Safety and Environmental Enforcement's public incident database using a schema-based search interface that accepts operator name, geographic area (e.g., Vermilion, Green Canyon), and ISO 8601 date ranges as filter parameters. Returns structured incident records including incident type classification, injury count, fatality count, and precise geographic coordinates. The MCP server translates natural language filter requests into parameterized queries against BSEE's REST API, normalizing operator names and area codes to match official taxonomy.

Aggregates all historical BSEE incident records for a specified operator and computes summary statistics: total incident count, cumulative injury count, cumulative fatality count, violation count, and active platform count. The server performs server-side aggregation across the entire BSEE dataset for the operator, returning a single summary object rather than requiring the client to fetch and aggregate individual incident records. This enables rapid safety scorecard generation without pagination or client-side computation.

Retrieves the most recent BSEE incident records across all Gulf of Mexico operators, sorted by incident date in descending order. Accepts two parameters: a configurable time window (e.g., 'last 7 days', 'last 30 days') and a result limit (e.g., 'top 10', 'top 100'). The server queries BSEE's incident database, filters by date, and returns a paginated or truncated result set. Useful for monitoring real-time safety trends and identifying emerging incident patterns without specifying a particular operator.

Exposes three BSEE query functions (incident search, operator summary, recent incidents) as MCP tools that can be called by LLM agents and client applications via the Model Context Protocol. Each tool is defined with a JSON schema specifying input parameters (operator name, area, date range, time window, result limit) and output structure. The MCP server translates tool calls into HTTP requests to the BSEE API, handles authentication (none required for public data), and returns results in a standardized JSON format. Enables natural language queries like 'How many incidents has Shell had?' to be automatically routed to the appropriate BSEE tool.

Normalizes raw BSEE incident and operator data into a consistent JSON schema with standardized field names, data types, and enumerations. Maps BSEE's internal incident type codes (e.g., 'INJ', 'FAT', 'ENV') to human-readable labels, normalizes operator names to match the official BSEE operator registry, and converts geographic area codes to canonical region names. Handles missing or null values gracefully, returning sensible defaults (e.g., 0 for injury count if not reported). This abstraction shields clients from BSEE's raw data format variations and inconsistencies.

Parses raw BSEE incident records returned from the API and normalizes them into a consistent JSON schema with standardized field names, data types, and value enumerations. Handles variations in BSEE's data format (e.g., date formats, incident type classifications, geographic area codes) and ensures all incident records conform to the same structure regardless of source or age. Implements schema validation to catch malformed or incomplete records before returning them to clients.