Japan corporate registry daily diff: new, changed and closed companies, lookup, signed-record check
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
RegBase API key for tool calls (initialize and tools/list are open for registry and health checks). Planned pricing: $0.01 per tool call.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Exact prefecture name filter, e.g. 東京都.
Maximum items to return (1-100).
Filter by change type; omit for all types.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http jp-corp-diff https://regbase-mcp.local-connect-design.trade/mcp \ --header 'X-API-Key: YOUR_X_API_KEY'
Headers
X-API-Key (required): RegBase API key for tool calls (initialize and tools/list are open for registry and health checks). Planned pricing: $0.01 per tool call.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.
| Argument | Type | Description |
|---|---|---|
| prefecture | string | Exact prefecture name filter, e.g. 東京都. |
| max_results | integer | Maximum items to return (1-100). |
| change_types | array | Filter by change type; omit for all types. |
{
"type": "object",
"properties": {
"prefecture": {
"type": "string",
"description": "Exact prefecture name filter, e.g. 東京都."
},
"max_results": {
"type": "integer",
"default": 20,
"description": "Maximum items to return (1-100)."
},
"change_types": {
"type": "array",
"items": {
"enum": [
"new",
"changed",
"closed",
"revival",
"other"
],
"type": "string"
},
"description": "Filter by change type; omit for all types."
}
}
}Describe the bundled registry snapshot: record counts, as-of date and source.
No arguments.
{
"type": "object",
"properties": {}
}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.
| Argument | Type | Description |
|---|---|---|
| query* | string | Corporate number or company name substring. |
| max_results | integer |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Corporate number or company name substring."
},
"max_results": {
"type": "integer",
"default": 10
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| record* | object | The signed record object to verify. |
{
"type": "object",
"required": [
"record"
],
"properties": {
"record": {
"type": "object",
"description": "The signed record object to verify."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 9, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.