New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

p2pquake.seismic.recent_quakes

Get recent earthquake reports issued by the Japan Meteorological Agency (JMA) via the P2PQuake network. Returns seismic events with epicenter name, coordinates, depth, Richter magnitude, maximum JMA intensity (Shindo scale 1–7), tsunami advisory status, and per-prefecture/city observation points....

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 90 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/p2pquake.seismic.recent-quakes.md

What p2pquake.seismic.recent_quakes does on Apibase

AI agents call p2pquake.seismic.recent_quakes 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.

ParameterTypeRequiredDescription
limit integer — Number of events to return (default 10, max 100)
order integer — Sort direction: -1 for newest-first (default), 1 for oldest-first
offset integer — Pagination offset (0-based, default 0)
max_scale integer — Maximum JMA seismic intensity as raw scale value (same scale as min_scale)
min_scale integer — Minimum JMA seismic intensity as raw scale value (10=Shindo1, 20=Shindo2, 30=Shindo3, 40=Shindo4, 45=Shindo4+, 50=Shindo5w, 55=Shindo5s, 60=Shindo6w, 65=Shindo6
prefecture integer — Filter by Japanese prefecture JIS code (1=Hokkaido, 13=Tokyo, 27=Osaka, 40=Fukuoka, 47=Okinawa)
quake_type string — JMA report type filter: ScalePrompt=intensity prompt, Destination=epicenter info, DetailScale=full epicenter+intensity report, Foreign=overseas earthquake, Othe
max_magnitude number — Maximum earthquake magnitude (Richter scale)
min_magnitude number — Minimum earthquake magnitude (Richter scale, e.g. 5.0 for moderate earthquakes)

Parameters from the server's own tool schema.

Why p2pquake.seismic.recent_quakes is rated Low

Tool only retrieves and returns publicly available earthquake data with no side effects.

From the tool's definition Get recent earthquake reports... Returns seismic events

Questions about p2pquake.seismic.recent_quakes

What does the p2pquake.seismic.recent_quakes tool do? +

Get recent earthquake reports issued by the Japan Meteorological Agency (JMA) via the P2PQuake network. Returns seismic events with epicenter name, coordinates, depth, Richter magnitude, maximum JMA intensity (Shindo scale 1–7), tsunami advisory status, and per-prefecture/city observation points. Filter by minimum/maximum seismic intensity, magnitude, prefecture (JIS code 1–47), or report type. Sort newest-first (default) or oldest-first. JMA intensity scale: 10=Shindo1, 20=Shindo2, ..., 60=Shindo6w, 65=Shindo6s, 70=Shindo7. Tsunami status: None | Checking | NonEffective | Watch | Warning. Data source: P2PQuake — community-operated JMA relay, open data, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does p2pquake.seismic.recent_quakes accept? +

p2pquake.seismic.recent_quakes accepts 9 parameters: limit, order, offset, max_scale, min_scale, prefecture, quake_type, max_magnitude, min_magnitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on p2pquake.seismic.recent_quakes? +

Register the Apibase MCP server in PolicyLayer and add a rule for p2pquake.seismic.recent_quakes: 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.

What risk level is p2pquake.seismic.recent_quakes? +

p2pquake.seismic.recent_quakes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit p2pquake.seismic.recent_quakes? +

Yes. Add a rate_limit block to the p2pquake.seismic.recent_quakes 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.

How do I block p2pquake.seismic.recent_quakes completely? +

Set action: deny in the PolicyLayer policy for p2pquake.seismic.recent_quakes. 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.

What MCP server provides p2pquake.seismic.recent_quakes? +

p2pquake.seismic.recent_quakes 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.