# Japan Entity Evidence (remote · jp-entity-evidence-production.mk-career-planning.workers.dev)

Japanese public records on an organization: FSA, MOF, EDINET, ISA and gBizINFO lists. Evidence only.

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

## Components

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

## Channel facts

- Endpoint: `https://jp-entity-evidence-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-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**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 458 tokens (~152/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Entity Evidence MCP server?

Japan Entity Evidence is a hosted endpoint at https://jp-entity-evidence-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-entity-evidence 'https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-jp-entity-evidence": {
      "type": "http",
      "url": "https://jp-entity-evidence-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-18 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (3)

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

### `entity_evidence_check` (~348 tokens)

Japan entity evidence: public-record status

For checks spanning several Japanese registries at once: FSA registers, warnings and enforcement case list, MOF asset-freeze list, EDINET filings, ISA support organizations, gBizINFO where connected. Returns each registry's status, version date, source, matches and what was not checked; a domain alone stays unverified. For one registry, use jp-finance, jp-sanctions, jp-edinet or jp-ssw-support-orgs. Stated scope and dates only; no match is not proof none exists. No compliance determination.

Input parameters:

- `address_hint` (string): Part of the address, e.g. 千代田区, to tie a name to one gBizINFO corporate number
- `corporate_number` (string): 13-digit corporate number, e.g. 3010401049814 (NTA registry not yet connected)
- `detail`: true: all records and receipts (default compact)
- `domain` (string): Optional website domain, e.g. example.com. Never resolved to an organization (identity.domain is unverified)
- `edinet_code` (string): EDINET filer code, e.g. E03816
- `fsa_registration_number` (string): GET form of registration_numbers.fsa
- `name` (string): Organization name, e.g. 株式会社SBI証券. A person-like name is screened only against the MOF list
- `prefecture` (string): Prefecture to narrow the ISA and gBizINFO name searches, e.g. Tokyo
- `registration_numbers` (object): Registration numbers by registry
- `ssw_registration_number` (string): GET form of registration_numbers.ssw

Output parameters:

- `answered_at` (string)
- `detail` (boolean): false = compact answer (default); true = every matched record and full receipts.
- `identity` (object)
- `legal_notice` (string)
- `not_covered` (array): What this service does not cover (detail=true; also in /llms.txt).
- `official_check` (object)
- `privacy_note` (string)
- `provenance` (array): Freshness receipts for every upstream source used.
- `receipt` (object)
- `sections` (array): One section per registry, in the common registry-status shape.
- `summary` (object)
- `terms` (string): URL of the terms of service.

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

## Diagnostics

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

## Score history

- 2026-10-18: 67
- 2026-10-17: 66

## Common questions

### What is the Japan Entity Evidence MCP server?

Japan Entity Evidence is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-entity-evidence. Japanese public records on an organization: FSA, MOF, EDINET, ISA and gBizINFO lists. Evidence only. This page covers its hosted endpoint (https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp).

### Is the Japan Entity Evidence MCP server safe to use?

Japan Entity Evidence scores 67 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 Entity Evidence MCP server expose?

Japan Entity Evidence exposes 3 tools: catalog, entity_evidence_check, get_receipt. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.

### Does the Japan Entity Evidence MCP server require authentication?

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

### Is the Japan Entity Evidence MCP server still maintained?

Japan Entity Evidence 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://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp
- Website: https://jp-entity-evidence-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-jp-entity-evidence/jp-entity-evidence-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-jp-entity-evidence/jp-entity-evidence-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-jp-entity-evidence/jp-entity-evidence-production