mcpbeat Sign in

Japan Entity Evidence MCP Server

answering

Japan Entity Evidence is answering right now. Last checked 5 min ago. It exposes 3 tools.

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

Uptime history 8 days of history
8 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
1210 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Japan Entity Evidence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add jp-entity-evidence --transport http https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.jp-entity-evidence]
url = "https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "jp-entity-evidence": {
      "url": "https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "jp-entity-evidence": {
      "type": "http",
      "url": "https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

catalog
catalog
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
entity
entity_evidence_check
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.
receipt
get_receipt
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.

Endpoints

URLTransportStateLatencyChecked
https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp streamable-http answering 1018 ms 5 min ago

Alternatives to Japan Entity Evidence

same job, measured the same way
補助金AI
by mkisama94

Search Japanese subsidies and public company data using J-Grants, gBizINFO, and EDINET.

15 tools answering
Rubric MCP Server
by 0xsims

Attest agent decisions and verify records on a public ledger. Evidence, not just data.

203 installs/wk local only
Japan SSW Registered Support Organizations
by mk-career-planning

Is this Japanese SSW support organization in ISA's list? Hosted; tracks list changes. Relay only.

4 tools answering
HODLXXI Read-Only
by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering
Wikidata + Google Knowledge Graph MCP
by dondego

Read-only Wikidata tools and identity evidence. Local optional Google KG; bounded public remote.

175 installs/wk 8 tools answering
BizFetch
by bizfetch

Judge Japanese companies against your criteria using Japan's public data (gBizINFO, NTA, EDINET).

answering
SourceFinch
by sourcefinch

Evidence-grade monitoring of public web sources: changes, records and exports. Free plan available.

answering
C
Circuit AI MCP
by wrnreed-analytics

Public collaboration for AI agents: find requests, share evidence, and form groups.

34 installs/wk local only

Japan Entity Evidence — questions

Answers built from our own checks of this server.

What can Japan Entity Evidence do?
It exposes 3 tools, read directly from the server on our last check. Among them: catalog, entity_evidence_check, get_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Japan Entity Evidence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1210 ms. The bar chart above shows every period we have measured.
How do I connect Japan Entity Evidence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Japan Entity Evidence need an API key?
No. Japan Entity Evidence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Japan Entity Evidence?
It answers our handshake in 1210 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.