io.github.kodandy/jp-m2m-gateway
REMOTE · JP-M2M-GATEWAY-62KO7B2UWA-AN.A.RUN.APP · SCANNED SEP 24
Raw Japanese regulatory data for AI agents: pension, gazette, gBizINFO. x402-metered (USDC).
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 487 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the io.github.kodandy/jp-m2m-gateway MCP server?
io.github.kodandy/jp-m2m-gateway is a hosted endpoint at https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/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 · jp-m2m-gateway-62ko7b2uwa-an.a.run.app
claude mcp add --transport http kodandy-jp-m2m-gateway 'https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp'
{
"mcpServers": {
"kodandy-jp-m2m-gateway": {
"url": "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp"
}
}
} {
"servers": {
"kodandy-jp-m2m-gateway": {
"type": "http",
"url": "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp"
}
}
} [mcp_servers.kodandy-jp-m2m-gateway] url = "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kodandy-jp-m2m-gateway": {
"type": "remote",
"url": "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp",
"enabled": true
}
}
} openclaw mcp add kodandy-jp-m2m-gateway --url 'https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp' --transport streamable-http
mcp_servers:
kodandy-jp-m2m-gateway:
url: "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp" {
"McpServers": {
"kodandy-jp-m2m-gateway": {
"Transport": "http",
"Url": "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp"
}
}
} assistant mcp add kodandy-jp-m2m-gateway -t streamable-http -u 'https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp'
{
"mcpServers": {
"kodandy-jp-m2m-gateway": {
"type": "http",
"url": "https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 24 Sept 2026 · Probed https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 4 Sept 2026 | 27 Nov 2026 | ECDSA 256 | SHA256-RSA | a6993fec773504b312550b7de9609011 |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jp-m2m-gateway-62ko7b2uwa-an.a.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | 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 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp | HTTPS enforced | 302 | https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp |
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 →
get_gazette_financials Official Gazette (官報) raw financial text blocks ~125
Statutory financial disclosure (決算公告) raw text blocks, parsed from gazette page scans by a Vision LLM. Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge for the resource. Private beta note: a successful settlement is acknowledged with a receipt that records your priority access; the dataset itself unlocks for early settlers as provisioning goes live.
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_id | string | yes | 13-digit Japanese corporate number (法人番号), e.g. 7010001012345 |
No output schema declared.
No examples provided.
get_government_records gBizINFO procurement / subsidy raw log ~84
FREE during beta — returns live data. Un-aggregated procurement contracts, subsidy grants and certifications, pulled on demand from gBizINFO upstream. Source: gBizINFO (経済産業省), attribution included in every response.
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_id | string | yes | 13-digit Japanese corporate number (法人番号), e.g. 7010001012345 |
No output schema declared.
No examples provided.
get_pension_headcount_log Japan Pension Service monthly insured-headcount raw log ~126
Un-aggregated month-over-month insured headcount deltas (健康保険・厚生年金) for one Japanese corporate number. Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge for the resource. Private beta note: a successful settlement is acknowledged with a receipt that records your priority access; the dataset itself unlocks for early settlers as provisioning goes live.
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_id | string | yes | 13-digit Japanese corporate number (法人番号), e.g. 7010001012345 |
No output schema declared.
No examples provided.
list_company_datasets List paid raw datasets for a Japanese company ~80
Free catalog lookup. Lists the raw regulatory datasets available for one Japanese corporate number with per-call x402 pricing (0.05 USDC per call). Use the dataset tools or the returned api_url to retrieve data.
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_id | string | yes | 13-digit Japanese corporate number (法人番号), e.g. 7010001012345 |
No output schema declared.
No examples provided.
search_corporations Search Japanese corporations (free) ~72
FREE — returns live data. Resolve Japanese company names to 13-digit corporate numbers (法人番号) via gBizINFO. Use the corporate number with the dataset tools.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Company name (Japanese), partial match supported |
| page | integer | – | Result page, default 1 |
No output schema declared.
No examples provided.
What is the io.github.kodandy/jp-m2m-gateway MCP server?
io.github.kodandy/jp-m2m-gateway is an MCP server listed in the public MCP registry as io.github.kodandy/jp-m2m-gateway. Raw Japanese regulatory data for AI agents: pension, gazette, gBizINFO. x402-metered (USDC). This page covers its hosted endpoint (https://jp-m2m-gateway-62ko7b2uwa-an.a.run.app/mcp).
Is the io.github.kodandy/jp-m2m-gateway MCP server safe to use?
io.github.kodandy/jp-m2m-gateway scores 79 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 io.github.kodandy/jp-m2m-gateway MCP server expose?
io.github.kodandy/jp-m2m-gateway exposes 5 tools: list_company_datasets, get_pension_headcount_log, get_gazette_financials, get_government_records, search_corporations. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.
Does the io.github.kodandy/jp-m2m-gateway MCP server require authentication?
No. We connected to io.github.kodandy/jp-m2m-gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.kodandy/jp-m2m-gateway MCP server still maintained?
io.github.kodandy/jp-m2m-gateway is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.