Search the meta-data-mcp plugin registry. Returns plugins that match a free-text query and/or domain/region filters. Use this FIRST when you don't know which plugin can answer a question. If no plugin matches, the response includes a next_step field that explains how to autonomously create one via opendata_plugins_create.

Autonomously create a new plugin for this meta-data-mcp server from a YAML spec. Use this when opendata_providers_find returned no match. Recommended flow: first call opendata_plugins_draft with structured fields to get a valid YAML spec, then pass it here. The new plugin is materialized to disk, imported, registered in the live registry, and its tools become available immediately. On success this also opens a public contribution PR of the generated plugin to the project so others can use it; set META_DATA_MCP_AUTO_CONTRIBUTE=0 to disable.

Build a validated YAML plugin spec from structured inputs. Use this BEFORE opendata_plugins_create to avoid hand-writing YAML. Validates id format, kebab-case tool names, path-placeholder/param consistency, parameter types, and response format. Returns the YAML string ready to feed into opendata_plugins_create.

Explain the scoring breakdown for a provider search. Shows how each provider was ranked using token matching, fuzzy matching, semantic similarity, and metadata filters.

List the controlled domain vocabulary used by the provider registry (e.g. 'health', 'legal', 'finance', 'earth-science').

List the controlled region vocabulary used by the provider registry (e.g. 'us', 'eu', 'uk', 'global').

Fetch the full registry entry for a single provider id — title, description, domains, regions, keywords, homepage, license note, required environment variables.

Enumerate all providers in the opendata-mcp registry (paginated, terse). Returns id, title, domains, regions, and any required env vars per provider.

Activate a registered provider so its tools become callable in this session. By default the server starts in discovery-only mode — only meta tools (find-providers, list-providers, etc.) are advertised. Activation imports the plugin module and merges its tools into the advertised list, then sends a tools/list_changed notification so the client refetches its catalog. Idempotent.

Remove a previously-activated provider's tools from the session's advertised list. The Python module remains imported (Python caches modules) but its tools no longer appear in tools/list. A tools/list_changed notification is sent so the client refetches.

List the providers currently activated in this session, along with the tool names each contributes. Useful for inspecting why a particular tool is (or isn't) advertised.

Snapshot the in-memory provider health registry. Returns a score in [0.0, 1.0] for each requested provider (or every registered provider when called without arguments). Health degrades on recent 5xx / 429 / network failures and decays back toward 1.0 over ~5 minutes; 401/403 are excluded as caller misconfig. The discovery app uses this to paint live health badges next to each search result.

Proxy any activated plugin tool by name. Use this when dynamically activated tools aren't directly callable in your environment. First activate the provider with opendata_providers_activate, then call this tool with the tool name and arguments from the activation response's tool_schemas field.

Run several plugin tool calls, normalize their results onto a common geography + time axis, and merge them into one cited series. Auto-activates each query's provider. Use this to overlay the same indicator from different open-data sources (e.g. Eurostat vs World Bank) in a single answer.

Federate several plugin tool calls and report a coverage matrix — which sources cover which geographies and periods — alongside the merged series. Use this to spot gaps or disagreements between open-data sources.