Skip to main content
Glama
sepehr071

iran-quake-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to iran-quake-mcp

No user-submitted related servers found.

    Related Servers

    • EMSC MCP Server

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search global seismic event data from the European-Mediterranean Seismological Centre's FDSN API, filtering by UTC time range, magnitude, and geographic area, and to retrieve the most recent earthquakes above a minimum magnitude.
      241 npm
      MIT

    • usgs-earthquakes

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to the USGS Earthquake Catalog for querying earthquake events via the FDSNWS API, enabling natural language questions about earthquake data.
      198 npm
      MIT

    • earthscope-fdsn

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying seismic station metadata, regional earthquake catalogs, and federated waveform data availability across FDSN web services, letting users locate seismometers, retrieve local seismicity, and identify data holdings through direct tool calls or natural language.
      213 npm
      MIT

    • mcp-geonet-nz

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query official New Zealand geohazard monitoring data from GeoNet/GNS Science, including recent earthquakes filtered by Modified Mercalli Intensity, detailed single-quake records, and current Volcanic Alert Levels with hazards and aviation colour codes for monitored volcanoes. Runs keyless over a hosted gateway URL or locally via npx as a stdio server.
      12 npm
      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.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a recognizable role: free-form filtered search, newest-first list, strongest-first list, single-event detail, and aggregate counts. However, eq_search, eq_latest, and eq_significant all return event lists and differ mainly in sort/filter semantics, so a sloppy agent could pick the wrong one; the descriptions do a good job clarifying when to use each.

    Naming Consistency4/5

    All names use the eq_ prefix with snake_case, which is highly predictable and readable. The one deviation is that search/detail are verb-like while latest/significant/stats are nouns/adjectives, so the verb_noun pattern isn't strictly uniform.

    Tool Count5/5

    Five tools is well-scoped for an Iran earthquake service: discovery (search/latest/significant), retrieval (detail), and aggregation (stats). No tool feels redundant or padded.

    Completeness4/5

    The surface covers the core lifecycle: find events by time/place/magnitude, get newest and largest, fetch full detail, and compute activity counts. Gaps are minor (no source/catalog listing or station/network metadata), but nothing blocks typical agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources