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

Japan Diet Bill Tracker

REMOTE · JP-DIET-PRODUCTION.MK-CAREER-PLANNING.WORKERS.DEV

Where is a bill in Japan's Diet now? Stages, dates, laws it amends and when, with source URLs.

69 Trust /100

Last scanned (14 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 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 → 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1467 tokens (~146/item across 10 items; 10 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 Management20
  • Stability observed for 6 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 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.

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 66

    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 21 Nov 2026 · Probed https://jp-diet-production.mk-career-planning.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=mk-career-planning.workers.dev CN=YE2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA384 62a608d12f78fd3a8d88d692f2a2cd87fd3
SANs: *.mk-career-planning.workers.dev, mk-career-planning.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jp-diet-production.mk-career-planning.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://jp-diet-production.mk-career-planning.workers.dev/mcp Verified 200
http (plaintext) http://jp-diet-production.mk-career-planning.workers.dev/mcp Inconclusive 405
MCP tools · 10 exposed · ~1,467 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. 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 →

Tool Tokens
catalog ~27

List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

Input schema present but exposes no named parameters.

NameTypeReqDescription
daily_limitsobjectyesDaily limits of paid calls (calls, usd, timezone) or a misconfiguration notice.
fetch_status_valuesobject––
legalobjectyes–
pausedobjectyesOperator pause flags (true = paused).
paymentobjectyes–
provenancearray–Freshness receipts for every upstream source used.
serverobjectyes–
termsstringyesURL of the terms of service.
toolsarrayyesEvery tool of this server with its price.

No examples provided.

get_receipt ~83

Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 30 days after settlement.

NameTypeReqDescription
receipt_idstringyesThe receipt_id returned with a paid result ("rcpt_" + 64 hex characters).
NameTypeReqDescription
paymentobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
receipt_idstringyesReceipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt.
result–yesThe stored result, exactly as returned by the paid call.
settled_atstring|nullyes–
termsstringyesURL of the terms of service.
toolstringyesName of the paid tool that produced the result.

No examples provided.

jp_diet_bill_status ~198

Where is this Diet bill now and how did it get there? Give bill_id (e.g. 222-閣法-1 or 222-cabinet-1) or a title. Returns status, position and the timeline per session and house (referral, committee and plenary decisions, promulgation), each with date, source URL and first observed time; the Diet meetings that dealt with the bill (house, meeting, date, official record link); for cabinet bills the cabinet decision date and page. Each block has a status. Free.

NameTypeReqDescription
bill_idstring–Bill id: submitted session, kind and number, for example 222-閣法-1, 222-cabinet-1, 221-hr-1, 222-hc-2
titlestring–Bill title or part of it, in Japanese (used when bill_id is not given)
NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
bill–yes–
cabinet_decisionobject–Cabinet decision of a cabinet bill from the Prime Minister's Office agenda pages (PDL1.0; keep the source line).
candidatesarrayyes–
disclaimerstringyes–
meetingsobject–Diet meetings whose record contains the bill title (meeting-level data and links only; no speeches, no speaker names).
official_checkobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
queryobjectyes–
sourceobjectyesWhere the answer comes from and how fresh it is.
statusstringyes–
status_notestringyes–
termsstringyesURL of the terms of service.
unknown_reasonstring|nullyes–

No examples provided.

jp_diet_bills_list ~285

List the law bills of a Diet session (default: current; past sessions from 142 (1998) as loaded, see jp_diet_sessions_list; 閣法 = cabinet bills, 衆法/参法 = member bills of the House of Representatives/Councillors) with where each is now: status as published (審議状況, e.g. 成立 = enacted), a status code, the position read from published stages (e.g. in_committee), latest stage date and source URLs. Filters: session, house, kind, status, title words. Free.

NameTypeReqDescription
housestring–Only bills now with this house, according to the published status
kindstring–Bill kind: 閣法 or cabinet (cabinet bill), 衆法 or hr_member (House of Representatives member bill), 参法 or hc_member (House of Councillors member bill)
limitinteger–Maximum number of bills, 1-200 (default 100)
querystring–Words in the bill title, in Japanese (for example 消費税 = consumption tax)
sessioninteger–Diet session number, for example 222 (default: the current session)
statusstring–Only bills with this status code (see status_meaning in the answer)
NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
billsarrayyes–
disclaimerstringyes–
official_checkobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
queryobjectyes–
session_coverageobjectyes–
sourceobjectyesWhere the answer comes from and how fresh it is.
statusstringyes–
status_notestringyes–
termsstringyesURL of the terms of service.
totalnumberyes–
truncatedbooleanyes–
unknown_reasonstring|nullyes–

No examples provided.

jp_diet_changes ~126

Which Diet bills moved since a date? Changes this service observed on the bill pages of both houses, newest first: bill id and title, from-stage and to-stage (or list status before and after), the published date of the new stage, when observed, and the source URL. First loads and loading of past sessions are not counted. Free.

NameTypeReqDescription
limitinteger–Maximum number of changes, 1-500 (default 200)
sincestring–Japan date YYYY-MM-DD; changes observed on or after it (default: 7 days ago)
NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
changesarrayyes–
disclaimerstringyes–
notestringyes–
observation_notestringyes–
official_checkobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
queryobjectyes–
sourceobjectyes–
statusstringyes–
termsstringyesURL of the terms of service.
totalnumberyes–
truncatedbooleanyes–
unknown_reasonstring|nullyes–

No examples provided.

jp_diet_enforcement_calendar ~214

Which Japanese laws change on which dates? Enforcement dates of amendments, new laws and repeals made by Acts between two dates (Japan time; default the next 365 days; the last year also works): law changed (e-Gov id, title, number, category), amending law number and title, promulgation date, date and its basis, e-Gov's note on the provision, e-Gov link, and the Diet bill id when known. From e-Gov law search (PDL1.0). Facts only. Free.

NameTypeReqDescription
fromstring–First date, YYYY-MM-DD in Japan time (default today)
include_undated––true: also list revisions whose enforcement date is not set yet (default false)
limitinteger–Maximum number of dated entries, 1-500 (default 500)
tostring–Last date, YYYY-MM-DD (default from + 365 days; at most 731 days after from)
NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
coverageobjectyesHow far this service has read e-Gov's revision histories.
eventsarrayyes–
notestringyes–
queryobjectyes–
statusstringyes–
termsstringyesURL of the terms of service.
totalnumberyes–
truncatedbooleanyes–
unknown_reasonstring|nullyes–

No examples provided.

jp_diet_group_votes ~127

How did each parliamentary group (会派) vote on the law bills of a Diet session? From the House of Representatives bill progress pages: for each bill with a plenary vote, the groups for and against as published (names exactly as published, not merged across renames), a bills x groups table, and pairwise agreement between groups (share of bills where both were on the same side, with n). Group-level public votes only; no individual members. Free.

NameTypeReqDescription
sessioninteger–Diet session number, for example 222 (default: the current session)
NameTypeReqDescription
agreementarrayyes–
answered_atstringyes–
attributionobjectyes–
billsarrayyes–
bills_without_group_datanumberyes–
disclaimerstringyes–
groupsarrayyes–
notestringyes–
observation_notestringyes–
official_checkobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
queryobjectyes–
session_coverage–yes–
sourceobjectyes–
statusstringyes–
termsstringyesURL of the terms of service.
unknown_reasonstring|nullyes–

No examples provided.

jp_diet_law_history ~154

How has this Japanese law been changed, by which Acts, and from when? Give an e-Gov law id (e.g. 322AC0000000049 = 労働基準法). Returns amendments by Acts since 1998 that e-Gov's revision history lists (mostly from 2016-2017 on), newest first: amending law number and title, promulgation date, each enforcement stage with its date (future included) and e-Gov's note, e-Gov link, and the Diet bill id when known. No law text. Free.

NameTypeReqDescription
law_idstringyese-Gov law id, for example 322AC0000000049
NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
changesarrayyes–
coverageobjectyesHow far this service has read e-Gov's revision histories.
law–yes–
notestringyes–
queryobjectyes–
statusstringyes–
termsstringyesURL of the terms of service.

No examples provided.

jp_diet_sessions_list ~97

Which Diet sessions does this service hold bill records for? Returns every session the House of Representatives bill pages list (from 142, 1998), newest first: number, type (常会 ordinary, 臨時会 extraordinary, 特別会 special), start and end dates, number of law bills, and how far it is loaded (coverage complete, partial or not_loaded; past sessions are loaded newest first). Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
countsobjectyes–
coveragestringyespartial while past sessions are still being loaded.
disclaimerstringyes–
official_checkobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
sessionsarrayyes–
sessions_notestringyes–
sourceobjectyesWhere the answer comes from and how fresh it is.
statusstringyes–
status_notestringyes–
termsstringyesURL of the terms of service.
unknown_reasonstring|nullyes–

No examples provided.

jp_diet_stats ~156

Counts of law bills per Diet session and kind (cabinet / member bills): listed, newly submitted, carried in, enacted, withdrawn, not concluded, carried over, rejected, enactment share of closed sessions; days from submission to enactment (median, p25, p75, n); by committee. This service's own aggregation of the bill pages it has loaded, always with coverage (which sessions are complete or still loading). Past facts only, not a forecast. Free.

NameTypeReqDescription
kindstring–Only this bill kind: 閣法 or cabinet, 衆法 or hr_member, 参法 or hc_member
sessioninteger–Only this Diet session (default: every loaded session)
NameTypeReqDescription
answered_atstringyes–
attributionobjectyes–
by_committeearrayyes–
computed_atstring|nullyes–
coverage–yes–
days_to_enactment–yes–
definitionsobjectyes–
disclaimerstringyes–
observation_notestringyes–
official_checkobjectyes–
provenancearrayyesFreshness receipts for every upstream source used.
queryobjectyes–
sessionsarrayyes–
sourceobjectyes–
statusstringyes–
termsstringyesURL of the terms of service.
totals–yes–
unknown_reasonstring|nullyes–

No examples provided.

Install

How do I install the Japan Diet Bill Tracker MCP server?

Japan Diet Bill Tracker is a hosted endpoint at https://jp-diet-production.mk-career-planning.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 · jp-diet-production.mk-career-planning.workers.dev

# add to Claude Code
claude mcp add --transport http mk-career-planning-jp-diet 'https://jp-diet-production.mk-career-planning.workers.dev/mcp'
Common questions

What is the Japan Diet Bill Tracker MCP server?

Japan Diet Bill Tracker is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-diet. Where is a bill in Japan's Diet now? Stages, dates, laws it amends and when, with source URLs. This page covers its hosted endpoint (https://jp-diet-production.mk-career-planning.workers.dev/mcp).

Is the Japan Diet Bill Tracker MCP server safe to use?

Japan Diet Bill Tracker scores 69 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 Diet Bill Tracker MCP server expose?

Japan Diet Bill Tracker exposes 10 tools: catalog, jp_diet_bills_list, jp_diet_sessions_list, jp_diet_bill_status, jp_diet_group_votes, and 5 more. Their descriptions and schemas cost roughly 1,467 tokens of context every time the server is loaded.

Does the Japan Diet Bill Tracker MCP server require authentication?

No. We connected to Japan Diet Bill Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Japan Diet Bill Tracker MCP server still maintained?

Japan Diet Bill Tracker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Japan Diet Bill Tracker MCP server?

VerifyMCP ran 12 checks on Japan Diet Bill Tracker, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Japan Diet Bill Tracker: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.