seismic-mcp
Related Servers
Alternatives to seismic-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server wrapping the USGS Earthquake Hazards API, enabling AI assistants to search the global earthquake catalog, look up event details, count quakes, find 'Did You Feel It' reports, and read realtime feeds.5MIT
- AlicenseNot gradedqualityDmaintenanceA powerful MCP server that connects AI assistants to authoritative natural hazard data sources, enabling monitoring of earthquakes, tsunamis, volcanoes, and solar events with configurable alerts and webhooks.1MIT
- FlicenseAqualityDmaintenanceExposes live earth-science data (e.g., earthquakes from USGS) as tools for MCP-compatible AI agents, enabling them to fetch and reason about real-time geophysical events.1-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that makes live Earth data usable by AI agents. Its initial data sources cover natural hazards: earthquakes from the USGS FDSN event catalog and volcanic activity from the Smithsonian Global Volcanism Program.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server enabling real-time communication, task delegation, and acknowledgment among multiple AI agents through a single local endpoint.341 npm4MIT
- AlicenseAqualityCmaintenanceAn MCP server providing real-time access to Philippine government data including earthquakes, weather, typhoons, procurement, population, and air quality. It enables AI agents to query multiple official Philippine data sources through a unified interface for research and analysis purposes.415MIT
TDQS
Scored across 7 tools
Each tool targets a distinct operation: finding reconciled events, retrieving a specific event, comparing source reports, surfacing disagreements, listing agencies, listing raw agency feeds, and fetching agency metadata. The overlap between find_events and find_discrepancies is clearly delineated by threshold filtering, and list_recent_by_agency is explicitly positioned as the raw single-agency counterpart to the reconciled find_events.
All tools follow a snake_case verb_noun pattern: find_events, get_event, compare_sources, find_discrepancies, list_agencies, list_recent_by_agency, get_agency_info. The verbs are varied but predictable (find/list/get/compare), and the noun usage (plural for collection-style operations, singular for single-item fetches) is consistent.
Seven tools is well within the ideal 3-15 range and each tool earns its place in the cross-agency seismic data domain. The count is lean enough to avoid overwhelming an agent while covering the core workflows of discovery, retrieval, comparison, and metadata lookup.
The domain is a read-only, cross-agency earthquake data service, and the surface is complete: discover reconciled events, fetch a specific event, compare raw source fields, find disagreement hotspots, enumerate agencies, inspect a single agency's raw feed, and understand agency-specific biases. No obvious dead ends exist—every tool's output either feeds into another tool or stands alone as a meaningful answer.