mcp-fdsnws-event
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fdsn_query_earthquakesA | Query earthquake events from an FDSN datacenter with flexible parameters. Returns a compact tabular result (columns + rows), one row per event, using the preferred origin and magnitude. Depth is in KILOMETERS. For the full detail of a single event (all origins/magnitudes, arrivals, focal mechanism) use the by-id tools. Common usage examples:
Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy. |
| fdsn_get_earthquake_by_idA | Get basic information about a specific earthquake event by event ID. Returns the preferred origin, preferred magnitude, station magnitudes, and amplitudes. For detailed data (all alternative origins, all alternative magnitudes, or seismic arrivals/picks), use the specialized tools instead. The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values. Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy. |
| fdsn_get_arrivals_by_idA | Get all seismic phase arrivals for an earthquake event, including linked pick data (station, time, phase). Use this when asked about recorded phases, station readings, or seismic wave arrivals. The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values. Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy. |
| fdsn_get_allmagnitudes_by_idA | Get all computed magnitude solutions for an earthquake event. Use this when asked about different magnitude types (ML, Mw, Mb, Md), magnitude comparisons across agencies, or station counts. The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values. Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy. |
| fdsn_get_allorigins_by_idA | Get all computed origin solutions (hypocenter locations) for an earthquake event. Use this when asked about alternative locations, origin comparisons, or which agencies computed origins. The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values. Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy. |
| fdsn_get_focalmechanism_by_idA | Get focal mechanism and moment tensor data for an earthquake event. Returns nodal planes (strike, dip, rake), principal axes (T, P, N), and moment tensor components when available. Use this for understanding the rupture geometry and seismic source characteristics. The eventid is an opaque, provider-specific string and MUST be copied verbatim from a prior fdsn_query_earthquakes result (EventID column). Never invent, guess, reformat, or use placeholder values. Available datacenters: INGV (default), EMSC, GFZ, USGS, and others supported by ObsPy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/INGV/mcp-fdsnws-event'
If you have feedback or need assistance with the MCP directory API, please join our Discord server