Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Earthquake MCP Server

de cyanheadsversión 0.5.1i★ –iComputadora o nube
Nombre en el registroio.github.cyanheads/earthquake-mcp-server

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Computadora o nube
  • Transporte: stdio, Streamable HTTP
  • Categoría: Búsqueda y memoria de IA

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 3 de 3 superadas
  • Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
  • Puede hacer 4 cosas (herramientas) earthquake_get_feed, earthquake_search_events, earthquake_get_event, earthquake_count_events
  • Debes completar tú: MCP_LOG_LEVEL, USGS_BASE_URL, EMSC_BASE_URL, DEFAULT_LIMIT, REQUEST_TIMEOUT_MS, EARTHQUAKE_CLAMP_LIMITS

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Funciona en Claude para web, escritorio y móvil:

  1. Abre Settings → Connectors
  2. Presiona Add custom connector
  3. Pega la dirección de abajo y presiona Add
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Add2https://…3
https://earthquake.caseyjhand.com/mcp

O ejecútalo en tu computadora

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "earthquake": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/earthquake-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "USGS_BASE_URL": "your-value",
        "EMSC_BASE_URL": "your-value",
        "DEFAULT_LIMIT": "your-value",
        "REQUEST_TIMEOUT_MS": "your-value",
        "EARTHQUAKE_CLAMP_LIMITS": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

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

O ejecútalo en tu computadora

claude mcp add earthquake --env MCP_LOG_LEVEL=your-value --env USGS_BASE_URL=your-value --env EMSC_BASE_URL=your-value --env DEFAULT_LIMIT=your-value --env REQUEST_TIMEOUT_MS=your-value --env EARTHQUAKE_CLAMP_LIMITS=your-value -- npx -y @cyanheads/earthquake-mcp-server

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "earthquake": {
      "url": "https://earthquake.caseyjhand.com/mcp"
    }
  }
}

O ejecútalo en tu computadora

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "earthquake": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/earthquake-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "USGS_BASE_URL": "your-value",
        "EMSC_BASE_URL": "your-value",
        "DEFAULT_LIMIT": "your-value",
        "REQUEST_TIMEOUT_MS": "your-value",
        "EARTHQUAKE_CLAMP_LIMITS": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "earthquake": {
      "type": "http",
      "url": "https://earthquake.caseyjhand.com/mcp"
    }
  }
}

O ejecútalo en tu computadora

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "earthquake": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/earthquake-mcp-server"
      ],
      "env": {
        "MCP_LOG_LEVEL": "your-value",
        "USGS_BASE_URL": "your-value",
        "EMSC_BASE_URL": "your-value",
        "DEFAULT_LIMIT": "your-value",
        "REQUEST_TIMEOUT_MS": "your-value",
        "EARTHQUAKE_CLAMP_LIMITS": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

ChatGPT solo se conecta a servidores en internet:

  1. Abre ChatGPT en la web → Settings → Connectors (Apps)
  2. Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
  3. Pega la dirección de abajo, ponle un nombre y guarda
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Create2https://…3
https://earthquake.caseyjhand.com/mcp

Los nombres de los menús pueden variar un poco según el plan y con el tiempo.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • MCP_LOG_LEVEL env
    Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').
  • USGS_BASE_URL env
    USGS API base URL. Override for testing or mirroring.
  • EMSC_BASE_URL env
    EMSC API base URL. Override for testing or mirroring.
  • DEFAULT_LIMIT env
    Events earthquake_search_events returns when a call omits limit (1-1000).
  • REQUEST_TIMEOUT_MS env
    Per-attempt HTTP timeout in milliseconds (1000-120000). Every feed, search, count, and event call also runs under one 50-second total deadline across its requests and retries.
  • EARTHQUAKE_CLAMP_LIMITS env
    Clamp a search or feed limit above 1000 to 1000 with a notice. Set false to advertise and enforce a maximum of 1000 instead.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

  • earthquake_get_feed

    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 cura

  • earthquake_search_events

    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 ap

  • earthquake_get_event

    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

  • earthquake_count_events

    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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub cyanheads, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • ✓ Superada

    El endpoint responde

    Respondió en 180 ms (HTTP 200)

  • – No aplica

    Inicio de sesión con OAuth

    No hace falta iniciar sesión

  • ✓ Superada

    Sin instrucciones ocultas en las descripciones de herramientas

    Leímos 4 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Búsqueda y memoria de IAi

  • Más estrellas que el 0% de los otros 5714 servidores de esta categoría
  • Publicado en el registro más recientemente que el 89% de los otros 5714 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 5714 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Earthquake MCP Server?

Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.5.1) llegó al registro hace 4 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Context7, Codebase Memory, Exa

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Context7

Up-to-date docs for AI agents

de upstashMuy usado↓ 972,7 mil/sem★ 64,2 milActualizado anteayer

Computadora o nube

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

de DeusDataMuy usado↓ 18 mil/sem★ 48,1 milActualizado hace 22 días

Se ejecuta en tu computadora

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

de exa-labsMuy usado★ 5,2 milActualizado hace 2 meses

Se ejecuta en la nube✓ exa.ai

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

@cyanheads/earthquake-mcp-server Search USGS and EMSC seismic data — real-time feeds, event queries, and earthquake counts via MCP. STDIO or Streamable HTTP. 4 Tools • 3 Resources

Public Hosted Server: https://earthquake.caseyjhand.com/mcp


Overview

Seismic data from USGS ComCat and the EMSC SeismicPortal. Fetch real-time earthquake feeds, search and count seismic events by time, magnitude, depth, and location, and pull full analysis detail for a single event.

Tools
ToolDescription
earthquake_get_feedFetch a USGS pre-computed real-time earthquake feed by magnitude tier and time window
earthquake_search_eventsSearch earthquakes by time range, magnitude, depth, location radius, PAGER alert level, felt reports, or ShakeMap and DYFI intensity
earthquake_count_eventsCount earthquakes matching filters without fetching full records
earthquake_get_eventFetch one earthquake by USGS or EMSC event ID, with USGS analysis products and opt-in origins, magnitudes, phase arrivals, aftershock forecast, and PAGER loss estimates
Resources
ResourceDescription
earthquake://feed/{magnitude_tier}/{time_window}First 100-event page of a USGS real-time feed, with an exact continuation URI
earthquake://feed/{magnitude_tier}/{time_window}/page/{cursor}Continue the retained feed generation using the returned next_uri
earthquake://event/{event_id}One earthquake by USGS or EMSC event ID as injectable context, with the same detail product projection as earthquake_get_event
Skill
SkillDescription
earthquake-guideAgent guide for the earthquake_* tools: identifier chains between USGS and EMSC, coverage and magnitude-scale gates, and when product and include groups answer a question. Loaded by plugin hosts from skills/ and served over MCP as skill://earthquake-guide/SKILL.md

Capability reference

earthquake_get_feed tool
  • Choose a magnitude tier (all, 1.0, 2.5, 4.5, significant) and a window (hour, day, week, month). USGS caches these feeds; use earthquake_search_events for historical or filtered queries.
  • Returns events, page count, generation time, and source feed URL. all includes microseisms; significant is USGS-curated using magnitude, felt reports, and PAGER impact.
  • Each page returns limit events (default 15), fewer only on the last page. A limit above 1,000 returns 1,000 with a notice naming the requested and applied values; with EARTHQUAKE_CLAMP_LIMITS=false it is rejected instead. limit applies to the first page; later pages keep the page size in the cursor. totalCount reports the whole feed; pass nextCursor back unchanged with the same tier and window.
  • Continuations read the first-read generation, unaffected by upstream edits. Retention lasts up to 15 minutes, subject to capacity eviction and restart. cursor_expired means restart without a cursor; legacy cursors must also be restarted.

earthquake_search_events tool
  • Search usgs or emsc by time, magnitude, depth, radius, or bounding box. A radius requires latitude, longitude, and radius_km together; box edges are independently optional, support antimeridian bounds up to ±360°, and intersect a supplied circle.
  • Returns normalized events with event_type, EMSC's event_certainty, and USGS's associated_ids (other network IDs merged into the event). ignoredFilters names unsupported filters; queryEcho reports the effective query.
  • Both search and count accept open magnitude_type values on either source; EMSC matches its own lowercase types (mb, mw) exactly and has no mww. product_type (required product, e.g. moment-tensor) and review_status (automatic or reviewed) apply only to USGS; EMSC names them in ignoredFilters. Blank values mean omitted.
  • event_type, magnitude_type, and product_type stay open strings; USGS matches them case-insensitively, and event_type takes a comma-separated list. USGS answers a value outside its published vocabulary with zero events, so when a USGS search's first page or a USGS count comes back empty, notice names each unlisted value and the listed values it equals once case and -, _, and spaces are ignored: product_type "moment_tensor" suggests "moment-tensor". The vocabulary read is one attempt within the call's deadline, cached for 24 hours; if it fails, the zero returns as it would without the check. EMSC publishes no vocabulary and is not checked.
  • min_mmi (ShakeMap intensity, Modified Mercalli) and min_cdi (DYFI community intensity), each 1–12, select events by how strongly they shook, which a magnitude floor or alert_level misses. Both apply only to USGS: an event without a ShakeMap or DYFI reports never matches, and EMSC names them in ignoredFilters.
  • Date-only bounds (including expanded year/year-month forms) mean midnight at the start of the named day on both sources: 2026-10-10 becomes 2026-10-10T00:00:00. Explicit time and timezone suffixes are preserved; unpadded date components are padded. Offsetless times use UTC for the 30-day default. queryEcho shows the exact effective bounds.
  • Sort by time or magnitude in either direction. Each call requests limit events upstream (default 15, set by DEFAULT_LIMIT) and returns them all, fewer only on the last page. A limit above 1,000 returns 1,000 with a notice naming the requested and applied values; with EARTHQUAKE_CLAMP_LIMITS=false it is rejected instead. queryEcho.limit reports the applied limit. Continue with the returned nextOffset (offset plus the events returned, counting from 1) and the same filters, limit, and order. Search pages read the current catalog, so upstream edits can affect later pages.
  • Strictly inverted magnitude, depth, or explicit time bounds fail locally as invalid_range, naming both values and recovery. Equal and single bounds remain valid; time comparisons use UTC instants, including explicit offsets. Calendar-invalid values remain for upstream rejection.
  • A nonempty short page establishes totalCount; an empty first page establishes zero, while an empty later page leaves the total unknown. Full pages use a count lookup, with countUnavailable on failure. Feed, search, count, and event calls each share one 50-second deadline across their requests and retries; for search that includes the count lookup. Cancellation remains cancellation.

earthquake_count_events tool
  • Count matches using the same filters as earthquake_search_events, without fetching events. Omit start_time for the last 30 days; queryEcho reports the resolved window and applied filters.
  • exceeds_limit flags the 20,000-event single-request threshold, not a retrieval ceiling: search offset paging can retrieve larger match sets. max_allowed is 20,000 for USGS and null for EMSC; ignoredFilters names filters the source cannot apply.
  • A USGS count of zero carries notice when a supplied event_type, magnitude_type, or product_type value is not in the USGS vocabulary, as search's empty first page does.

earthquake_get_event tool
  • Pass the id of any feed or search result. An EMSC unid from a source=emsc search (eight digits, underscore, seven digits, e.g. 20190706_0000043) is looked up on EMSC SeismicPortal; every other ID goes to USGS (e.g. us6000sznj).
  • A USGS event returns the normalized event plus optional detail: PAGER, ShakeMap, DYFI, moment tensor, ground-failure alerts, origin quality (including depth_type, which separates an assigned depth from a located one), and finite-fault dimensions. Groups are omitted when none of their projected fields is available; absence does not imply zero impact. associated_ids lists the other network IDs USGS holds for the event; an alias such as us70004bn0 returns the preferred event (ci38457511) with the alias listed there.
  • An EMSC event returns the same normalized event its search result carries, with no detail and no associated_ids.
  • include opts into more for USGS events:
GroupSourceExtra requests
originsEvery origin product in the event response, preferred firstNone
magnitudesEvent-level magnitudes from the preferred phase-data product's QuakeML, with a station count where publishedOne, shared with arrivals
arrivalsEvery phase arrival of that document's preferred origin, joined to its pick and sorted nearest firstOne, shared with magnitudes
aftershock_forecastThe USGS Operational Aftershock Forecast: each window's probability of an aftershock at or above each magnitude, its expected-count range, and the chance of one as large as the mainshockOne
pagerThe PAGER estimates behind the alert, from the preferred losspager product's JSON files: the fatality and economic-loss alert levels with every probability bracket (economic bounds in millions of USD), PAGER's impact statements, and the people exposed at each shaking intensity, in total and per countryTwo, or three when the product publishes impact statements
  • A requested group that is not returned is listed in unavailable_includes: not_published when the event has no such product (every group on an EMSC event) or its product lacks the files the group reads (PAGER products published before the JSON files existed), fetch_failed when the download failed, returned HTML, did not parse, pointed outside the configured USGS origin, or answered with a redirect. The event, detail, and other groups still return; cancellation propagates. The event request and its product downloads share one 50-second deadline.
  • Blank IDs fail locally

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx