Skip to main content
Glama
INGV

mcp-fdsnws-event

Official
by INGV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-fdsnws-event

No user-submitted related servers found.

    Related Servers

    • quake-mcp

      adamcwade
      A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      5
      MIT

    • earth-data-mcp

      fablackner
      A
      license
      Not graded
      quality
      C
      maintenance
      An 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

    • wems-mcp-server

      heliosarchitect
      A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      22 PyPI
      1
      MIT

    • seismic-mcp

      hoon1983
      A
      license
      A
      quality
      D
      maintenance
      A unified MCP server that queries 20 seismic agencies in parallel, reconciles cross-agency earthquake reports, and surfaces discrepancies for AI agents.
      7
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of FDSN earthquake data: querying events, fetching basic info, and retrieving specific data types (arrivals, magnitudes, origins, focal mechanisms). There is no overlap or ambiguity between the tools.

    Naming Consistency4/5

    The tools follow a clear fdsn_<action>_<resource> pattern, with consistent use of '_by_id' for detail retrieval. Minor deviations include the mix of 'query' for search versus 'get' for retrieval, and singular/plural resource names (e.g., earthquakes vs earthquake), but the pattern remains predictable.

    Tool Count5/5

    With 6 tools, the set is well-scoped for an FDSN event server. It provides a search tool and targeted detail tools without unnecessary redundancy, making it easy for agents to navigate.

    Completeness5/5

    The tool surface covers the full lifecycle of earthquake event exploration: searching, getting summary details, and retrieving all major data products (origins, magnitudes, arrivals, focal mechanisms). No critical operations are missing for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources