# 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

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `regbase-mcp.local-connect-design.trade`: 70/100 (this document), [markdown](https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp.md), [page](https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp)

## Channel facts

- Endpoint: `https://regbase-mcp.local-connect-design.trade/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-11-21.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 247 tokens (~61/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add --transport http lexusdev7-jp-corp-diff 'https://regbase-mcp.local-connect-design.trade/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lexusdev7-jp-corp-diff": {
      "url": "https://regbase-mcp.local-connect-design.trade/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lexusdev7-jp-corp-diff": {
      "type": "http",
      "url": "https://regbase-mcp.local-connect-design.trade/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lexusdev7-jp-corp-diff]
url = "https://regbase-mcp.local-connect-design.trade/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lexusdev7-jp-corp-diff": {
      "type": "remote",
      "url": "https://regbase-mcp.local-connect-design.trade/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lexusdev7-jp-corp-diff --url 'https://regbase-mcp.local-connect-design.trade/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lexusdev7-jp-corp-diff:
    url: "https://regbase-mcp.local-connect-design.trade/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lexusdev7-jp-corp-diff": {
      "Transport": "http",
      "Url": "https://regbase-mcp.local-connect-design.trade/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lexusdev7-jp-corp-diff -t streamable-http -u 'https://regbase-mcp.local-connect-design.trade/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lexusdev7-jp-corp-diff": {
      "type": "http",
      "url": "https://regbase-mcp.local-connect-design.trade/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-11-20 (score 70, +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.

### 2026-11-18 (score 69, +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.

### 2026-11-16 (score 68, +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.

### 2026-11-14 (score 67, +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.

### 2026-11-12 (score 66, +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.

### 2026-11-10 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 64)

First indexed and scored.

## MCP tools (4)

### `get_latest_diff` (~101 tokens)

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.

Input parameters:

- `change_types` (array): Filter by change type; omit for all types.
- `max_results` (integer): Maximum items to return (1-100).
- `prefecture` (string): Exact prefecture name filter, e.g. 東京都.

### `lookup_company` (~62 tokens)

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.

Input parameters:

- `max_results` (integer)
- `query` (string, required): Corporate number or company name substring.

### `verify_signed_record` (~60 tokens)

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.

Input parameters:

- `record` (object, required): The signed record object to verify.

### `get_snapshot_info` (~24 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 64

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

## Links

- Remote endpoint: https://regbase-mcp.local-connect-design.trade/mcp
- Authorisation metadata: https://regbase-mcp.local-connect-design.trade/.well-known/oauth-protected-resource/mcp
- Website: https://regbase-mcp.local-connect-design.trade/
- Changelog RSS feed: https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp.json
- HTML version of this page: https://verifymcp.io/servers/lexusdev7-jp-corp-diff/regbase-mcp
