One interface for people and machines

The website, REST API and MCP tools read the same stored records. USGS earthquakes, MET Norway forecasts and NOAA SWPC estimates keep their original sources and timestamps. Public read access is available without an account or API key.

Start with a useful question

Inspect earthquake JSON ↗ · GeoJSON ↗ · Source health ↗

MCP tools that return data

Connect to https://ursy.live/wp-json/ursy-mcp/v1/mcp. The stateless endpoint uses JSON-RPC over HTTP POST and supports MCP 2025-06-18 and 2025-03-26 with JSON responses. It offers 17 read-only tools, four resources and two resource templates. Streaming subscriptions are not offered.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_earthquakes","arguments":{"hours":24,"min_magnitude":4.5,"limit":20}}}

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"your-client","version":"1.0"}}}

{"jsonrpc":"2.0","method":"notifications/initialized"}

{"jsonrpc":"2.0","id":2,"method":"tools/list"}

{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_forecast","arguments":{"place":"paris","limit":24}}}

{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"get_planetary_kp","arguments":{"limit":60}}}

URSY ID and account access

Live’s public APIs read the same Earth and space records as this website. Saved places and appearance preferences stay in your browser; Live currently has no customer workspace or private account API.

For a central URSY account, use URSY ID’s hosted account pages and account and agent guide. ID supports verified account setup through https://ursy.id/api/registrations, device authorization and hosted sign-in with PKCE S256. Use ID’s current resource policy and least-privilege scopes for https://ursy.id/api. Account setup needs email verification and hosted approval; registering an agent application does not verify a person. Your password stays on ID.

An ID account token does not unlock private Live resources. Read Live’s machine-readable identity and account scope, or inspect ID’s approved resources and permissions.

Access and sensible polling

Read-only REST and MCP requests are public. No account, API key or preview header is needed. Use a descriptive User-Agent for your application, cache results appropriately and follow the response pagination links.

curl 'https://ursy.live/wp-json/ursy-live/v1/status'

curl 'https://ursy.live/wp-json/ursy-mcp/v1/mcp' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Collection runs every five minutes and respects provider forecast expiry. Polling faster does not create newer observations. REST event pages contain at most 500 records, over intervals of at most 30 days. Change pages contain at most 100 revisions. MCP responses are bounded to 256 KB; narrow a query or use REST paging when a result is too large.

REST allows 240 requests per five minutes, with a 60-request minute burst. MCP allows 120 requests per five minutes, with a 30-request minute burst. Both are per client address. Honour 429 and Retry-After.

Read the evidence correctly

observed_at describes an earthquake observation; forecast point time describes when a forecast is valid. Source issue time, source revision time and collection time have separate meanings. Check stale flags and source health. Unknown measurements remain null, and no matching records is different from unavailable data.

The initial earthquake feed covers seven days; records collected by this installation are retained for thirty. The version history contains only revisions URSY actually collected. An expired cursor returns 410; rebuild from retained records and restart the changes stream. Omission from a rolling feed does not establish that an event was cancelled.

The API currently covers twelve reference forecast cities. Global geocoding, fire, ocean and satellite feeds are not connected. Original provider licences and attribution apply. Read the methodology and inspect the sources.

TEAS.co.uk sponsors this service. The shared runtime adds a clearly labelled paid sponsor sign-off after the data; it does not replace original source credit. Service protection and privacy.