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
Available components
Last scanned (13 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
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 Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 17 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.
- 15 Oct 26 +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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 66
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 18 Oct 2026 · Probed https://japan-agent-api-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 japan-agent-api-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://japan-agent-api-production.mk-career-planning.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://japan-agent-api-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 ~93
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.
| 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.
jp_municipality Japan municipality code lookup ~300
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| as_of_codes | array | yes | Codes valid on as_of, with names, JMA area and J-LIS certificate availability. |
| changes | array | yes | – |
| checked_scope | string | yes | – |
| disclaimer | string | yes | – |
| input | object | yes | The query as understood (code or prefecture and name, and as_of). |
| license_note | string | yes | – |
| national_rules | – | yes | – |
| out_of_scope | array | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| responded_at | string | yes | – |
| retrieved_at | string|null | yes | – |
| source | string | yes | – |
| status | string | yes | mapped / split_candidates / unknown / invalid. |
| status_values | object | yes | – |
| terms | string | yes | URL of the terms of service. |
No examples provided.
jp_municipality_batch Japan municipality batch lookup (paid) ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Default as_of for items that do not set their own. |
| items | array | yes | 1 to 50 lookups; each gives code, or prefecture and name. |
Structured output declared, but exposes no named fields.
No examples provided.
jp_trip_impact_check Japan trip impact check (paid) ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| itinerary | array | yes | 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… |
Structured output declared, but exposes no named fields.
No examples provided.
jp_typhoons Japan typhoon bulletins (JMA) ~85
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| checked_sources | array | yes | – |
| count | number | yes | – |
| ended | array | yes | – |
| license_note | string | yes | – |
| note | string | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| responded_at | string | yes | – |
| retrieved_at | string | yes | When the upstream data was retrieved (ISO 8601). |
| source | string | yes | Data source and processor. |
| status | string | yes | 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 | yes | URL of the terms of service. |
| typhoons | array | yes | – |
| unchecked | array | yes | – |
No examples provided.
jp_volcanoes Japan volcanic alert levels (JMA) ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| coverage | object | yes | 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 | yes | – |
| note | string | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| responded_at | string | yes | – |
| retrieved_at | string | yes | When the upstream data was retrieved (ISO 8601). |
| source | string | yes | Data source and processor. |
| terms | string | yes | URL of the terms of service. |
| volcanoes | array | yes | One entry per volcano. |
No examples provided.
jp_warnings Japan weather warnings by prefecture (JMA) ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_municipalities | boolean | – | Also list every municipality (Japanese and English names) per warning. Default false. |
| prefecture | string | yes | 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| bulletins | array | yes | – |
| counts | object | yes | – |
| coverage | string | yes | 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 | yes | – |
| forecast_areas | array | yes | – |
| license_note | string | yes | – |
| lifted_in_latest_bulletin | array | yes | – |
| missing_offices | array | yes | – |
| prefecture | object | yes | – |
| provenance | array | yes | Freshness receipts for every upstream source used. |
| region | – | yes | – |
| responded_at | string | yes | – |
| retrieved_at | string | yes | When the upstream data was retrieved (ISO 8601). |
| source | string | yes | Data source and processor. |
| terms | string | yes | URL of the terms of service. |
| warnings | array | yes | Warnings and advisories in effect (type, level, status, areas). |
No examples provided.
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.
remote · japan-agent-api-production.mk-career-planning.workers.dev
claude mcp add --transport http mk-career-planning-japan-agent-api 'https://japan-agent-api-production.mk-career-planning.workers.dev/mcp'
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.