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

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

## Components

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

## Channel facts

- Endpoint: `https://jp-titp-actions-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. 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.
  - 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**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-jp-titp-actions": {
      "type": "http",
      "url": "https://jp-titp-actions-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 73, +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.

### 2026-11-03 (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-01 (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-10-31 (score 70, 0)

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

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

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

### 2026-10-25 (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-24 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

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

### `titp_action_lookup` (~261 tokens)

Look up published TITP administrative actions

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.

Input parameters:

- `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)

Output parameters:

- `action_notice` (object): Always pass on: the action is as published on the date shown; it does not mean the organization currently has problems.
- `actions` (array)
- `answered_at` (string)
- `attribution` (object)
- `candidates` (array)
- `data_version`
- `legal_notice` (string)
- `official_check` (object): Read first: confirm on the official ISA page listed here before relying on this answer.
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `registry_status` (object)
- `status` (string): 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)
- `terms` (string): URL of the terms of service.
- `total` (number)
- `truncated` (boolean)
- `unknown_reason` (string|null)

### `titp_action_changes` (~198 tokens)

TITP administrative action file changes

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.

Input parameters:

- `change_type` (string): Optional filter: added or modified
- `limit` (integer): Maximum number of changes, 1-500 (default 100)
- `since` (string, required): 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

Output parameters:

- `action_notice` (object): Always pass on: the action is as published on the date shown; it does not mean the organization currently has problems.
- `answered_at` (string)
- `attribution` (object)
- `changes` (array): Changes observed by this service between file versions, oldest first.
- `coverage` (object)
- `history_note` (string)
- `history_window` (object): Free history window applied to this answer.
- `legal_notice` (string)
- `official_check` (object): Read first: confirm on the official ISA page listed here before relying on this answer.
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `removals` (array): Number of actions that left ISA's published files per version. No identifiers: actions ISA no longer publishes are not returned.
- `terms` (string): URL of the terms of service.
- `tracking_since` (string|null): When this service first loaded the files. Nothing before it was observed.
- `truncated` (boolean)

### `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-titp-actions/jp-titp-actions-production#diagnostics

## Score history

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

## Common questions

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

### What did VerifyMCP test on the Japan TITP Administrative Actions MCP server?

VerifyMCP ran 12 checks on Japan TITP Administrative Actions, 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 TITP Administrative Actions: 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.

## Links

- Remote endpoint: https://jp-titp-actions-production.mk-career-planning.workers.dev/mcp
- Website: https://jp-titp-actions-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-jp-titp-actions/jp-titp-actions-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-jp-titp-actions/jp-titp-actions-production/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mk-career-planning-jp-titp-actions/jp-titp-actions-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-jp-titp-actions/jp-titp-actions-production