# Japan Agent API (remote · japan-agent-api-production.mk-career-planning.workers.dev)

Japan JMA warnings, typhoons, volcano levels and municipality code history in English; x402 checks

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `japan-agent-api-production.mk-career-planning.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/mk-career-planning-japan-agent-api/japan-agent-api-production.md), [page](https://verifymcp.io/servers/mk-career-planning-japan-agent-api/japan-agent-api-production)

## Channel facts

- Endpoint: `https://japan-agent-api-production.mk-career-planning.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

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

- **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**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1194 tokens (~149/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Agent API MCP server?

Japan Agent API is a hosted endpoint at https://japan-agent-api-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-japan-agent-api 'https://japan-agent-api-production.mk-career-planning.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mk-career-planning-japan-agent-api": {
      "url": "https://japan-agent-api-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mk-career-planning-japan-agent-api": {
      "type": "http",
      "url": "https://japan-agent-api-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mk-career-planning-japan-agent-api]
url = "https://japan-agent-api-production.mk-career-planning.workers.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mk-career-planning-japan-agent-api --url 'https://japan-agent-api-production.mk-career-planning.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mk-career-planning-japan-agent-api:
    url: "https://japan-agent-api-production.mk-career-planning.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mk-career-planning-japan-agent-api": {
      "Transport": "http",
      "Url": "https://japan-agent-api-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mk-career-planning-japan-agent-api -t streamable-http -u 'https://japan-agent-api-production.mk-career-planning.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-japan-agent-api": {
      "type": "http",
      "url": "https://japan-agent-api-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-10-17 (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-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 66)

First indexed and scored.

## MCP tools (8)

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

### `jp_warnings` (~149 tokens)

Japan weather warnings by prefecture (JMA)

Which JMA weather emergency warnings, warnings and advisories are in effect in this Japanese prefecture now? Structured JSON in English and Japanese (type, level, status, areas with JMA's English names, issued_at, source URL). Relay only; no independent forecast.

Input parameters:

- `include_municipalities` (boolean): Also list every municipality (Japanese and English names) per warning. Default false.
- `prefecture` (string, required): Japanese prefecture: English name (e.g. "Tokyo", "Osaka", "Hokkaido"; "Tokyo-to" and "Osaka Prefecture" also work), Japanese name in kanji, or JIS code "01".."47".

Output parameters:

- `bulletins` (array)
- `counts` (object)
- `coverage` (string): complete = the current status of every forecast area was confirmed (JMA XML bulletin or JMA website current-status data); partial = some not confirmed; unknown = none confirmed (see missing_offices;…
- `danger_notice` (boolean)
- `forecast_areas` (array)
- `license_note` (string)
- `lifted_in_latest_bulletin` (array)
- `missing_offices` (array)
- `prefecture` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `region`
- `responded_at` (string)
- `retrieved_at` (string): When the upstream data was retrieved (ISO 8601).
- `source` (string): Data source and processor.
- `terms` (string): URL of the terms of service.
- `warnings` (array): Warnings and advisories in effect (type, level, status, areas).

### `jp_typhoons` (~85 tokens)

Japan typhoon bulletins (JMA)

Which typhoons is JMA issuing bulletins for right now, and what do the bulletins forecast? Number, name, center position, central pressure, maximum wind, issue time, and forecast-circle centers, radii and times, relayed as structured JSON from JMA bulletins (VPTW60-65). No independent forecast, interpolation or track extension.

Output parameters:

- `checked_sources` (array)
- `count` (number)
- `ended` (array)
- `license_note` (string)
- `note` (string)
- `provenance` (array): Freshness receipts for every upstream source used.
- `responded_at` (string)
- `retrieved_at` (string): When the upstream data was retrieved (ISO 8601).
- `source` (string): Data source and processor.
- `status` (string): listed = JMA is issuing typhoon bulletins; none_in_checked_sources = none in the checked feeds; partial/unknown = some or all could not be checked.
- `terms` (string): URL of the terms of service.
- `typhoons` (array)
- `unchecked` (array)

### `jp_volcanoes` (~193 tokens)

Japan volcanic alert levels (JMA)

What is the current JMA Volcanic Alert Level (1-5, or warning kind) of this volcano or of every JMA-monitored volcano? Name in English or Japanese, or 3-digit JMA code. Returns JMA English and Japanese names, level, previous level and change, issue time, prefectures named in JMA bulletins, source URL and freshness receipt. Relay only; no forecast or interpretation. Gaps filled from JMA website lists (newer wins). No JMA source seen = not_seen_in_checked_feeds, never assumed level 1.

Input parameters:

- `volcano` (string): Optional. JMA volcano name in English (e.g. "Sakurajima", "Asamayama") or Japanese (e.g. "桜島"), or the 3-digit JMA volcano code (e.g. "506"). Omit to list all volcanoes.

Output parameters:

- `count` (number)
- `coverage` (object): complete = every volcano has a usable state (from an XML bulletin, warning.json or the monthly national summary) and no bulletin is pending or failed.
- `license_note` (string)
- `note` (string)
- `provenance` (array): Freshness receipts for every upstream source used.
- `responded_at` (string)
- `retrieved_at` (string): When the upstream data was retrieved (ISO 8601).
- `source` (string): Data source and processor.
- `terms` (string): URL of the terms of service.
- `volcanoes` (array): One entry per volcano.

### `jp_municipality` (~300 tokens)

Japan municipality code lookup

Which code does this Japanese municipality have on a date (default today)? Give a 5/6-digit code, or prefecture and name (old names OK). Returns status mapped / split_candidates / unknown / invalid, the valid code with English and Japanese names, change type and date (merger, incorporation, division, designated city, name change), confirmed JMA warning areas only, and J-LIS convenience-store certificate availability for 8 certificate types. Facts only, from e-Stat LOD (CC BY 4.0) and J-LIS.

Input parameters:

- `as_of` (string): YYYY-MM-DD. The date the answer is for (default: today in Japan time).
- `code` (string): Municipality code: 5 digits, or 6 digits including the check digit (e.g. 22131 or 221317).
- `name` (string): Municipality or ward name in Japanese (old names accepted; a ward may be prefixed with its city) or its e-Stat English name (e.g. "Naka-ku", "Hamamatsu-shi"). Use with prefecture.
- `prefecture` (string): Japanese prefecture: English name (e.g. "Tokyo", "Osaka", "Hokkaido"; "Tokyo-to" and "Osaka Prefecture" also work), Japanese name in kanji, or JIS code "01".."47". Use with name.

Output parameters:

- `as_of` (string)
- `as_of_codes` (array): Codes valid on as_of, with names, JMA area and J-LIS certificate availability.
- `changes` (array)
- `checked_scope` (string)
- `disclaimer` (string)
- `input` (object): The query as understood (code or prefecture and name, and as_of).
- `license_note` (string)
- `national_rules`
- `out_of_scope` (array)
- `provenance` (array): Freshness receipts for every upstream source used.
- `responded_at` (string)
- `retrieved_at` (string|null)
- `source` (string)
- `status` (string): mapped / split_candidates / unknown / invalid.
- `status_values` (object)
- `terms` (string): URL of the terms of service.

### `get_receipt` (~93 tokens)

Get receipt of a paid call

Re-fetch the stored result of a settled paid call (e.g. jp_trip_impact_check) 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.

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.

### `jp_trip_impact_check` (~184 tokens)

Japan trip impact check (paid)

Does a JMA warning or advisory in effect now match a stop on this Japan itinerary [{date, prefecture}]? Per stop: matched_advisory (with severity), no_match_in_checked_sources (NOT a statement of no impact) or unknown (data missing, or date not today/tomorrow JST). Returns checked sources and areas, unchecked areas, issued_at, retrieved_at, and current JMA typhoon/volcano bulletins (listed, not matched). No forecast. Retrying with the same payment is not charged; use receipt_id with get_receipt.

Input parameters:

- `itinerary` (array, required): 1 to 14 stops {date, prefecture}, in travel order. Only stops dated today or tomorrow (Japan time) can be matched; others return unknown, but typhoon and volcano bulletins currently in effect are sti…

### `jp_municipality_batch` (~163 tokens)

Japan municipality batch lookup (paid)

Which codes are valid on a date for up to 50 Japanese municipalities? e-Stat LOD change history (CC BY 4.0): status mapped / split_candidates (all successors, not apportioned) / unknown / invalid, the code valid on as_of with English and Japanese names, change type and date, confirmed JMA warning areas only, and J-LIS convenience-store certificate availability (available / not_listed / unknown). Facts only; no document preparation or legal advice. Retrying with the same payment is not charged.

Input parameters:

- `as_of` (string): Default as_of for items that do not set their own.
- `items` (array, required): 1 to 50 lookups; each gives code, or prefecture and name.

## Diagnostics

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

## Score history

- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 66

## Common questions

### What is the Japan Agent API MCP server?

Japan Agent API is an MCP server listed in the public MCP registry as io.github.mk-career-planning/japan-agent-api. Japan JMA warnings, typhoons, volcano levels and municipality code history in English; x402 checks. This page covers its hosted endpoint (https://japan-agent-api-production.mk-career-planning.workers.dev/mcp).

### Is the Japan Agent API MCP server safe to use?

Japan Agent API scores 69 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 Agent API MCP server expose?

Japan Agent API exposes 8 tools: catalog, jp_warnings, jp_typhoons, jp_volcanoes, jp_municipality, and 3 more. Their descriptions and schemas cost roughly 1,194 tokens of context every time the server is loaded.

### Does the Japan Agent API MCP server require authentication?

No. We connected to Japan Agent API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan Agent API MCP server still maintained?

Japan Agent API is still listed as active in the MCP registry. We last reached this channel on 18 October 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://japan-agent-api-production.mk-career-planning.workers.dev/mcp
- Website: https://japan-agent-api-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-japan-agent-api/japan-agent-api-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-japan-agent-api/japan-agent-api-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-japan-agent-api/japan-agent-api-production