Public Data Catalog
REMOTE · PUBLIC-DATA-CATALOG-MCP.YUSUKE8H.WORKERS.DEV · SCANNED SEP 20
Reviewed public-data search and execution with provenance and verifiable integrity receipts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 166 tokens (~55/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Public Data Catalog MCP server?
Public Data Catalog is a hosted endpoint at https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · public-data-catalog-mcp.yusuke8h.workers.dev
claude mcp add --transport http yhay81-public-data-catalog 'https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp'
{
"mcpServers": {
"yhay81-public-data-catalog": {
"url": "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp"
}
}
} {
"servers": {
"yhay81-public-data-catalog": {
"type": "http",
"url": "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp"
}
}
} [mcp_servers.yhay81-public-data-catalog] url = "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yhay81-public-data-catalog": {
"type": "remote",
"url": "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add yhay81-public-data-catalog --url 'https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp' --transport streamable-http
mcp_servers:
yhay81-public-data-catalog:
url: "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp" {
"McpServers": {
"yhay81-public-data-catalog": {
"Transport": "http",
"Url": "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp"
}
}
} assistant mcp add yhay81-public-data-catalog -t streamable-http -u 'https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp'
{
"mcpServers": {
"yhay81-public-data-catalog": {
"type": "http",
"url": "https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Sept 26 +3
- Stability: fail → pass ▲ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- Stability: 0.27 → fail ▼ security
- Tool “search_data” rewrote its description, which is the text the model reads security
- Schema quality: 49 → 55 ▼ functional
- “search_data” made “query” required, so existing callers break ▼ functional
- Tool coverage: 14% → 33% ▲ functional
- Schema quality: fair → poor functional
- Server version: 0.4.0 → 0.6.0 functional
- “search_data” added an optional parameter “kind” cosmetic
- “search_data” reworded the description of “query” cosmetic
- “search_data” dropped the optional parameter “domain” cosmetic
- “search_data” dropped the optional parameter “sourceId” cosmetic
- Tool “search_data” changed its title: Search reviewed public data → Search Japanese public datasets cosmetic
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yusuke8h.workers.dev | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a85ba7bf54cf9e4d0e96e97f5f4de07c |
| SANs: yusuke8h.workers.dev, *.yusuke8h.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of public-data-catalog-mcp.yusuke8h.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://public-data-catalog-mcp.yusuke8h.workers.dev/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
execute Execute a reviewed retrieval contract ~43
Run one allowlisted, bounded HTTPS GET contract and return extracted values, provenance, and an integrity receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | – | – |
| recipeId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| elapsed_ms | integer | yes | – |
| interpretation | array | yes | – |
| parameters | object | yes | – |
| provenance | object | yes | – |
| question | object | yes | – |
| receipt | object | yes | – |
| recipe_id | string | yes | – |
| request_url | string | yes | – |
| results | object | yes | – |
| retrieved_at | string | yes | – |
| status | string | yes | – |
No examples provided.
search_data Search Japanese public datasets ~80
Search current metadata from e-Gov Data Portal and Statistics Dashboard, then return a short ranked list with publisher, formats, coverage, usage terms, and official links.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Search all sources, downloadable datasets, or statistical series |
| limit | integer | – | – |
| query | string | yes | What data to find, preferably in Japanese |
| Name | Type | Req | Description |
|---|---|---|---|
| available | object | yes | – |
| interpreted_as | array | yes | – |
| note | string | yes | – |
| query | string | yes | – |
| results | array | yes | – |
| searched_at | string | yes | – |
| sources | array | yes | – |
| status | string | yes | – |
| total | integer | yes | – |
No examples provided.
verify Verify an execution receipt ~43
Check receipt and result hashes plus the execution envelope against the reviewed catalog. This detects later modification; it does not prove publisher authenticity or current freshness.
| Name | Type | Req | Description |
|---|---|---|---|
| execution | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | yes | – |
| receipt_id | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
What is the Public Data Catalog MCP server?
Public Data Catalog is an MCP server listed in the public MCP registry as io.github.yhay81/public-data-catalog. Reviewed public-data search and execution with provenance and verifiable integrity receipts. This page covers its hosted endpoint (https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp).
Is the Public Data Catalog MCP server safe to use?
Public Data Catalog scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Public Data Catalog MCP server expose?
Public Data Catalog exposes 3 tools: search_data, execute, verify. Their descriptions and schemas cost roughly 166 tokens of context every time the server is loaded.
Does the Public Data Catalog MCP server require authentication?
No. We connected to Public Data Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Public Data Catalog MCP server still maintained?
Public Data Catalog is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.