{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_aigniteconsulting-beacon-gom","slug":"aigniteconsulting-beacon-gom","name":"Beacon GoM — Gulf of Mexico Safety Intelligence","type":"mcp","url":"https://smithery.ai/servers/aigniteconsulting/beacon-gom","page_url":"https://unfragile.ai/aigniteconsulting-beacon-gom","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:aigniteconsulting/beacon-gom"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_aigniteconsulting-beacon-gom__cap_0","uri":"capability://search.retrieval.bsee.incident.record.search.with.multi.dimensional.filtering","name":"bsee incident record search with multi-dimensional filtering","description":"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.","intents":["Find all incidents for a specific operator across a date range to assess historical safety performance","Identify incident clusters in a geographic area to understand regional risk patterns","Retrieve raw incident details (type, severity, location) for compliance audits or safety reviews","Compare incident frequency across multiple operators in the same area"],"best_for":["Compliance officers and safety managers at oil & gas companies conducting internal audits","Insurance underwriters assessing operational risk for offshore platforms","Regulatory analysts at BSEE or state agencies monitoring industry safety trends","Environmental consultants building safety case studies for project proposals"],"limitations":["Search limited to public BSEE records only — does not include proprietary incident data or unreported near-misses","Geographic filtering uses BSEE area codes (e.g., 'Vermilion', 'Green Canyon') which may not align with operator-internal naming conventions","Date range queries may have latency >2s for multi-year searches across all operators due to BSEE API response times","No full-text search on incident descriptions — filtering is by structured fields only (operator, area, date)"],"requires":["MCP client compatible with SSE endpoint (Server-Sent Events)","Network access to https://publicmcp.beacongom.com/sse","No API key required (public data source)"],"input_types":["text (operator name, e.g., 'Shell', 'BP')","text (area code, e.g., 'Vermilion', 'Green Canyon')","ISO 8601 date strings (YYYY-MM-DD format for range start/end)"],"output_types":["JSON array of incident objects","Structured fields: incident_id, operator, area, incident_type, date, injuries, fatalities, location_coordinates"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aigniteconsulting-beacon-gom__cap_1","uri":"capability://data.processing.analysis.operator.safety.profile.aggregation.and.summary.generation","name":"operator safety profile aggregation and summary generation","description":"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.","intents":["Generate a one-page safety summary for an operator to include in a compliance report or board presentation","Compare safety metrics (incidents per platform, injury rate) across multiple operators to identify industry leaders vs laggards","Assess whether an operator's safety record meets threshold criteria for insurance underwriting or contract qualification","Track an operator's safety trend over time by querying summaries at different date snapshots"],"best_for":["Safety managers and compliance officers needing quick operator scorecards for internal or external reporting","Insurance underwriters and brokers evaluating operational risk for premium setting","Procurement teams vetting contractor safety credentials before awarding offshore contracts","Regulatory bodies monitoring industry-wide safety performance and identifying repeat violators"],"limitations":["Summary statistics are cumulative across all time — no built-in time-windowing (e.g., 'incidents in last 2 years') without additional filtering logic","Violation count may include resolved/closed violations, not distinguishing active vs historical compliance status","Active platform count is a point-in-time snapshot and may lag actual operational changes by days or weeks","Does not normalize by platform count or operational hours, so raw incident counts may not reflect true safety rate"],"requires":["MCP client compatible with SSE endpoint","Network access to https://publicmcp.beacongom.com/sse","Operator name must match BSEE's official operator registry (e.g., 'Shell Offshore Inc.' vs 'Shell')"],"input_types":["text (operator name, case-insensitive)"],"output_types":["JSON object with fields: operator_name, total_incidents, total_injuries, total_fatalities, violation_count, active_platform_count"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aigniteconsulting-beacon-gom__cap_2","uri":"capability://search.retrieval.recent.incident.feed.with.configurable.time.window.and.result.limit","name":"recent incident feed with configurable time window and result limit","description":"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.","intents":["Monitor recent offshore incidents across the entire Gulf of Mexico to stay informed of industry safety events","Build a real-time safety news feed or dashboard showing the latest incidents by date","Identify emerging incident types or geographic hotspots by analyzing the most recent incident cluster","Set up alerts or notifications when new incidents are reported in a specific area or by a specific operator type"],"best_for":["Safety analysts and compliance officers who need to stay current on industry incidents","Dashboard and reporting tool builders integrating live BSEE data into internal systems","Risk management teams monitoring operational changes and emerging safety concerns","Media and research organizations tracking offshore safety trends for reporting or academic analysis"],"limitations":["BSEE incident reporting has a lag of 1-7 days, so 'recent' incidents may not reflect incidents that occurred today","Result limit is a hard cap — no pagination support, so querying 'top 1000' may timeout or be rejected by the server","Time window is relative (e.g., 'last 7 days') and does not support absolute date ranges; use the incident search capability for precise date filtering","Does not distinguish between incident severity or type in the feed — all incidents are weighted equally regardless of fatality or injury count"],"requires":["MCP client compatible with SSE endpoint","Network access to https://publicmcp.beacongom.com/sse","Time window parameter must be in a supported format (e.g., '7d', '30d', '90d')"],"input_types":["text (time window, e.g., '7 days', '30 days', '90 days')","integer (result limit, e.g., 10, 50, 100)"],"output_types":["JSON array of incident objects, sorted by date descending","Structured fields: incident_id, operator, area, incident_type, date, injuries, fatalities, location_coordinates"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aigniteconsulting-beacon-gom__cap_3","uri":"capability://tool.use.integration.mcp.tool.calling.interface.for.bsee.data.access","name":"mcp tool-calling interface for bsee data access","description":"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.","intents":["Enable LLM agents to autonomously query BSEE data without manual API integration or custom code","Build conversational interfaces where users ask natural language questions about offshore safety and get real-time answers","Integrate BSEE data into multi-step workflows (e.g., 'fetch operator summary, then search for recent incidents in that area')","Allow non-technical users to query safety data through a chat interface without learning BSEE's API or portal"],"best_for":["LLM application developers building agents that need to access real-time safety data","Teams building conversational safety dashboards or chatbots for compliance teams","Workflow automation platforms (e.g., Zapier, Make) that want to add BSEE data as a data source","Enterprise systems integrating offshore safety data into broader compliance or risk management platforms"],"limitations":["MCP is a text-based protocol with SSE transport — not optimized for high-frequency polling or real-time streaming of incident updates","Tool schemas are fixed and cannot be dynamically extended by clients — adding new query types requires server-side changes","No built-in caching or rate limiting — high-volume queries may hit BSEE API rate limits or incur latency","LLM agents may misinterpret tool outputs or construct malformed queries if prompt engineering is poor"],"requires":["MCP client library (e.g., Claude SDK, Anthropic MCP client, or compatible third-party implementation)","SSE support in the client (most modern HTTP clients support this)","Network access to https://publicmcp.beacongom.com/sse","LLM model capable of function calling (e.g., Claude 3, GPT-4, Llama 2 with tool-calling fine-tuning)"],"input_types":["MCP tool call with JSON parameters (operator, area, date_start, date_end, time_window, limit)"],"output_types":["JSON tool result containing incident records or operator summary","Structured error messages if query parameters are invalid or BSEE API returns an error"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aigniteconsulting-beacon-gom__cap_4","uri":"capability://data.processing.analysis.public.bsee.data.normalization.and.schema.mapping","name":"public bsee data normalization and schema mapping","description":"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.","intents":["Consume BSEE data in a consistent, predictable format without parsing or cleaning raw API responses","Build reports and dashboards that display human-readable incident types and operator names instead of cryptic codes","Integrate BSEE data with downstream systems (databases, analytics platforms) that expect standardized schemas","Handle edge cases (missing data, name variations) automatically without client-side error handling"],"best_for":["Application developers building tools on top of BSEE data who want a clean, normalized interface","Data engineers building ETL pipelines that ingest BSEE data into data warehouses","Business analysts and report builders who need human-readable data without technical data cleaning","Teams integrating BSEE data with multiple downstream systems that expect consistent schemas"],"limitations":["Normalization may lose granularity — e.g., mapping incident codes to broad categories may obscure subtle incident type distinctions","Operator name normalization relies on a static registry that may lag actual operator name changes or mergers","Default values for missing data (e.g., 0 injuries) may mask data quality issues or incomplete reporting","Schema is fixed and cannot be customized per client — all clients receive the same normalized format"],"requires":["MCP client compatible with SSE endpoint","Network access to https://publicmcp.beacongom.com/sse"],"input_types":["Raw BSEE API responses (internal to the server)"],"output_types":["JSON objects with standardized fields: incident_id, operator_name, area_name, incident_type (human-readable), date, injuries, fatalities, violations, active_platforms"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_aigniteconsulting-beacon-gom__cap_5","uri":"capability://data.processing.analysis.structured.incident.record.parsing.and.normalization","name":"structured incident record parsing and normalization","description":"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.","intents":["Ensure incident data is consistently formatted for downstream processing, analytics, or reporting","Handle variations in BSEE's data format without requiring client-side normalization logic","Validate incident records for completeness and correctness before using them in compliance reports","Enable reliable parsing of incident data in automated workflows without manual error handling"],"best_for":["Data engineering teams building ETL pipelines that consume BSEE incident data","Analytics platforms that require normalized incident schemas for consistent querying","Compliance reporting systems that need validated, audit-ready incident records","Automated incident processing workflows that cannot tolerate schema inconsistencies"],"limitations":["Normalization is lossy; non-standard fields or metadata in raw BSEE records may be discarded","Schema validation is strict; records that don't conform to the expected schema are rejected rather than partially returned","No schema versioning; changes to BSEE's data format may require updates to the normalization logic","Incident type enumerations are fixed; new incident types added by BSEE may not be recognized until the schema is updated"],"requires":["MCP client that can handle structured JSON responses","Familiarity with the normalized incident schema (field names, data types, enumerations)"],"input_types":["raw BSEE incident records (JSON or other format)"],"output_types":["normalized JSON incident records with standardized field names and data types"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":31,"verified":false,"data_access_risk":"high","permissions":["MCP client compatible with SSE endpoint (Server-Sent Events)","Network access to https://publicmcp.beacongom.com/sse","No API key required (public data source)","MCP client compatible with SSE endpoint","Operator name must match BSEE's official operator registry (e.g., 'Shell Offshore Inc.' vs 'Shell')","Time window parameter must be in a supported format (e.g., '7d', '30d', '90d')","MCP client library (e.g., Claude SDK, Anthropic MCP client, or compatible third-party implementation)","SSE support in the client (most modern HTTP clients support this)","LLM model capable of function calling (e.g., Claude 3, GPT-4, Llama 2 with tool-calling fine-tuning)","MCP client that can handle structured JSON responses"],"failure_modes":["Search limited to public BSEE records only — does not include proprietary incident data or unreported near-misses","Geographic filtering uses BSEE area codes (e.g., 'Vermilion', 'Green Canyon') which may not align with operator-internal naming conventions","Date range queries may have latency >2s for multi-year searches across all operators due to BSEE API response times","No full-text search on incident descriptions — filtering is by structured fields only (operator, area, date)","Summary statistics are cumulative across all time — no built-in time-windowing (e.g., 'incidents in last 2 years') without additional filtering logic","Violation count may include resolved/closed violations, not distinguishing active vs historical compliance status","Active platform count is a point-in-time snapshot and may lag actual operational changes by days or weeks","Does not normalize by platform count or operational hours, so raw incident counts may not reflect true safety rate","BSEE incident reporting has a lag of 1-7 days, so 'recent' incidents may not reflect incidents that occurred today","Result limit is a hard cap — no pagination support, so querying 'top 1000' may timeout or be rejected by the server","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.47,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.635Z","last_scraped_at":"2026-05-03T15:19:03.621Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=aigniteconsulting-beacon-gom","compare_url":"https://unfragile.ai/compare?artifact=aigniteconsulting-beacon-gom"}},"signature":"gjGYFXyf1jY0VV0LJmSHwwKRTChJqXjmHO8p8gaQowf/Jnm1MKeFyxo+QJGvMGNscl11tYGr7YgJliUit24wBQ==","signedAt":"2026-07-08T20:21:12.968Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/aigniteconsulting-beacon-gom","artifact":"https://unfragile.ai/aigniteconsulting-beacon-gom","verify":"https://unfragile.ai/api/v1/verify?slug=aigniteconsulting-beacon-gom","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}