Meta Data Mcp
Discover and lazily activate among 76 open data providers so agents can fetch government, science, finance, and environment facts on demand.
Overview
meta-data-mcp is a MCP server for the idea phase that queries 76 lazy-activated open data APIs through find, list, activate, and deactivate provider tools.
What is this MCP server?
- Single MCP façade over 76 open data APIs across government, science, finance, and environment
- Lazy activation: default tool surface stays small until you activate a provider
- opendata.providers.find for semantic, ranked provider search with health scores and domain tags
- opendata.providers.activate / deactivate to add or remove domain tools without server restart
- opendata.providers.list exposes full provider metadata for exploration
- 76 open data API providers
- Core tools: opendata.providers.find, activate, deactivate, list
- Lazy activation to limit default exposed tools
Community signal: 3 GitHub stars.
What problem does it solve?
Solo builders waste days wiring one-off HTTP clients to scattered public APIs when agents could answer data questions if routing and discovery were centralized.
Who is it for?
Builders running research-heavy validate loops, hackathon prototypes, or internal tools that need occasional authoritative public datasets.
Skip if: Teams needing a single commercial data vendor SLA, private paid market feeds only, or fully offline/air-gapped research with no HTTP providers.
What do I get? / Deliverables
You semantic-search providers, activate only what you need, and get structured open-data answers without restarting the server or bloating the default tool list.
- Ranked provider matches from semantic find queries
- Activated domain-specific open-data toolsets without server restart
- Structured API responses for research notes, charts, or validation docs
Recommended MCP Servers
Journey fit
Open-data discovery is the first canonical stop on the solo-builder journey when validating ideas with external evidence. Research is where you query macro indicators, incidents, and public records—not where you deploy production monitoring.
How it compares
Multi-provider open-data router MCP, not a single-domain skill or static CSV dump.
Common Questions / FAQ
Who is meta-data-mcp for?
Indie developers and agent users who want one MCP entry point to dozens of government and scientific APIs instead of custom integrations per source.
When should I use meta-data-mcp?
Use it during idea research, validate scoping with external stats, or grow analytics experiments whenever you need on-demand public datasets routed to the right API.
How do I add meta-data-mcp to my agent?
Install the server from its GitHub registry package per publisher instructions, register it in your MCP client, then call opendata.providers.find before opendata.providers.activate for the domain you need.