Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Japan Parliament Search

REMOTE · KOKKAI-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3

Search Japan's National Diet records (1947-present): statements, Q&A, and debates with citations.

0 this week 55 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security46
Transport & Reachability40
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 430 tokens (~215/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · kokkai-mcp.easakura.workers.dev

# add to Claude Code
claude mcp add --transport http easakura-japan-parliament-search-mcp https://kokkai-mcp.easakura.workers.dev/sse
# ~/.codex/config.toml
[mcp_servers.easakura-japan-parliament-search-mcp]
url = "https://kokkai-mcp.easakura.workers.dev/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "easakura-japan-parliament-search-mcp": {
      "type": "remote",
      "url": "https://kokkai-mcp.easakura.workers.dev/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add easakura-japan-parliament-search-mcp --url https://kokkai-mcp.easakura.workers.dev/sse --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  easakura-japan-parliament-search-mcp:
    url: "https://kokkai-mcp.easakura.workers.dev/sse"
// mcp.json
{
  "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.

Changelog

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.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 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
  • 30 Jul 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 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
  • 26 Jul 26 55

    First indexed and scored.

Diagnostics

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 3 Aug 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 13 Jul 2026 11 Oct 2026 ECDSA 256 ECDSA-SHA256 997e95d4e676a1e20e6b46db6f16ffd5
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
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
Transports 2 probes
Transport URL Outcome Status Location
sse https://kokkai-mcp.easakura.workers.dev/sse Verified 200
http (plaintext) http://kokkai-mcp.easakura.workers.dev/sse Served over HTTP 200
MCP tools — 2 exposed · ~430 tokens

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.

Tool Tokens
search_meetings ~153

キーワードを含む国会の会議(本会議・委員会)単位で検索する。どの委員会でいつ議論されたかの全体像を掴むのに使う。個別の発言内容はsearch_speechesで取得する。

NameTypeReqDescription
fromstring開始日 YYYY-MM-DD
housestring院で絞り込み
max_resultsinteger最大件数(1〜10)
querystringyes検索語(例: 生成AI / 補助金)
untilstring終了日 YYYY-MM-DD

No output schema declared.

No examples provided.

search_speeches ~277

日本の国会会議録(1947年〜最新)から発言を全文検索する。大臣答弁・質疑・政府見解の一次資料を、発言者・院・会議名・期間で絞り込める。政策調査・報道・ロビイング・コンプライアンス確認に有用。デフォルトは発言の冒頭抜粋を返す。full_text=trueで発言全文を取得(長い場合がある)。

NameTypeReqDescription
fromstring開始日 YYYY-MM-DD
full_textbooleantrueで発言全文を返す(既定は400字抜粋)
housestring院で絞り込み
max_resultsinteger最大件数(1〜10)
meetingstring会議名で絞り込み(例: 予算委員会)
querystringyes検索語(例: 生成AI / インボイス / 防衛費)
speakerstring発言者名で絞り込み(例: 岸田文雄)
untilstring終了日 YYYY-MM-DD

No output schema declared.

No examples provided.