mcp-registry/com.olyport/earthquake · v1.26.0
As of 2026-10-26 22:39 UTC, the Olyport Earthquake MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Real-time earthquake events from the US Geological Survey
Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/earthquake/mcp
9 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.olyport%2Fearthquake/fixes
{
"name": "get_earthquake_detail",
"description": "Get full details of a specific earthquake event by its USGS event ID.\n\n Returns comprehensive information including magnitude, location, depth,\n felt reports, tsunami status, and tectonic summary when available.\n\n Args:\n event_id: The USGS event ID (e.g. 'us7000m1xh'). Get IDs from search results.\n ",
"inputSchema": {
"type": "object",
"title": "get_earthquake_detailArguments",
"required": [
"event_id"
],
"properties": {
"event_id": {
"type": "string",
"title": "Event Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_earthquakes_near",
"description": "Get earthquakes near a specific geographic location.\n\n Searches for earthquakes within a radius of the given coordinates.\n Useful for assessing local seismic risk or investigating felt reports.\n\n Args:\n latitude: Latitude of the center point (e.g. 37.7749 for San Francisco).\n longitude: Longitude of the center point (e.g. -122.4194 for San Francisco).\n radius_km: Search radius in kilometers (default 100, max 20001).\n min_magnitude: Minimum magnitude to includ",
"inputSchema": {
"type": "object",
"title": "get_earthquakes_nearArguments",
"required": [
"latitude",
"longitude"
],
"properties": {
"days": {
"type": "integer",
"title": "Days",
"default": 30
},
"latitude": {
"type": "number",
"title": "Latitude"
},
"longitude": {
"type": "number",
"title": "Longitude"
},
"radius_km": {
"type": "number",
"title": "Radius Km",
"default": 100
},
"min_magnitude": {
"type": "number",
"title": "Min Magnitude",
"default": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_recent_earthquakes",
"description": "Get recent earthquakes worldwide above a minimum magnitude.\n\n Returns earthquake events from the USGS catalog sorted by time (newest first).\n Useful for monitoring seismic activity globally.\n\n Args:\n min_magnitude: Minimum magnitude to include (default 2.5). Use 4.5+ for significant quakes only.\n days: Number of days to look back (default 7, max 30).\n limit: Maximum number of earthquakes to return (default 50, max 500).\n ",
"inputSchema": {
"type": "object",
"title": "get_recent_earthquakesArguments",
"properties": {
"days": {
"type": "integer",
"title": "Days",
"default": 7
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 50
},
"min_magnitude": {
"type": "number",
"title": "Min Magnitude",
"default": 2.5
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.olyport/earthquake"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.olyport/earthquake"}) over MCP.
get_earthquakes_near ~269 tokensget_recent_earthquakes ~219 tokensget_earthquake_detail ~149 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fearthquake?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fearthquake?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fearthquake.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fearthquake.svg :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fearthquake?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:84db7d4c880d15b2…, first seen 2026-10-17, included at leaf 4773 of 75,874. Version history · verify what your client received.
Compare: most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 22:39 UTC, the Olyport Earthquake MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Olyport Earthquake MCP server advertises 3 tools, including get_earthquake_detail, get_earthquakes_near, get_recent_earthquakes.
Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/earthquake/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.