INDIVIDUAL MCP TOOL
search_entries
Search the verified register of official European public-data APIs, datasets and portals.
LIVE ENDPOINT
https://c0mm0.com/mcp
Connect to this endpoint to inspect the live schema for search_entries and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.c0mm0-register]
url = "https://c0mm0.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"c0mm0-register": {
"type": "http",
"url": "https://c0mm0.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: c0mm0-register
Remote MCP URL: https://c0mm0.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"c0mm0-register": {
"url": "https://c0mm0.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"c0mm0-register": {
"type": "http",
"url": "https://c0mm0.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "c0mm0-register",
"transport": "streamable-http",
"url": "https://c0mm0.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_entry— One entry's full record: metadata, license, verification state, and the Access Contract — a ranked list of actionable URLs (direct downloads, verified runnable requests, specs).related_entries— An entry's graph neighborhood: containment relations (portal ⊃ dataset, service → dataset), same-publisher siblings, and the join-key identifiers its fields carry (with fan-out counts).find_joinable_sources— Every register source whose data carries a given join-key identifier (e.g.plan_query— PLAN a query WITHOUT running it: which source it would hit, the exact upstream request, how many requests, roughly how long (from that source's own measured latency, or null when nothing has been measured — never a guess), which fields would NOT resolve, and which filters cannot be pushed upstream and would be applied locally over a bounded window.run_query— RUN a query against a live-tier source and get real rows back, with the exact upstream request used.cite_query— CITE a query: run it and persist an immutable evidence manifest (query spec, upstream request, retrieval time, result hash, license).subscribe_to_changes— SUBSCRIBE to a source: returns its change-feed URL (RSS, no account needed) plus the recent change events — verification failures, schema changes, deprecation.