Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.hoon1983/seismic-mcp

PYPI · SEISMIC-MCP

Unified earthquake data from 20 global seismic agencies, with cross-agency report reconciliation.

Available components

0 this week 82 Trust /100

Last scanned (20 hours ago)

Scores higher than 84% of PyPI servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 950 tokens (~135/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 30 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 23 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/seismic-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~856 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_sources ~81

Side-by-side per-field comparison of every agency's report for one event. Returns a field-major view (magnitude, lat, lon, depth, time, ...) with one column per agency and the numeric spread per field. Use this when an agent needs to explain *why* sources disagree on a specific earthquake.

NameTypeReqDescription
canonical_idstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

find_discrepancies ~198

Return events where agency reports disagree past the given thresholds. Same query params as `find_events`, plus tunable spread thresholds. By default keeps only events reported by 2+ agencies, since a lone report cannot disagree with itself. Useful for journalism, QA of preliminary feeds, or surfacing where the global picture is genuinely uncertain.

NameTypeReqDescription
agencies–––
center_lat–––
center_lon–––
end_time–––
limitinteger––
max_latitude–––
max_longitude–––
max_magnitude–––
min_latitude–––
min_location_spread_kmnumber––
min_longitude–––
min_magnitude–––
min_magnitude_spreadnumber––
radius_km–––
require_multi_agencyboolean––
start_time–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

find_events ~248

Find recent or historical earthquakes, reconciled across multiple seismic agencies. Queries every supported agency in parallel (~20 networks including USGS, EMSC, JMA, INGV, GeoNet, AFAD, and others) and clusters their reports so each returned event lists every agency that picked it up — the agent sees cross-network disagreement explicitly when it exists. Unreachable agencies fail gracefully and are skipped; a 60s TTL cache makes repeat queries cheap. Pass `agencies=["USGS", "EMSC", ...]` to restrict the source set. Use `list_agencies` to see all supported codes. NOT for emergency or early-warning use; data is preliminary. Defaults: last 24 hours, no magnitude filter, limit 50.

NameTypeReqDescription
agencies–––
center_lat–––
center_lon–––
end_time–––
limitinteger––
max_latitude–––
max_longitude–––
max_magnitude–––
min_latitude–––
min_longitude–––
min_magnitude–––
radius_km–––
start_time–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_agency_info ~74

Static metadata about a seismic agency: coverage, latency, magnitude completeness, notes. Use to interpret cross-agency disagreement (e.g. JMA magnitudes are systematically lower than USGS Mw for the same event) or to decide which agency is authoritative for a region.

NameTypeReqDescription
agencystringyes–
NameTypeReqDescription
result–yes–

No examples provided.

get_event ~121

Fetch one reconciled event by canonical_id (format: 'AGENCY:event_id'). Re-queries the seed agency by ID, then sweeps every supported agency in parallel within ±10 minutes and ~3° of the seed to find matching reports. Returns the reconciled cluster, or None if the seed cannot be found. Use canonical_ids from `find_events` (e.g. 'USGS:us6000sze1') to drill into a single event with the full cross-agency view.

NameTypeReqDescription
canonical_idstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

list_agencies ~26

All agency codes this server knows about (whether FDSN-wired or not).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_recent_by_agency ~108

Raw recent events from a single agency, without cross-agency reconciliation. Returns `SourceReport` objects exactly as the agency reported them. Use this to see what one network alone is publishing (often includes small local events the global feeds miss) or to compare against the reconciled view from `find_events`.

NameTypeReqDescription
agencystringyes–
end_time–––
limitinteger––
min_magnitude–––
start_time–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the io.github.hoon1983/seismic-mcp server?

io.github.hoon1983/seismic-mcp runs locally as a PyPI package, launched with uvx seismic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · seismic-mcp

# add to Claude Code
claude mcp add hoon1983-seismic-mcp -- uvx seismic-mcp
Common questions

What is the io.github.hoon1983/seismic-mcp server?

io.github.hoon1983/seismic-mcp is listed in the public MCP registry as io.github.hoon1983/seismic-mcp. Unified earthquake data from 20 global seismic agencies, with cross-agency report reconciliation. This page covers its PyPI package (seismic-mcp).

Is the io.github.hoon1983/seismic-mcp server safe to use?

io.github.hoon1983/seismic-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.hoon1983/seismic-mcp server expose?

io.github.hoon1983/seismic-mcp exposes 7 tools: find_events, get_event, compare_sources, find_discrepancies, list_recent_by_agency, and 2 more. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.

Is the io.github.hoon1983/seismic-mcp server still maintained?

io.github.hoon1983/seismic-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.hoon1983/seismic-mcp server under?

io.github.hoon1983/seismic-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.hoon1983/seismic-mcp server?

VerifyMCP ran 16 checks on io.github.hoon1983/seismic-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.