Japan TITP Administrative Actions
REMOTE · JP-TITP-ACTIONS-PRODUCTION.MK-CAREER-PLANNING.WORKERS.DEV
Published TITP actions (ISA) on Japanese intern supervising/implementing orgs. Tracks file changes.
Available components
Last scanned (43 minutes ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 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. 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 569 tokens (~142/item across 4 items; 4 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 Management43
- Stability observed for 13 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Tool “get_receipt” rewrote its description, which is the text the model reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ 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 5 Nov 2026 · Probed https://jp-titp-actions-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-titp-actions-production.mk-career-planning.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://jp-titp-actions-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-titp-actions-production.mk-career-planning.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 →
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.
titp_action_changes TITP administrative action file changes ~198
Which TITP administrative actions were added to or changed in ISA's published files since a date? From this service's own record of file versions (ISA publishes only the current files). Each change has the action id, observed_at, changed fields and before/after. Actions that ISA no longer publishes are not returned; only the number that left the files per version is shown, without identifiers. History starts at tracking_since. Free window: last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| change_type | string | – | Optional filter: added or modified |
| limit | integer | – | Maximum number of changes, 1-500 (default 100) |
| since | string | yes | ISO 8601 date or date-time with time zone, e.g. 2026-10-01 or 2026-10-01T00:00:00Z |
| target_type | string | – | Optional filter: supervising_organization or implementing_organization |
| Name | Type | Req | Description |
|---|---|---|---|
| action_notice | object | yes | Always pass on: the action is as published on the date shown; it does not mean the organization currently has problems. |
| answered_at | string | yes | – |
| attribution | object | yes | – |
| changes | array | yes | Changes observed by this service between file versions, oldest first. |
| coverage | object | yes | – |
| history_note | string | yes | – |
| history_window | object | yes | Free history window applied to this answer. |
| legal_notice | string | yes | – |
| official_check | object | yes | Read first: confirm on the official ISA page listed here before relying on this answer. |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| removals | array | yes | Number of actions that left ISA's published files per version. No identifiers: actions ISA no longer publishes are not returned. |
| terms | string | yes | URL of the terms of service. |
| tracking_since | string|null | yes | When this service first loaded the files. Nothing before it was observed. |
| truncated | boolean | yes | – |
No examples provided.
titp_action_lookup Look up published TITP administrative actions ~261
Has this TITP supervising or implementing organization in Japan had an administrative action published by ISA, and when? Look up by permit number (1708000404), plan certification number (1704019156) or organization name (exact after normalization; partial = candidates), optional prefecture. Returns listed, not_found_in_checked_records (not proof of no action; actions no longer published are not returned) or unknown, with type, date, reason as published, source file and as-of date.
| Name | Type | Req | Description |
|---|---|---|---|
| certification_number | string | – | Technical intern training plan certification number, e.g. 認1704019156, 変認1809000128 or the digits |
| limit | integer | – | Maximum number of actions per list, 1-100 (default 20) |
| name | string | – | Organization name as published (Japanese), at least 2 characters. Width, case, spaces and line breaks are ignored |
| permit_number | string | – | Supervising organization permit number, e.g. 許1708000404 or 1708000404 |
| prefecture | string | – | Optional filter: prefecture of the published address (Tokyo or 東京都), JIS code (13) or local government code (130001) |
| Name | Type | Req | Description |
|---|---|---|---|
| action_notice | object | yes | Always pass on: the action is as published on the date shown; it does not mean the organization currently has problems. |
| actions | array | yes | – |
| answered_at | string | yes | – |
| attribution | object | yes | – |
| candidates | array | yes | – |
| data_version | – | yes | – |
| legal_notice | string | yes | – |
| official_check | object | yes | Read first: confirm on the official ISA page listed here before relying on this answer. |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| registry_status | object | yes | – |
| status | string | yes | listed = an action matching by number or exact name is in the ISA files checked; not_found_in_checked_records = no match in the files checked (does not mean no action was taken; actions ISA no longer… |
| 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.
How do I install the Japan TITP Administrative Actions MCP server?
Japan TITP Administrative Actions is a hosted endpoint at https://jp-titp-actions-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-titp-actions-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-jp-titp-actions 'https://jp-titp-actions-production.mk-career-planning.workers.dev/mcp'
What is the Japan TITP Administrative Actions MCP server?
Japan TITP Administrative Actions is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-titp-actions. Published TITP actions (ISA) on Japanese intern supervising/implementing orgs. Tracks file changes. This page covers its hosted endpoint (https://jp-titp-actions-production.mk-career-planning.workers.dev/mcp).
Is the Japan TITP Administrative Actions MCP server safe to use?
Japan TITP Administrative Actions scores 73 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 TITP Administrative Actions MCP server expose?
Japan TITP Administrative Actions exposes 4 tools: catalog, titp_action_lookup, titp_action_changes, get_receipt. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.
Does the Japan TITP Administrative Actions MCP server require authentication?
No. We connected to Japan TITP Administrative Actions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan TITP Administrative Actions MCP server still maintained?
Japan TITP Administrative Actions is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.