Skip to content

earthquake-mcp-server

io.github.cyanheads/earthquake-mcp-servercyanheadsstreamable-httpv0.5.2Scanned

Search USGS and EMSC seismic data — real-time feeds, event queries, and earthquake counts.

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the earthquake-mcp-server can do

The earthquake-mcp-server is published by the GitHub account cyanheads. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools bring in text other people can write (earthquake_get_feed, earthquake_search_events, earthquake_get_event and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 0.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • earthquake_count_eventsCount matches without event records, or size an earthquake_search_events query.Reads text others writeNo findings

    Why it is in this group

    • The name "earthquake_count_events" says "count": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Count matches without event records, or size an earthquake_search_events query. Omitting start_time uses 30 days; pass explicit bounds for historical periods. queryEcho reports applied filters/window; ignoredFilters names unsupported EMSC inputs. Circle and independently optional box edges intersect. Both catalogs include non-tectonic events; event_type="earthquake" excludes them on USGS. exceeds_limit marks the 20,000-event single-request threshold, not a retrieval ceiling: search supports offset paging beyond it. max_allowed is 20,000 for USGS, null for EMSC.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • earthquake_get_eventFetch one earthquake by event ID: a USGS ID, or an EMSC ID (an origin date and seven-digit sequence, e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "earthquake_get_event" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch one earthquake by event ID: a USGS ID, or an EMSC ID (an origin date and seven-digit sequence, e.g. "20190706_0000043"). Returns the same normalized event a search result carries. For a USGS event it adds a projection of the analysis products only the single-event response holds: PAGER impact alert and report link, ShakeMap peak intensity and ground motion, DYFI felt-report totals, focal mechanism from a moment tensor or a standalone focal-mechanism product, landslide and liquefaction alerts, origin quality (azimuthal gap, station count, location uncertainty, depth type), and finite-fault rupture dimensions. Product groups are omitted when no projected field is available — a small automatic event typically carries only origin quality, while a large reviewed one has most of it. Opt into more with include: alternative origin solutions, magnitude solutions, phase arrivals, the USGS aftershock forecast, or the PAGER loss estimates behind the alert with population exposure by shaking intensity; a requested group that is not returned is listed in unavailable_includes. EMSC publishes none of these products, so an EMSC event has no detail and lists every requested group as not_published. Event IDs appear in the "id" field of earthquake_get_feed and earthquake_search_events results; a USGS event's associated_ids are also accepted.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • earthquake_get_feedFetch a USGS pre-computed real-time earthquake feed by magnitude tier and time window.Reads text others writeNo findings

    Why it is in this group

    • The name "earthquake_get_feed" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch a USGS pre-computed real-time earthquake feed by magnitude tier and time window. These feeds are CDN-cached by USGS and faster and more available than the query API — use them for "what's happening now" queries. "all" includes microseisms (M<1); "significant" is a USGS curation based on magnitude, felt reports, and PAGER impact estimates. "hour" returns 0–10 events typically; "month" can exceed 10,000 for the "all" tier, so results are returned a page at a time: count is the page size, totalCount the whole feed, and nextCursor the input for the following page. Each page returns limit events (default 15, at most 1,000), fewer only on the last page. The cursor is opaque and must be passed back verbatim — unlike earthquake_search_events, these feeds retain the first-read generation for up to 15 minutes, subject to capacity eviction and restart. An expired cursor requires a fresh first read. For historical or filtered queries, use earthquake_search_events instead.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • earthquake_search_eventsSearch USGS or independent global EMSC seismic catalogs by time, magnitude, depth, area and source-specific filters.Reads text others writeNo findings

    Why it is in this group

    • The name "earthquake_search_events" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search USGS or independent global EMSC seismic catalogs by time, magnitude, depth, area and source-specific filters. Both include non-tectonic events; event_type="earthquake" excludes them on USGS. Circle and independently optional box edges intersect. Unsupported EMSC filters appear in ignoredFilters. Size queries with earthquake_count_events. Returns limit events per call (at most 1,000), fewer only on the last page. Continue with offset=nextOffset and unchanged filters/order. totalCount is the full match total when known; countUnavailable marks a failed count lookup, so the total is unknown. Paging can retrieve matches beyond 20,000.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
  2. Tools3 changed.~3 changedView diff
  3. Tools3 changed.~3 changedView diff
  4. Tools3 changed.~3 changedView diff

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http earthquake https://earthquake.caseyjhand.com/mcp
claude mcp add --transport http earthquake https://earthquake.caseyjhand.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__earthquake__earthquake_get_feed",
      "mcp__earthquake__earthquake_search_events",
      "mcp__earthquake__earthquake_get_event",
      "mcp__earthquake__earthquake_count_events"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as earthquake. Review it before you use it.

Capability tags behind 4 rules
  • mcp__earthquake__earthquake_get_feed untrusted-input
  • mcp__earthquake__earthquake_search_events untrusted-input
  • mcp__earthquake__earthquake_get_event untrusted-input
  • mcp__earthquake__earthquake_count_events untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/earthquake-mcp-server/verify?hash=77e4ebbe0a7f41b0094f1ba5d02ee72ffdf36770f04f9e7f4cee0af4633b3a36" | jq -e '.changed == false'

Pinned hash 77e4ebbe0a7f, from Nov 14, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cyanheads/earthquake-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cyanheads/earthquake-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/earthquake-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/earthquake-mcp-server)

Source: MCP Registry · repository. Synced Nov 14, 2026, 07:17 UTC.

earthquake-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the earthquake-mcp-server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the earthquake-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the earthquake-mcp-server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the earthquake-mcp-server have?

4 tools: 4 read. earthquake_get_feed, earthquake_search_events, earthquake_get_event and earthquake_count_events.

Does the earthquake-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the earthquake-mcp-server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the earthquake-mcp-server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.