Skip to content

Japan Entity Evidence MCP server

io.github.mk-career-planning/jp-entity-evidencemk-career-planningstreamable-httpv0.2.0Scanned

Japanese public records on 1-10 companies per call: FSA, MOF, EDINET, ISA, gBizINFO. Evidence only.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Japan Entity Evidence MCP server can do

The Japan Entity Evidence MCP server is published by the GitHub account mk-career-planning. It has 4 tools. It can create or change data (2 tools: entity_evidence_check and entity_evidence_batch), but cannot delete data. 2 tools only read.

2 tools bring in text other people can write (entity_evidence_check and entity_evidence_batch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • entity_evidence_batchSame check as entity_evidence_check for 1-10 Japanese organizations in one call (by corporate number, exact name or registration number): per company the full evidence with each se…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Same check as entity_evidence_check for 1-10 Japanese organizations in one call (by corporate number, exact name or registration number): per company the full evidence with each section's source, retrieval time, version date and what was not checked, plus a summary counting resolved, name-only, ambiguous, not found and unknown, and unavailable sources. Ambiguous names are never resolved by guess. Not charged if no company can be checked. Not a compliance determination.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • entity_evidence_checkFor checks across several Japanese registries: FSA registers, warnings and enforcement cases, MOF asset-freeze list, EDINET filings, ISA support organizations, CAA actions, gBizINF…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    For checks across several Japanese registries: FSA registers, warnings and enforcement cases, MOF asset-freeze list, EDINET filings, ISA support organizations, CAA actions, gBizINFO where connected. Gives 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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • catalogList the tools of this server with prices, data sources, licensing, daily limits and data freshness.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

    Annotations the server declares

    • readOnlyHint: true
  • get_receiptRe-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment.No findings

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    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 30 days after settlement.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including entity_evidence_check (write), entity_evidence_batch (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2
  3. Tools1 added, 1 changed.+1 added~1 changedView diff

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http jp-entity-evidence https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp
claude mcp add --transport http jp-entity-evidence https://jp-entity-evidence-production.mk-career-planning.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jp-entity-evidence__catalog",
      "mcp__jp-entity-evidence__get_receipt"
    ],
    "ask": [
      "mcp__jp-entity-evidence__entity_evidence_check",
      "mcp__jp-entity-evidence__entity_evidence_batch"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jp-entity-evidence. Review it before you use it.

Capability tags behind 2 rules
  • mcp__jp-entity-evidence__entity_evidence_check untrusted-input
  • mcp__jp-entity-evidence__entity_evidence_batch untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mk-career-planning/jp-entity-evidence/verify?hash=765dd803b58fb7a2518e3067977dd3b2858493fb2a65b7236cf29fc92df9968a" | jq -e '.changed == false'

Pinned hash 765dd803b58f, from Nov 14, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.mk-career-planning/jp-entity-evidence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.mk-career-planning/jp-entity-evidence
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mk-career-planning/jp-entity-evidence.svg)](https://radar.anlyon.com/servers/io.github.mk-career-planning/jp-entity-evidence)

Source: MCP Registry. Synced Nov 1, 2026, 11:17 UTC.

Japan Entity Evidence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Japan Entity Evidence MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Japan Entity Evidence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Japan Entity Evidence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Japan Entity Evidence MCP server have?

4 tools: 2 write, 2 read. entity_evidence_check, entity_evidence_batch, catalog and get_receipt.

Does the Japan Entity Evidence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Japan Entity Evidence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Japan Entity Evidence MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.