Earthquake Data SkillEarthquake Data Skill

OnlineCredit Usage:1 per callTool:EarthquakeDataSkill

The tool

Feed live seismic data to your agent. Call it as an MCP tool to read worldwide earthquake counts and the largest recent magnitude.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as EarthquakeDataSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "EarthquakeDataSkill",
  "arguments": {}
}

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "earthquakes_LastUpdated": "2026-02-18T12:00:00.000Z",
    "earthquakes_LastHour": 9,
    "count24h": 187,
    "largestMagnitude24h": 5.2,
    "avgMagnitude24h": 1.84,
    "earthquakes": [
      {
        "mag": 3.4,
        "place": "153 km SSW of Channel Islands Beach, California",
        "time": 1765921110756,
        "felt": 1,
        "cdi": 2.2,
        "mmi": 2.538,
        "status": "reviewed",
        "tsunami": 0,
        "sig": 178,
        "net": "us",
        "types": ",dyfi,nearby-cities,origin,phase-data,scitech-link,shakemap,",
        "nst": 36,
        "dmin": 0.479,
        "rms": 0.65,
        "gap": 247,
        "magType": "ml",
        "type": "earthquake",
        "title": "M 3.4 - 153 km SSW of Channel Islands Beach, California",
        "coordinates": [
          -119.931,
          32.9103
        ]
      },
      {
        "mag": 2.25,
        "place": "6 km NW of The Geysers, CA",
        "time": 1765921522850,
        "status": "automatic",
        "tsunami": 0,
        "sig": 78,
        "net": "nc",
        "types": ",focal-mechanism,nearby-cities,origin,phase-data,",
        "nst": 54,
        "dmin": 0.01126,
        "rms": 0.05,
        "gap": 23,
        "magType": "md",
        "type": "earthquake",
        "title": "M 2.3 - 6 km NW of The Geysers, CA",
        "coordinates": [
          -122.792831,
          38.819332
        ]
      }
    ]
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
earthquakes_LastUpdatedstring2026-02-18T12:00:00.000Z
earthquakes_LastHournumber9
count24hnumber187Total earthquake count in the past 24 hours
largestMagnitude24hnumber5.2Largest earthquake magnitude in the past 24 hours
avgMagnitude24hPremiumnumber1.84Average earthquake magnitude in the past 24 hours
earthquakesarray[2]list of rows
earthquakes.0.magnumber3.4
earthquakes.0.placestring153 km SSW of Channel Islands Beach, California
earthquakes.0.timenumber1765921110756
earthquakes.0.feltnumber1
earthquakes.0.cdinumber2.2
earthquakes.0.mminumber2.538
earthquakes.0.statusstringreviewed
earthquakes.0.tsunaminumber0
earthquakes.0.signumber178
earthquakes.0.netstringus
earthquakes.0.typesstring,dyfi,nearby-cities,origin,phase-data,scitech-link,shakemap,
earthquakes.0.nstnumber36
earthquakes.0.dminnumber0.479
earthquakes.0.rmsnumber0.65
earthquakes.0.gapnumber247
earthquakes.0.magTypestringml
earthquakes.0.typestringearthquake
earthquakes.0.titlestringM 3.4 - 153 km SSW of Channel Islands Beach, California
earthquakes.0.coordinatesarray[-119.931,32.9103]

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Earthquake Data Skill

Set up Earthquake Data Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use EarthquakeDataSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?