# Japan Qualified Invoice Issuers (Corporations) (remote · jp-invoice-registry-production.mk-career-planning.workers.dev)

Japan NTA qualified invoice issuer status of corporations by T-number. Records daily changes.

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

## Components

- remote · `jp-invoice-registry-production.mk-career-planning.workers.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production.md), [page](https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production)

## Channel facts

- Endpoint: `https://jp-invoice-registry-production.mk-career-planning.workers.dev/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-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 498 tokens (~124/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 Japan Qualified Invoice Issuers (Corporations) MCP server?

Japan Qualified Invoice Issuers (Corporations) is a hosted endpoint at https://jp-invoice-registry-production.mk-career-planning.workers.dev/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 mk-career-planning-jp-invoice-registry 'https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mk-career-planning-jp-invoice-registry": {
      "url": "https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mk-career-planning-jp-invoice-registry": {
      "type": "http",
      "url": "https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mk-career-planning-jp-invoice-registry]
url = "https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mk-career-planning-jp-invoice-registry": {
      "type": "remote",
      "url": "https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mk-career-planning-jp-invoice-registry --url 'https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mk-career-planning-jp-invoice-registry:
    url: "https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mk-career-planning-jp-invoice-registry": {
      "Transport": "http",
      "Url": "https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mk-career-planning-jp-invoice-registry -t streamable-http -u 'https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mk-career-planning-jp-invoice-registry": {
      "type": "http",
      "url": "https://jp-invoice-registry-production.mk-career-planning.workers.dev/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-03 (score 73, +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-01 (score 72, +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-10-31 (score 71, 0)

- [security] Tool “get_receipt” rewrote its description, which is the text the model reads

### 2026-10-30 (score 71, +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-10-28 (score 70, +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-10-26 (score 69, +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-10-24 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 67)

First indexed and scored.

## MCP tools (4)

### `catalog` (~27 tokens)

Catalog: tools, prices and limits

List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

Output parameters:

- `daily_limits` (object): Daily limits of paid calls (calls, usd, timezone) or a misconfiguration notice.
- `fetch_status_values` (object)
- `legal` (object)
- `paused` (object): Operator pause flags (true = paused).
- `payment` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `server` (object)
- `terms` (string): URL of the terms of service.
- `tools` (array): Every tool of this server with its price.

### `invoice_registration_lookup` (~181 tokens)

Look up a qualified invoice issuer registration (corporations)

Is this Japanese corporation a registered qualified invoice issuer, since when, and was it cancelled or did it expire? Give number (T1000020109142) or corporate_number (13 digits); the check digit is validated. Returns listed, expired (cancellation or expiry date passed) or unknown, with NTA's published dates, the difference file used, fetched_at and recorded changes. Corporations only. A number not seen in the recorded files is unknown, never 'not registered'.

Input parameters:

- `corporate_number` (string): Corporate number (houjin bangou), 13 digits, e.g. 1000020109142; looked up as T + the 13 digits
- `number` (string): Registration number: T followed by 13 digits, e.g. T1000020109142 (width, spaces and hyphens ignored)

Output parameters:

- `answered_at` (string)
- `attribution` (object)
- `data_version` (object)
- `legal_notice` (string)
- `nta_notice` (object): Always pass on: cancellation and expiry are published facts with the dates as published, not an assessment of the business.
- `official_check` (object): Read first: as published by NTA; check the official site listed here before relying on this answer.
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `recorded_changes` (array)
- `registration`
- `registry_status` (object)
- `status` (string): listed = the latest recorded record shows a registration; expired = it shows a cancellation or expiry date that has passed; unknown = not in the changes recorded since tracking_since while the full f…
- `status_note` (string)
- `terms` (string): URL of the terms of service.
- `unknown_reason` (string|null)

### `invoice_registration_changes` (~207 tokens)

Qualified invoice issuer changes (corporations)

Which Japanese corporations were newly registered as qualified invoice issuers, had their published details changed, or had their registration cancelled or expired, in NTA's daily difference files since a date? From this service's own record of the files it read (NTA keeps them 40 business days). Each change has the file date, observed_at, the event type and the dates as published. Corporations only. Free window: last 30 days; page with next_cursor.

Input parameters:

- `cursor` (string): next_cursor from a previous answer, to read the next page
- `event_type` (string): Optional filter: registered, details_changed, expired, cancelled, record_deleted or past_record
- `limit` (integer): Maximum number of changes, 1-500 (default 100)
- `since` (string, required): ISO 8601 date or date-time with time zone, e.g. 2026-10-01; changes in difference files created on or after that date

Output parameters:

- `answered_at` (string)
- `attribution` (object)
- `changes` (array): Corporate rows of the NTA difference files read by this service, oldest first.
- `coverage` (object)
- `files_observed` (array)
- `history_note` (string)
- `history_window` (object): Free history window applied to this answer.
- `legal_notice` (string)
- `next_cursor` (string|null)
- `nta_notice` (object): Always pass on: cancellation and expiry are published facts with the dates as published, not an assessment of the business.
- `official_check` (object): Read first: as published by NTA; check the official site listed here before relying on this answer.
- `provenance` (array): Freshness receipts for every upstream source used.
- `query` (object)
- `terms` (string): URL of the terms of service.
- `tracking_since` (string|null): Date of the first NTA difference file this service read. Nothing before it was observed.
- `truncated` (boolean)

### `get_receipt` (~83 tokens)

Get receipt of a paid call

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.

Input parameters:

- `receipt_id` (string, required): The receipt_id returned with a paid result ("rcpt_" + 64 hex characters).

Output parameters:

- `payment` (object)
- `provenance` (array): Freshness receipts for every upstream source used.
- `receipt_id` (string): Receipt id of the settled paid call ("rcpt_" + 64 hex). Use with get_receipt.
- `result`: The stored result, exactly as returned by the paid call.
- `settled_at` (string|null)
- `terms` (string): URL of the terms of service.
- `tool` (string): Name of the paid tool that produced the result.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 67

## Common questions

### What is the Japan Qualified Invoice Issuers (Corporations) MCP server?

Japan Qualified Invoice Issuers (Corporations) is an MCP server listed in the public MCP registry as io.github.mk-career-planning/jp-invoice-registry. Japan NTA qualified invoice issuer status of corporations by T-number. Records daily changes. This page covers its hosted endpoint (https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp).

### Is the Japan Qualified Invoice Issuers (Corporations) MCP server safe to use?

Japan Qualified Invoice Issuers (Corporations) scores 73 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 Japan Qualified Invoice Issuers (Corporations) MCP server expose?

Japan Qualified Invoice Issuers (Corporations) exposes 4 tools: catalog, invoice_registration_lookup, invoice_registration_changes, get_receipt. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.

### Does the Japan Qualified Invoice Issuers (Corporations) MCP server require authentication?

No. We connected to Japan Qualified Invoice Issuers (Corporations) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan Qualified Invoice Issuers (Corporations) MCP server still maintained?

Japan Qualified Invoice Issuers (Corporations) is still listed as active in the MCP registry. We last reached this channel on 5 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 Japan Qualified Invoice Issuers (Corporations) MCP server?

VerifyMCP ran 12 checks on Japan Qualified Invoice Issuers (Corporations), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Japan Qualified Invoice Issuers (Corporations): HTTPS. 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://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp
- Website: https://jp-invoice-registry-production.mk-career-planning.workers.dev/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production.json
- HTML version of this page: https://verifymcp.io/servers/mk-career-planning-jp-invoice-registry/jp-invoice-registry-production