Japan Residence Processing Times
REMOTE · JP-RESIDENCE-PROCESSING-PRODUCTION.MK-CAREER-PLANNING.WORKERS.DEV
Average processing days of Japan residence applications per status, from ISA's published PDFs.
Available components
Last scanned (43 minutes ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 655 tokens (~131/item across 5 items; 5 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 Management37
- Stability observed for 11 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 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.
- 3 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.
- 1 Nov 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 Oct 26 0
- Tool “get_receipt” rewrote its description, which is the text the model reads security
- 30 Oct 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.
- 27 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.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 67
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 5 Nov 2026 · Probed https://jp-residence-processing-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-residence-processing-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-residence-processing-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jp-residence-processing-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.
residence_processing_history Japan residence processing time history ~239
How has ISA's average processing time for this status of residence changed over time? Give status and optionally procedure and measure. Returns series per granularity (monthly from October 2024, quarterly FY2017 to FY2024 Q2, never mixed or interpolated), procedure and measure, oldest first, with periods that could not be read or are blank listed as gaps with the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| measure | string | – | Optional: disposition (days to issuance or notification of permission) or review_end (days to the end of examination; extension and change, from FY2020). Omit for both |
| procedure | string | – | Optional: coe (certificate of eligibility), extension (extension of period of stay) or change (change of status of residence). Omit for all |
| status | string | yes | Status of residence: key (e.g. engineer-humanities-international, student, highly-skilled-professional-1a), Japanese name as in ISA's table (e.g. 留学, 高度専門職1号イ) or English name (e.g. Student). Exact m… |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| disclaimer | object | yes | Read first: averages of applications approved in the period, as published by ISA; not a forecast for any individual application. |
| fixed_notes | array | yes | Notes that apply to every figure (approvals only, what disposition means, blank is not zero, seasonal peaks). |
| history_note | string | yes | – |
| latest_official_period | – | yes | ISA's latest period on the list page and whether this service could read its PDF. |
| legal_notice | string | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| residence_status | object | yes | – |
| series | array | yes | One series per granularity, procedure and measure, oldest first. Monthly and quarterly series are separate; nothing is interpolated. |
| source | object | yes | Where the answer comes from: ISA's list page and PDF, and when this service read them. |
| status | string | yes | – |
| status_note | string | yes | – |
| terms | string | yes | URL of the terms of service. |
No examples provided.
residence_processing_latest Latest Japan residence processing time ~256
How many days did ISA take on average, in its latest published period, to process a residence application for this status of residence? Give status (key, Japanese or English name), optionally procedure. Returns figures with period, blank cells, the PDF's notes, ISA's PDF URL and retrieval time. Status: found, not_listed (blank, not zero), unknown, unreadable_latest (older readable period, labelled). Averages of approved applications, not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| measure | string | – | Optional: disposition (days to issuance or notification of permission) or review_end (days to the end of examination; extension and change, from FY2020). Omit for both |
| procedure | string | – | Optional: coe (certificate of eligibility), extension (extension of period of stay) or change (change of status of residence). Omit for all |
| status | string | yes | Status of residence: key (e.g. engineer-humanities-international, student, highly-skilled-professional-1a), Japanese name as in ISA's table (e.g. 留学, 高度専門職1号イ) or English name (e.g. Student). Exact m… |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | – | yes | – |
| answered_at | string | yes | – |
| attribution | object | yes | – |
| disclaimer | object | yes | Read first: averages of applications approved in the period, as published by ISA; not a forecast for any individual application. |
| fixed_notes | array | yes | Notes that apply to every figure (approvals only, what disposition means, blank is not zero, seasonal peaks). |
| latest_official_period | – | yes | ISA's latest period on the list page and whether this service could read its PDF. |
| legal_notice | string | yes | – |
| older_readable | – | yes | Only with unreadable_latest: the most recent period this service could read. Older than ISA's latest. |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| query | object | yes | – |
| residence_status | object | yes | – |
| source | object | yes | Where the answer comes from: ISA's list page and PDF, and when this service read them. |
| status | string | yes | found = figures in the latest period read; not_listed = blank cells in that period (not zero); unknown = no readable data yet; unreadable_latest = ISA's latest PDF could not be read, older_readable h… |
| status_note | string | yes | – |
| terms | string | yes | URL of the terms of service. |
No examples provided.
residence_processing_statuses Statuses of residence in ISA processing tables ~50
Which statuses of residence and procedures do ISA's processing-time tables cover, and which keys and names does this service accept? Returns the canonical list (key, Japanese and English names), procedures and measures.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | – |
| attribution | object | yes | – |
| disclaimer | object | yes | Read first: averages of applications approved in the period, as published by ISA; not a forecast for any individual application. |
| fixed_notes | array | yes | Notes that apply to every figure (approvals only, what disposition means, blank is not zero, seasonal peaks). |
| legal_notice | string | yes | – |
| matching_note | string | yes | – |
| procedures | array | yes | – |
| statuses | array | yes | – |
| terms | string | yes | URL of the terms of service. |
No examples provided.
How do I install the Japan Residence Processing Times MCP server?
Japan Residence Processing Times is a hosted endpoint at https://jp-residence-processing-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-residence-processing-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-jp-residence-processing 'https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp'
What is the Japan Residence Processing Times MCP server?
Japan Residence Processing Times is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-residence-processing. Average processing days of Japan residence applications per status, from ISA's published PDFs. This page covers its hosted endpoint (https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp).
Is the Japan Residence Processing Times MCP server safe to use?
Japan Residence Processing Times scores 72 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 Residence Processing Times MCP server expose?
Japan Residence Processing Times exposes 5 tools: catalog, residence_processing_latest, residence_processing_history, residence_processing_statuses, get_receipt. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.
Does the Japan Residence Processing Times MCP server require authentication?
No. We connected to Japan Residence Processing Times without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Residence Processing Times MCP server still maintained?
Japan Residence Processing Times 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.