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.
Available components
Last scanned (14 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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 →
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.
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 |
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 →
catalog Catalog: tools, prices and limits ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| daily_limits | object | yes | Daily limits of paid calls (calls, usd, timezone) or a misconfiguration notice. |
| fetch_status_values | object | – | – |
| legal | object | yes | – |
| paused | object | yes | Operator pause flags (true = paused). |
| payment | object | yes | – |
| provenance | array | – | Freshness receipts for every upstream source used. |
| server | object | yes | – |
| terms | string | yes | URL of the terms of service. |
| tools | array | yes | Every tool of this server with its price. |
No examples provided.
get_receipt Get receipt of a paid call ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id returned with a paid result ("rcpt_" + 64 hex characters). |
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| receipt_id | string | yes | Receipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt. |
| result | – | yes | The stored result, exactly as returned by the paid call. |
| settled_at | string|null | yes | – |
| terms | string | yes | URL of the terms of service. |
| tool | string | yes | Name of the paid tool that produced the result. |
No examples provided.
jp_diet_bill_status Japan Diet: one bill's stage and timeline ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | string | – | Bill id: submitted session, kind and number, for example 222-閣法-1, 222-cabinet-1, 221-hr-1, 222-hc-2 |
| title | string | – | Bill title or part of it, in Japanese (used when bill_id is not given) |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| bill | – | yes | – |
| cabinet_decision | object | – | Cabinet decision of a cabinet bill from the Prime Minister's Office agenda pages (PDL1.0; keep the source line). |
| candidates | array | yes | – |
| disclaimer | string | yes | – |
| meetings | object | – | Diet meetings whose record contains the bill title (meeting-level data and links only; no speeches, no speaker names). |
| official_check | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| source | object | yes | Where the answer comes from and how fresh it is. |
| status | string | yes | – |
| status_note | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| unknown_reason | string|null | yes | – |
No examples provided.
jp_diet_bills_list Japan Diet: law bills of a session ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| house | string | – | Only bills now with this house, according to the published status |
| kind | string | – | Bill kind: 閣法 or cabinet (cabinet bill), 衆法 or hr_member (House of Representatives member bill), 参法 or hc_member (House of Councillors member bill) |
| limit | integer | – | Maximum number of bills, 1-200 (default 100) |
| query | string | – | Words in the bill title, in Japanese (for example 消費税 = consumption tax) |
| session | integer | – | Diet session number, for example 222 (default: the current session) |
| status | string | – | Only bills with this status code (see status_meaning in the answer) |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| bills | array | yes | – |
| disclaimer | string | yes | – |
| official_check | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| session_coverage | object | yes | – |
| source | object | yes | Where the answer comes from and how fresh it is. |
| status | string | yes | – |
| status_note | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| total | number | yes | – |
| truncated | boolean | yes | – |
| unknown_reason | string|null | yes | – |
No examples provided.
jp_diet_changes Japan Diet: observed bill changes since a date ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of changes, 1-500 (default 200) |
| since | string | – | Japan date YYYY-MM-DD; changes observed on or after it (default: 7 days ago) |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| changes | array | yes | – |
| disclaimer | string | yes | – |
| note | string | yes | – |
| observation_note | string | yes | – |
| official_check | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| source | object | yes | – |
| status | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| total | number | yes | – |
| truncated | boolean | yes | – |
| unknown_reason | string|null | yes | – |
No examples provided.
jp_diet_enforcement_calendar Japan: law 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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | 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) |
| limit | integer | – | Maximum number of dated entries, 1-500 (default 500) |
| to | string | – | Last date, YYYY-MM-DD (default from + 365 days; at most 731 days after from) |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| coverage | object | yes | How far this service has read e-Gov's revision histories. |
| events | array | yes | – |
| note | string | yes | – |
| query | object | yes | – |
| status | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| total | number | yes | – |
| truncated | boolean | yes | – |
| unknown_reason | string|null | yes | – |
No examples provided.
jp_diet_group_votes Japan Diet: parliamentary group votes of a session ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| session | integer | – | Diet session number, for example 222 (default: the current session) |
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | array | yes | – |
| answered_at | string | yes | – |
| attribution | object | yes | – |
| bills | array | yes | – |
| bills_without_group_data | number | yes | – |
| disclaimer | string | yes | – |
| groups | array | yes | – |
| note | string | yes | – |
| observation_note | string | yes | – |
| official_check | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| session_coverage | – | yes | – |
| source | object | yes | – |
| status | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| unknown_reason | string|null | yes | – |
No examples provided.
jp_diet_law_history Japan: one law's amendments and enforcement dates ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | string | yes | e-Gov law id, for example 322AC0000000049 |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| changes | array | yes | – |
| coverage | object | yes | How far this service has read e-Gov's revision histories. |
| law | – | yes | – |
| note | string | yes | – |
| query | object | yes | – |
| status | string | yes | – |
| terms | string | yes | URL of the terms of service. |
No examples provided.
jp_diet_sessions_list Japan Diet: sessions and coverage ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| counts | object | yes | – |
| coverage | string | yes | partial while past sessions are still being loaded. |
| disclaimer | string | yes | – |
| official_check | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| sessions | array | yes | – |
| sessions_note | string | yes | – |
| source | object | yes | Where the answer comes from and how fresh it is. |
| status | string | yes | – |
| status_note | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| unknown_reason | string|null | yes | – |
No examples provided.
jp_diet_stats Japan Diet: bill statistics by session and kind ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only this bill kind: 閣法 or cabinet, 衆法 or hr_member, 参法 or hc_member |
| session | integer | – | Only this Diet session (default: every loaded session) |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| by_committee | array | yes | – |
| computed_at | string|null | yes | – |
| coverage | – | yes | – |
| days_to_enactment | – | yes | – |
| definitions | object | yes | – |
| disclaimer | string | yes | – |
| observation_note | string | yes | – |
| official_check | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| sessions | array | yes | – |
| source | object | yes | – |
| status | string | yes | – |
| terms | string | yes | URL of the terms of service. |
| totals | – | yes | – |
| unknown_reason | string|null | yes | – |
No examples provided.
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
claude mcp add --transport http mk-career-planning-jp-diet 'https://jp-diet-production.mk-career-planning.workers.dev/mcp'
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.