Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RegBase Japan Corporate Registry Diff

REMOTE · REGBASE-MCP.LOCAL-CONNECT-DESIGN.TRADE

Japan corporate registry daily diff: new, changed and closed companies, lookup, signed-record check

+3 this week 70 Trust /100

Last scanned (22 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security60
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 247 tokens (~61/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 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.

  • 12 Nov 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.

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 64

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://regbase-mcp.local-connect-design.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=local-connect-design.trade CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 5a3c2cd030e8d46d13aa421f5ef2712c
SANs: local-connect-design.trade, regbase-mcp.local-connect-design.trade, *.regbase-mcp.local-connect-design.trade
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of regbase-mcp.local-connect-design.trade. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
trade. DS published 64969 8 Verified
local-connect-design.trade. DS published 2371 13 Verified
regbase-mcp.local-connect-design.trade. Verified address RRset verified with the apex keys
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://regbase-mcp.local-connect-design.trade/mcp Verified 200
http (plaintext) http://regbase-mcp.local-connect-design.trade/mcp HTTPS enforced 301 https://regbase-mcp.local-connect-design.trade/mcp
MCP tools · 4 exposed · ~247 tokens

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 →

Tool Tokens
get_latest_diff ~101

Latest changes in Japan's National Tax Agency corporate registry (houjin bangou): newly registered, changed, closed and revived companies from the daily diff. Mirrors the RegBase jp-diff-feed actor.

NameTypeReqDescription
change_typesarray–Filter by change type; omit for all types.
max_resultsinteger–Maximum items to return (1-100).
prefecturestring–Exact prefecture name filter, e.g. 東京都.

No output schema declared.

No examples provided.

get_snapshot_info ~24

Describe the bundled registry snapshot: record counts, as-of date and source.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_company ~62

Look up a Japanese company by 13-digit corporate number (exact) or by name substring (Japanese or English). Mirrors the RegBase jp-company-lookup actor.

NameTypeReqDescription
max_resultsinteger––
querystringyesCorporate number or company name substring.

No output schema declared.

No examples provided.

verify_signed_record ~60

Verify a RegBase Ed25519-signed company evidence record offline against the published T3 public key (key_id derived at runtime). Mirrors the jp-signed-record actor's verify action.

NameTypeReqDescription
recordobjectyesThe signed record object to verify.

No output schema declared.

No examples provided.

Install

How do I install the RegBase Japan Corporate Registry Diff MCP server?

RegBase Japan Corporate Registry Diff is a hosted endpoint at https://regbase-mcp.local-connect-design.trade/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 · regbase-mcp.local-connect-design.trade

# add to Claude Code
claude mcp add --transport http lexusdev7-jp-corp-diff 'https://regbase-mcp.local-connect-design.trade/mcp'
Common questions

What is the RegBase Japan Corporate Registry Diff MCP server?

RegBase Japan Corporate Registry Diff is an MCP server listed in the public MCP registry as io.github.lexusdev7/jp-corp-diff. Japan corporate registry daily diff: new, changed and closed companies, lookup, signed-record check. This page covers its hosted endpoint (https://regbase-mcp.local-connect-design.trade/mcp).

Is the RegBase Japan Corporate Registry Diff MCP server safe to use?

RegBase Japan Corporate Registry Diff scores 70 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 RegBase Japan Corporate Registry Diff MCP server expose?

RegBase Japan Corporate Registry Diff exposes 4 tools: get_latest_diff, lookup_company, verify_signed_record, get_snapshot_info. Their descriptions and schemas cost roughly 247 tokens of context every time the server is loaded.

Does the RegBase Japan Corporate Registry Diff MCP server require authentication?

No. We connected to RegBase Japan Corporate Registry Diff without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RegBase Japan Corporate Registry Diff MCP server still maintained?

RegBase Japan Corporate Registry Diff is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the RegBase Japan Corporate Registry Diff MCP server?

VerifyMCP ran 12 checks on RegBase Japan Corporate Registry Diff, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about RegBase Japan Corporate Registry Diff: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.