io.github.hoon1983/seismic-mcp
PYPI · SEISMIC-MCP · SCANNED SEP 21
Unified earthquake data from 20 global seismic agencies, with cross-agency report reconciliation.
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 88 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add hoon1983-seismic-mcp -- uvx seismic-mcp
{
"mcpServers": {
"hoon1983-seismic-mcp": {
"command": "uvx",
"args": [
"seismic-mcp"
]
}
}
} {
"servers": {
"hoon1983-seismic-mcp": {
"command": "uvx",
"args": [
"seismic-mcp"
]
}
}
} codex mcp add hoon1983-seismic-mcp -- uvx seismic-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hoon1983-seismic-mcp": {
"type": "local",
"command": [
"uvx",
"seismic-mcp"
],
"enabled": true
}
}
} openclaw mcp add hoon1983-seismic-mcp --command uvx --arg seismic-mcp
mcp_servers:
hoon1983-seismic-mcp:
command: "uvx"
args: ["seismic-mcp"] {
"McpServers": {
"hoon1983-seismic-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"seismic-mcp"
]
}
}
} assistant mcp add hoon1983-seismic-mcp -t stdio -c uvx -a seismic-mcp
{
"mcpServers": {
"hoon1983-seismic-mcp": {
"command": "uvx",
"args": [
"seismic-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −4
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.83 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
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 21 Sept 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 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | 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 →
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 →
compare_sources 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.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
find_discrepancies 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | – | – | – |
| center_lat | – | – | – |
| center_lon | – | – | – |
| end_time | – | – | – |
| limit | integer | – | – |
| max_latitude | – | – | – |
| max_longitude | – | – | – |
| max_magnitude | – | – | – |
| min_latitude | – | – | – |
| min_location_spread_km | number | – | – |
| min_longitude | – | – | – |
| min_magnitude | – | – | – |
| min_magnitude_spread | number | – | – |
| radius_km | – | – | – |
| require_multi_agency | boolean | – | – |
| start_time | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
find_events 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | – | – | – |
| center_lat | – | – | – |
| center_lon | – | – | – |
| end_time | – | – | – |
| limit | integer | – | – |
| max_latitude | – | – | – |
| max_longitude | – | – | – |
| max_magnitude | – | – | – |
| min_latitude | – | – | – |
| min_longitude | – | – | – |
| min_magnitude | – | – | – |
| radius_km | – | – | – |
| start_time | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_agency_info 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_event 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.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_agencies List Agencies ~26
All agency codes this server knows about (whether FDSN-wired or not).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_recent_by_agency 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`.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | yes | – |
| end_time | – | – | – |
| limit | integer | – | – |
| min_magnitude | – | – | – |
| start_time | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
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 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 September 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.