pubdata-mcp
Related Servers
Alternatives to pubdata-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenance62 live, cryptographically signed data tools for AI agents and robots: weather, natural hazards, flights, shipping, space, CVEs, sanctions, software versions, sea ice and more. Every datapoint carries source, licence, timestamp and an Ed25519 signature.13 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query live space weather, aurora forecasts, earthquake feeds, and the Helios Oracle over HTTPS with no API keys.MIT
- FlicenseAqualityDmaintenanceExposes live earth-science data (e.g., earthquakes from USGS) as tools for MCP-compatible AI agents, enabling them to fetch and reason about real-time geophysical events.1-
- AlicenseAqualityDmaintenanceReal-time earthquake data and seismic monitoring for AI agents via the USGS Earthquake Catalog API.8MIT
- AlicenseAqualityBmaintenanceProvides US weather forecasts, current conditions, alerts, earthquakes, elevation, and geocoding via keyless US-government data feeds. Enables AI agents to access real-time weather and geospatial data without API keys.6MIT

OmniScope MCP Suiteofficial
AlicenseNot gradedqualityBmaintenanceEnables LLMs and autonomous agents to access live global weather consensus, storm and seismic monitoring, space weather, webcam search, and tactical SITREP generation, plus sub-5ms local queries across 1M+ spatial sensor nodes in SQLite.MIT
TDQS
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.