Japan Residence Processing Times
io.github.mk-career-planning/jp-residence-processingmk-career-planningstreamable-httpv0.1.0Scanned
Average processing days of Japan residence applications per status, from ISA's published PDFs.
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
residence_processing_historyHow has ISA's average processing time for this status of residence changed over time?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
residence_processing_latestHow many days did ISA take on average, in its latest published period, to process a residence application for this status of residence?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
residence_processing_statusesWhich statuses of residence and procedures do ISA's processing-time tables cover, and which keys and names does this service accept?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
catalogList the tools of this server with prices, data sources, licensing, daily limits and data freshness.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
Annotations the server declares
- readOnlyHint: true
get_receiptRe-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment.No findings
Why it is in this group
- The name "get_receipt" says "get": a word for reading.
Description, as the server wrote it 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 90 days after settlement.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http jp-residence-processing https://jp-residence-processing-production.mk-career-planning.workers.dev/mcpclaude mcp add --transport http jp-residence-processing https://jp-residence-processing-production.mk-career-planning.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__jp-residence-processing__catalog",
"mcp__jp-residence-processing__get_receipt"
],
"ask": [
"mcp__jp-residence-processing__residence_processing_latest",
"mcp__jp-residence-processing__residence_processing_history",
"mcp__jp-residence-processing__residence_processing_statuses"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jp-residence-processing. Review it before you use it.
Capability tags behind 2 rules
- mcp__jp-residence-processing__residence_processing_latest untrusted-input
- mcp__jp-residence-processing__residence_processing_history untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.mk-career-planning/jp-residence-processing/verify?hash=9b50d31131b16d6116bd1d401fa88a8f71a4e4d31dc5f6dc25eeb27b343b6f76" | jq -e '.changed == false'Pinned hash 9b50d31131b1, from Oct 25, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.mk-career-planning/jp-residence-processing/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.mk-career-planning/jp-residence-processing)Source: MCP Registry. Synced Oct 25, 2026, 09:17 UTC.