emsc.seismic.search
Search the European-Mediterranean Seismological Centre (EMSC) real-time seismicity catalog (EMSC-RTS) by time range, bounding box or point+radius, magnitude range, and depth range. A distinct regional network from USGS, often lower-latency for Euro-Mediterranean events, with per-event reporting-a...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/emsc.seismic.search.md
What emsc.seismic.search does on Apibase
AI agents call emsc.seismic.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum number of events to return, 1-200 (default 50). |
endtime | string | — | End of the time window, ISO 8601 date or datetime (e.g. 2026-08-27T23:59:59). Omit for no upper bound. |
latitude | number | — | Center latitude in decimal degrees for a point+radius search (use with longitude and maxradius). |
maxdepth | number | — | Maximum hypocenter depth in kilometers. |
mindepth | number | — | Minimum hypocenter depth in kilometers. |
longitude | number | — | Center longitude in decimal degrees for a point+radius search (use with latitude and maxradius). |
maxradius | number | — | Search radius in degrees around the latitude/longitude point (e.g. 5 for ~550km at the equator). |
starttime | string | — | Start of the time window, ISO 8601 date or datetime (e.g. 2026-08-01 or 2026-08-01T00:00:00). Omit for no lower bound. |
maxlatitude | number | — | Maximum latitude in decimal degrees for a bounding-box search (e.g. 45.0). |
minlatitude | number | — | Minimum latitude in decimal degrees for a bounding-box search (e.g. 34.0). |
maxlongitude | number | — | Maximum longitude in decimal degrees for a bounding-box search (e.g. 25.0). |
maxmagnitude | number | — | Maximum earthquake magnitude to include (e.g. 7.0). |
Parameters from the server's own tool schema.
Why emsc.seismic.search is rated Low
Queries seismic event data without side effects or modification capabilities.
From the tool's definition Search catalog, returns event ID, time, magnitude, location, depth, region name.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs emsc.seismic.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For emsc.seismic.search, this is the rule to start with:
emsc.seismic.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every emsc.seismic.search call is checked against it from then on.
Questions about emsc.seismic.search
Search the European-Mediterranean Seismological Centre (EMSC) real-time seismicity catalog (EMSC-RTS) by time range, bounding box or point+radius, magnitude range, and depth range. A distinct regional network from USGS, often lower-latency for Euro-Mediterranean events, with per-event reporting-agency attribution. Returns event ID, time, magnitude, location, depth, region name, and reporting agency for each match. Data: seismicportal.eu (EMSC), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
emsc.seismic.search accepts 12 parameters: limit, endtime, latitude, maxdepth, mindepth, longitude, maxradius, starttime, maxlatitude, minlatitude, maxlongitude, maxmagnitude. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for emsc.seismic.search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
emsc.seismic.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the emsc.seismic.search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for emsc.seismic.search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
emsc.seismic.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue