Query 76 open data APIs — government, science, finance, environment, and more.
A single MCP server that transparently routes user requests to 83 open-data sources. is one MCP server — not many. Under the hood it bundles 83 plugins, each wrapping a different open-data API. The plugins are an implementation detail; from your LLM's perspective there is one server and one place to ask "where can I find data about X?" You install one server. You get all the data, discoverable…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A single MCP server that transparently routes user requests to 83 open-data sources. is one MCP server — not many. Under the hood it bundles 83 plugins, each wrapping a different open-data API. The plugins are an implementation detail; from your LLM's perspective there is one server and one place to ask "where can I find data about X?" You install one server. You get all the data, discoverable through built-in routing tools. Finding open data isn't the hard part — there's an absurd amount of it…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.