Japan Parliament Search
REMOTE · KOKKAI-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 20
Search Japan's National Diet records (1947-present): statements, Q&A, and debates with citations.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, 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 & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Japan Parliament Search MCP server?
Japan Parliament Search is a hosted endpoint at https://kokkai-mcp.easakura.workers.dev/sse, 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 · kokkai-mcp.easakura.workers.dev
claude mcp add --transport http easakura-japan-parliament-search-mcp 'https://kokkai-mcp.easakura.workers.dev/sse'
{
"mcpServers": {
"easakura-japan-parliament-search-mcp": {
"url": "https://kokkai-mcp.easakura.workers.dev/sse"
}
}
} {
"servers": {
"easakura-japan-parliament-search-mcp": {
"type": "http",
"url": "https://kokkai-mcp.easakura.workers.dev/sse"
}
}
} [mcp_servers.easakura-japan-parliament-search-mcp] url = "https://kokkai-mcp.easakura.workers.dev/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"easakura-japan-parliament-search-mcp": {
"type": "remote",
"url": "https://kokkai-mcp.easakura.workers.dev/sse",
"enabled": true
}
}
} openclaw mcp add easakura-japan-parliament-search-mcp --url 'https://kokkai-mcp.easakura.workers.dev/sse' --transport streamable-http
mcp_servers:
easakura-japan-parliament-search-mcp:
url: "https://kokkai-mcp.easakura.workers.dev/sse" {
"McpServers": {
"easakura-japan-parliament-search-mcp": {
"Transport": "http",
"Url": "https://kokkai-mcp.easakura.workers.dev/sse"
}
}
} assistant mcp add easakura-japan-parliament-search-mcp -t streamable-http -u 'https://kokkai-mcp.easakura.workers.dev/sse'
{
"mcpServers": {
"easakura-japan-parliament-search-mcp": {
"type": "http",
"url": "https://kokkai-mcp.easakura.workers.dev/sse"
}
}
} 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.
- 7 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 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://kokkai-mcp.easakura.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easakura.workers.dev | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a7163aae2923cc020e1322b0e402e606 |
| SANs: easakura.workers.dev, *.easakura.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 kokkai-mcp.easakura.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 | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://kokkai-mcp.easakura.workers.dev/sse | HTTP error | 404 | |
| http (plaintext) | http://kokkai-mcp.easakura.workers.dev/sse | Inconclusive | 404 |
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 →
search_meetings 国会の会議（委員会・本会議）を検索 ~153
キーワードを含む国会の会議（本会議・委員会）単位で検索する。どの委員会でいつ議論されたかの全体像を掴むのに使う。個別の発言内容はsearch_speechesで取得する。
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | 開始日 YYYY-MM-DD |
| house | string | – | 院で絞り込み |
| max_results | integer | – | 最大件数（1〜10） |
| query | string | yes | 検索語（例: 生成AI / 補助金） |
| until | string | – | 終了日 YYYY-MM-DD |
No output schema declared.
No examples provided.
search_speeches 国会答弁・発言を検索 ~277
日本の国会会議録（1947年〜最新）から発言を全文検索する。大臣答弁・質疑・政府見解の一次資料を、発言者・院・会議名・期間で絞り込める。政策調査・報道・ロビイング・コンプライアンス確認に有用。デフォルトは発言の冒頭抜粋を返す。full_text=trueで発言全文を取得（長い場合がある）。
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | 開始日 YYYY-MM-DD |
| full_text | boolean | – | trueで発言全文を返す（既定は400字抜粋） |
| house | string | – | 院で絞り込み |
| max_results | integer | – | 最大件数（1〜10） |
| meeting | string | – | 会議名で絞り込み（例: 予算委員会） |
| query | string | yes | 検索語（例: 生成AI / インボイス / 防衛費） |
| speaker | string | – | 発言者名で絞り込み（例: 岸田文雄） |
| until | string | – | 終了日 YYYY-MM-DD |
No output schema declared.
No examples provided.
What is the Japan Parliament Search MCP server?
Japan Parliament Search is an MCP server listed in the public MCP registry as io.github.easakura/japan-parliament-search-mcp. Search Japan's National Diet records (1947-present): statements, Q&A, and debates with citations. This page covers its hosted endpoint (https://kokkai-mcp.easakura.workers.dev/sse).
Is the Japan Parliament Search MCP server safe to use?
Japan Parliament Search scores 18 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 Japan Parliament Search MCP server expose?
Japan Parliament Search exposes 2 tools: search_speeches, search_meetings. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.
Does the Japan Parliament Search MCP server require authentication?
No. We connected to Japan Parliament Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Parliament Search MCP server still maintained?
Japan Parliament Search 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.