Iran Earthquakes
PYPI · IRAN-QUAKE-MCP
Unofficial read-only Iran earthquakes: latest, search, strongest, detail, stats (USGS, EMSC, IRSC).
Available components
Last scanned (13 hours ago)
Scores higher than 77% of PyPI servers
Category Maps and Location
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 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sepehr071/iran-quake-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1952 tokens (~390/item across 5 items; 5 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 22 Oct 26 +16
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.0 → 0.1.1 functional
- 20 Oct 26 63
First indexed and scored.
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 22 Oct 2026 · Analysed pypi/iran-quake-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sepehr071/iran-quake-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sepehr071/iran-quake-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 3390383803 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9c9fb549f83c6520feca3e80d9d463f7a4e903c0d8150d4d0837e4e083c6e037 |
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 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 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 →
eq_detail Earthquake detail ~169
Get one earthquake in full: location, depth_km, magnitude type and source quality fields. The source is detected from the id format (IRSC: plain number, found only in its latest ~20 events, adds the nearest towns). USGS adds review status, shaking (felt reports, cdi, mmi), tsunami flag, sig (significance 0-1000), nst (stations), gap (degrees), rms; EMSC adds the contributing agency (catalog) and last update. Times in UTC and Tehran (UTC+03:30).
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event id from another eq_ tool: USGS 'us6000u2w9', EMSC '20261016_0000282' or IRSC '213549'. |
No output schema declared.
No examples provided.
eq_latest Latest earthquakes ~277
List the most recent earthquakes in Iran, newest first. Use for "was there an earthquake today?". Times: time_utc and time_tehran (UTC+03:30); depth_km in km; magnitude type in mag_type (mb, ml, mw...). Call eq_detail with an id for more, eq_stats for counts.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look back this many hours, e.g. 24. |
| iran_only | boolean | – | True (default): keep only events inside a coarse Iran outline (lat/lon, includes Iranian waters) whose place text names Iran (or Persian Gulf, Gulf of Oman, Caspian Sea); neighbours across the border… |
| limit | integer | – | Max events to return, 1-50 (a reply stays under 15 KB), e.g. 20. |
| min_magnitude | number | – | Minimum magnitude, e.g. 3.0. |
| source | string | – | Data source: 'usgs' (USGS ComCat, default), 'emsc' (EMSC via SeismicPortal) or 'irsc' (Iranian Seismological Center, only its latest ~20 events, with province names). Magnitudes and locations differ… |
No output schema declared.
No examples provided.
eq_search Search earthquakes ~616
Search earthquakes in Iran by date range, magnitude, bounding box and place text. Use for history ("M5+ in 2026", "quakes near Bam"). USGS and EMSC have no province field: USGS gives the nearest town ('70 km NNE of Minab, Iran'), EMSC a region ('SOUTHERN IRAN'); filter by `place` (a province name works) or `bbox`. source='irsc' only knows its latest ~20 events, so older dates give `more`=true with few rows. Times: time_utc and time_tehran (UTC+03:30); depth_km in km. `more` = more results may exist beyond `limit` (or beyond the newest 500 events scanned when filtering by place/iran_only: narrow the dates or bbox).
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | – | – | Box 'min_lat,min_lon,max_lat,max_lon', e.g. '35,50,36,52' (Tehran area). Default: all Iran. |
| end_date | – | – | End, UTC, same format, e.g. '2026-10-15' (a date alone includes that whole day). Default: now. |
| iran_only | boolean | – | True (default): keep only events inside a coarse Iran outline (lat/lon, includes Iranian waters) whose place text names Iran (or Persian Gulf, Gulf of Oman, Caspian Sea); neighbours across the border… |
| limit | integer | – | Max events to return, 1-50 (a reply stays under 15 KB), e.g. 20. |
| max_magnitude | – | – | Maximum magnitude, e.g. 6. |
| min_magnitude | – | – | Minimum magnitude, e.g. 4.5. |
| order | string | – | 'time' (newest first, default) or 'magnitude' (largest first). |
| place | – | – | Text the place must contain, case and accents ignored, e.g. 'Minab' or 'southern iran' (EMSC region); IRSC places are 'Town, Province'. A province name (Tehran, Kerman, Hormozgan, Khuzestan, Fars, Si… |
| source | string | – | Data source: 'usgs' (USGS ComCat, default), 'emsc' (EMSC via SeismicPortal) or 'irsc' (Iranian Seismological Center, only its latest ~20 events, with province names). Magnitudes and locations differ… |
| start_date | string | yes | Start, UTC: 'YYYY-MM-DD' or 'YYYY-MM-DDTHH:MM:SS', e.g. '2026-10-01'. |
No output schema declared.
No examples provided.
eq_significant Significant earthquakes ~241
List the strongest recent earthquakes in Iran, largest magnitude first. Use for "biggest earthquakes this month/year". Times in UTC and Tehran (UTC+03:30), depth_km in km.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days, e.g. 30. |
| iran_only | boolean | – | True (default): keep only events inside a coarse Iran outline (lat/lon, includes Iranian waters) whose place text names Iran (or Persian Gulf, Gulf of Oman, Caspian Sea); neighbours across the border… |
| limit | integer | – | Max events to return, 1-50, e.g. 10. |
| min_magnitude | number | – | Minimum magnitude, e.g. 5.0. |
| source | string | – | Data source: 'usgs' (USGS ComCat, default), 'emsc' (EMSC via SeismicPortal) or 'irsc' (Iranian Seismological Center, only its latest ~20 events, with province names). Magnitudes and locations differ… |
No output schema declared.
No examples provided.
eq_stats Earthquake statistics ~255
Count earthquakes in Iran over a window: by magnitude band, by place, plus the strongest event. Use for "how active has Iran been this month". Places are USGS nearest towns or EMSC regions (no province data). `truncated` = the source returned its full 3000 rows before the Iran filter, so the count covers only the newest.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window length in days, ending now, e.g. 30. |
| iran_only | boolean | – | True (default): keep only events inside a coarse Iran outline (lat/lon, includes Iranian waters) whose place text names Iran (or Persian Gulf, Gulf of Oman, Caspian Sea); neighbours across the border… |
| min_magnitude | number | – | Minimum magnitude counted, e.g. 3.0. |
| source | string | – | Data source: 'usgs' (USGS ComCat, default), 'emsc' (EMSC via SeismicPortal) or 'irsc' (Iranian Seismological Center, only its latest ~20 events, with province names). Magnitudes and locations differ… |
No output schema declared.
No examples provided.
How do I install the Iran Earthquakes MCP server?
Iran Earthquakes runs locally as a PyPI package, launched with uvx iran-quake-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 · iran-quake-mcp
claude mcp add sepehr071-iran-quake-mcp -- uvx iran-quake-mcp
What is the Iran Earthquakes MCP server?
Iran Earthquakes is an MCP server listed in the public MCP registry as io.github.sepehr071/iran-quake-mcp. Unofficial read-only Iran earthquakes: latest, search, strongest, detail, stats (USGS, EMSC, IRSC). This page covers its PyPI package (iran-quake-mcp).
Is the Iran Earthquakes MCP server safe to use?
Iran Earthquakes scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. Its build provenance is signed and verified. 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 Iran Earthquakes MCP server expose?
Iran Earthquakes exposes 5 tools: eq_latest, eq_search, eq_significant, eq_detail, eq_stats. Their descriptions and schemas cost roughly 1,558 tokens of context every time the server is loaded.
Is the Iran Earthquakes MCP server still maintained?
Iran Earthquakes is still listed as active in the MCP registry. We last reached this channel on 22 October 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 Iran Earthquakes MCP server under?
Iran Earthquakes declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.