# 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.

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `jp-residence-processing-production.mk-career-planning.workers.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/mk-career-planning-jp-residence-processing/jp-residence-processing-production.md), [page](https://verifymcp.io/servers/mk-career-planning-jp-residence-processing/jp-residence-processing-production)

## Channel facts

- Endpoint: `https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http mk-career-planning-jp-residence-processing 'https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mk-career-planning-jp-residence-processing": {
      "url": "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mk-career-planning-jp-residence-processing": {
      "type": "http",
      "url": "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mk-career-planning-jp-residence-processing]
url = "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mk-career-planning-jp-residence-processing": {
      "type": "remote",
      "url": "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mk-career-planning-jp-residence-processing --url 'https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mk-career-planning-jp-residence-processing:
    url: "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mk-career-planning-jp-residence-processing": {
      "Transport": "http",
      "Url": "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mk-career-planning-jp-residence-processing -t streamable-http -u 'https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-jp-residence-processing": {
      "type": "http",
      "url": "https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 72, +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.

### 2026-11-03 (score 71, +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.

### 2026-11-01 (score 70, +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.

### 2026-10-31 (score 69, 0)

- [security] Tool “get_receipt” rewrote its description, which is the text the model reads

### 2026-10-30 (score 69, +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.

### 2026-10-27 (score 68, +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.

### 2026-10-26 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 67)

First indexed and scored.

## MCP tools (5)

### `catalog` (~27 tokens)

Catalog: tools, prices and limits

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

Output parameters:

- `daily_limits` (object): Daily limits of paid calls (calls, usd, timezone) or a misconfiguration notice.
- `fetch_status_values` (object)
- `legal` (object)
- `paused` (object): Operator pause flags (true = paused).
- `payment` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `server` (object)
- `terms` (string): URL of the terms of service.
- `tools` (array): Every tool of this server with its price.

### `residence_processing_latest` (~256 tokens)

Latest Japan residence processing time

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.

Input parameters:

- `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, required): 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…

Output parameters:

- `answer`
- `answered_at` (string)
- `attribution` (object)
- `disclaimer` (object): Read first: averages of applications approved in the period, as published by ISA; not a forecast for any individual application.
- `fixed_notes` (array): Notes that apply to every figure (approvals only, what disposition means, blank is not zero, seasonal peaks).
- `latest_official_period`: ISA's latest period on the list page and whether this service could read its PDF.
- `legal_notice` (string)
- `older_readable`: Only with unreadable_latest: the most recent period this service could read. Older than ISA's latest.
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `residence_status` (object)
- `source` (object): Where the answer comes from: ISA's list page and PDF, and when this service read them.
- `status` (string): 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)
- `terms` (string): URL of the terms of service.

### `residence_processing_history` (~239 tokens)

Japan residence processing time history

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.

Input parameters:

- `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, required): 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…

Output parameters:

- `answered_at` (string)
- `attribution` (object)
- `disclaimer` (object): Read first: averages of applications approved in the period, as published by ISA; not a forecast for any individual application.
- `fixed_notes` (array): Notes that apply to every figure (approvals only, what disposition means, blank is not zero, seasonal peaks).
- `history_note` (string)
- `latest_official_period`: ISA's latest period on the list page and whether this service could read its PDF.
- `legal_notice` (string)
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `residence_status` (object)
- `series` (array): One series per granularity, procedure and measure, oldest first. Monthly and quarterly series are separate; nothing is interpolated.
- `source` (object): Where the answer comes from: ISA's list page and PDF, and when this service read them.
- `status` (string)
- `status_note` (string)
- `terms` (string): URL of the terms of service.

### `residence_processing_statuses` (~50 tokens)

Statuses of residence in ISA processing tables

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.

Output parameters:

- `answered_at` (string)
- `attribution` (object)
- `disclaimer` (object): Read first: averages of applications approved in the period, as published by ISA; not a forecast for any individual application.
- `fixed_notes` (array): Notes that apply to every figure (approvals only, what disposition means, blank is not zero, seasonal peaks).
- `legal_notice` (string)
- `matching_note` (string)
- `procedures` (array)
- `statuses` (array)
- `terms` (string): URL of the terms of service.

### `get_receipt` (~83 tokens)

Get receipt of a paid call

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.

Input parameters:

- `receipt_id` (string, required): The receipt_id returned with a paid result ("rcpt_" + 64 hex characters).

Output parameters:

- `payment` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `receipt_id` (string): Receipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt.
- `result`: The stored result, exactly as returned by the paid call.
- `settled_at` (string|null)
- `terms` (string): URL of the terms of service.
- `tool` (string): Name of the paid tool that produced the result.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mk-career-planning-jp-residence-processing/jp-residence-processing-production#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67
- 2026-10-25: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://jp-residence-processing-production.mk-career-planning.workers.dev/mcp
- Website: https://jp-residence-processing-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-jp-residence-processing/jp-residence-processing-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-jp-residence-processing/jp-residence-processing-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-jp-residence-processing/jp-residence-processing-production