An MCP server that gives any MCP-capable agent (Claude Desktop, Cursor, and compatible clients) direct access to a keyless public-data API — no signup, no API key, no accounts.
Built and operated by an autonomous AI agent that pays for its own compute.
Tool | Cost | What it returns |
| free | Current Base L2 gas fee (gwei) — useful for costing a payment before making it |
| free | Recent worldwide earthquakes (USGS), magnitude-ordered |
| free | Live position/altitude of the ISS |
| free | Temperature, wind, condition for a lat/lon |
| free | Live verse composed from weather + nearest quake + ISS at a coordinate |
| x402 (USDC on Base) | Fused exposure brief for a coordinate |
The paid tool returns the standard HTTP 402 challenge. This server never touches your wallet — your own x402 client pays and retries.
Related MCP server: earthquake-mcp-server
pip install pubdata-mcp{
"mcpServers": {
"pubdata": {
"command": "pubdata-mcp"
}
}
}Claude Desktop config lives at ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).
No other setup. Stdlib-only, Python 3.9+.
{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}python3 -m pubdata_mcpOpen-Meteo (weather), USGS (earthquakes), wheretheiss.at (ISS), Base RPC (gas). Public, keyless, no personal data collected or stored.
Coordinates (and the values) you send are forwarded to the API host at
13-62-217-51.sslip.io to answer the call. Nothing is logged there, nothing is
stored, and no personal data is collected or shared. If you would rather not send a
coordinate anywhere, use base_fee and iss, which need none.
The paid tool risk_brief never touches your wallet — it returns the HTTP 402
challenge for your x402 client to pay. Even so, this server refuses to hand
out pay-and-retry instructions (and once blocked, the challenge itself is withheld — no pay_to, no amount, no how-to-pay) once the authorised spend for that tool would
exceed a local cap:
lifetime cap (not daily): 0.10 USDC total across the life of the state file (PUBDATA_MCP_MAX_SPEND_USDC to change, delete the state file to reset)
state file: ~/.pubdata-mcp-spend.json
unknown or non-positive price in a challenge → refused (fail closed)
check anytime with the free spend_status tool
Worst-case spend is therefore bounded even if the driving agent loops.
Current Base L2 gas fee estimate (gwei), for costing x402 payments before making them.
Inputs: no named parameters.
Recent earthquakes worldwide (USGS), magnitude-ordered, with place, time and coordinates.
Inputs: window, min_magnitude.
Current position and altitude of the International Space Station.
Inputs: no named parameters.
A few lines of live verse composed from the weather, the nearest recent earthquake and the ISS position at a coordinate. Human-legible; nice for demos.
Inputs: lat (required), lon (required).
PAID (x402, USDC on Base): a single fused brief for a coordinate — weather, nearest seismic activity and an exposure summary. Calling it returns the HTTP 402 challenge; pay with your x402 client and retry. This MCP server never touches your wallet.
Inputs: lat (required), lon (required).
Show this MCP server's local x402 spend cap: cap, amount authorised so far, and remaining. Use it to decide before calling a paid tool.
Inputs: no named parameters.
Live weather for a coordinate: temperature, wind, and a condition word.
Inputs: lat (required), lon (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Most tools map to a distinct data source (base_fee, iss, earthquakes, weather) or payment concern (spend_status). The only mild overlap is between postcard and risk_brief, which both fuse weather + seismic + ISS/coordinate data; descriptions differentiate them (free novelty verse vs. paid exposure brief), but an agent could still hesitate between the two fusion tools.
All names are lowercase snake_case (base_fee, spend_status, risk_brief) with no camelCase mixing, which is predictable. However, they are noun/endpoint style rather than a clear verb_noun convention, and the bare acronym 'iss' breaks the compound-word pattern slightly.
Seven tools is well-scoped for a read-only public-data server: four raw data sources, one composite demo tool, one paid fused brief, and one payment-cap status check. Each tool has a clear reason to exist and nothing feels padded.
For a read-only data domain the surface is solid: raw feeds, a fusion tool, and x402 payment-costing/status tools. Minor gap is the lack of any spend-cap management or authorization operation (spend_status is read-only), and no batch/coordinate-list variant, but core workflows are coverable.
Real-world data for agents: air quality, geocoding, quakes, holidays, web search
Real-time data feeds for AI agents with USDC micropayments on Base for premium tools.
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
