DaedalMap Earthquake Data
Server Details
Global earthquake events from the USGS, 2150 BC-present: magnitude, depth, location, counts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- xyver/daedal-map
- GitHub Stars
- 3
- Server Listing
- daedal-map
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 7 of 7 tools scored. Lowest: 3.4/5.
Each tool has a clearly distinct purpose: catalog discovery, pack metadata, canonical earthquake events (paid), live earthquake events (free), and three cross-disaster linking tools. The descriptions explicitly state when to use each, eliminating ambiguity.
All tools follow a consistent verb_noun pattern (e.g., get_catalog, get_earthquake_events, search_disaster_links). The naming is predictable and clearly indicates the action and resource.
With 7 tools, the server covers discovery, earthquake queries (two variants), and cross-disaster linking. The scope is well-scoped; each tool serves a specific purpose without superfluous additions.
The tool set covers the main workflows: catalog discovery, pack metadata, earthquake queries (canonical and live), and cross-disaster exploration. A minor gap is the lack of a direct tool to retrieve a single earthquake event by ID, though filtering in get_earthquake_events likely covers it.
Available Tools
7 toolsget_catalogGet CatalogRead-onlyInspect
Free discovery. Returns the list of live agent-ready data packs available on DaedalMap.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_disaster_link_chainGet Disaster Link ChainRead-onlyInspect
Free linked-disaster helper. Expands one exact disaster event id into a bounded related-event chain. Use this only when you already have an exact event id from a supported pack such as earthquakes, tsunamis, volcanoes, or wildfires.
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | Maximum link-chain depth to traverse. Default 1. | |
| pack_id | No | Optional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires. | |
| event_id | Yes | Exact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| cross_type_only | No | When true, only return cross-hazard links. Default true. |
get_disaster_links_for_eventGet Disaster Links For EventRead-onlyInspect
Free linked-disaster helper. Resolves one exact disaster event id into its published related-disaster links. Use this only when you already have an exact event id from a supported pack such as earthquakes, tsunamis, volcanoes, or wildfires.
| Name | Required | Description | Default |
|---|---|---|---|
| pack_id | No | Optional pack id hint when the event id is ambiguous. Supported exact-event link packs are earthquakes, tsunamis, volcanoes, and wildfires. | |
| event_id | Yes | Exact disaster event id from a supported pack row, such as 'NOAA-SIG-2' or 'USA-CA-FIRE-215'. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| cross_type_only | No | When true, only return cross-hazard links. Default true. |
get_earthquake_eventsGet Earthquake EventsRead-onlyInspect
Paid x402 canonical tool. Queries the published earthquakes_events lane. Use this first for earthquake questions because it is the enriched DaedalMap history lane with stable loc_id geography, not the preliminary upstream wrapper. Call without payment first - the server returns HTTP 402 with the exact USDC price before any charge. Small queries stay cheap; broad scans cost more or need narrower filters.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Optional sort instructions for row-returning queries. | |
| limit | No | Maximum number of rows to return. For top-N requests, include a narrow time range or region_ids before sorting. | |
| output | No | Optional output controls such as response format hints. | |
| filters | Yes | Structured filters including time ranges, region_ids, and compare clauses. | |
| metrics | Yes | Metric ids to return, such as 'event_count' or event attributes like 'magnitude'. | |
| request_id | No | Optional caller-supplied request id for tracing and idempotency. |
get_live_earthquake_eventsGet Live Earthquake EventsRead-onlyInspect
Free live wrapper. Calls the USGS FDSN API for recent preliminary earthquake events normalized to DaedalMap event fields. Use this only when the caller explicitly wants live/preliminary upstream results or needs a very recent window not yet present in the published canonical earthquake lane. This is not the enriched canonical history lane.
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | Recent lookback window in hours. Ignored when start_time is provided. | |
| limit | No | Maximum live rows to return. | |
| orderby | No | USGS result ordering. | |
| end_time | No | Optional exclusive-ish ISO-8601 end datetime. Defaults to now. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| start_time | No | Optional inclusive ISO-8601 start datetime. | |
| max_latitude | No | Optional bounding box maximum latitude. | |
| min_latitude | No | Optional bounding box minimum latitude. | |
| max_longitude | No | Optional bounding box maximum longitude. | |
| min_longitude | No | Optional bounding box minimum longitude. | |
| min_magnitude | No | Minimum earthquake magnitude. Defaults to 2.5. |
get_packGet PackRead-onlyInspect
Free discovery. Returns detailed metadata, coverage, freshness, preferred canonical tool guidance, and first-query examples for one pack. Call this before querying a new pack so you can see time shape, coverage limits, and the paste-ready first query.
| Name | Required | Description | Default |
|---|---|---|---|
| pack_id | Yes | Pack identifier such as 'currency', 'earthquakes', 'floods', 'hurricanes', 'tornadoes', 'tsunamis', 'un_sdg', 'volcanoes', 'world_factbook', or 'worldpop'. |
search_disaster_linksSearch Disaster LinksRead-onlyInspect
Free linked-disaster discovery helper. Searches published cross-disaster link families by event-type direction, optional via-event type, and optional year window. Use this when you want to discover whether a relationship family exists before you have an exact event id.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of matching chains to return. Default 10. | |
| year_end | No | Optional inclusive ending year filter. | |
| request_id | No | Optional caller-supplied request id for tracing. | |
| year_start | No | Optional inclusive starting year filter. | |
| end_event_type | No | Optional ending event type such as tsunami, flood, tornado, or earthquake. | |
| via_event_type | No | Optional intermediate event type for bounded chain discovery. | |
| start_event_type | No | Optional starting event type such as earthquake, hurricane, volcano, wildfire, flood, tornado, or tsunami. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.