Japan Qualified Invoice Issuers (Corporations) MCP server
io.github.mk-career-planning/jp-invoice-registrymk-career-planningstreamable-httpv0.1.0Scanned
Japan NTA qualified invoice issuer status of corporations by T-number. Records daily changes.
4 tools: 1 change things and 3 only 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
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Qualified Invoice Issuers (Corporations) MCP server can do
The Japan Qualified Invoice Issuers (Corporations) MCP server is published by the GitHub account mk-career-planning. It has 4 tools. It can create or change data (1 tool: invoice_registration_changes), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (invoice_registration_lookup and invoice_registration_changes).
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 once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 0.1.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 1Claude Code: ask
invoice_registration_changesWhich 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 …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 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
Only reads 3Show 3 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
invoice_registration_lookupIs this Japanese corporation a registered qualified invoice issuer, since when, and was it cancelled or did it expire?Reads text others writeNo findings
Why it is in this group
- The name "invoice_registration_lookup" says "lookup": a word for reading.
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 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'.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: 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.
Looked at Nov 15, 2026, 13:23 UTC, unchanged since Oct 24, 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including invoice_registration_changes (write)
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.
Tools1 changed.~1 changedView diff
- Changed:get_receiptOnly readsdescription
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http jp-invoice-registry https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcpclaude mcp add --transport http jp-invoice-registry https://jp-invoice-registry-production.mk-career-planning.workers.dev/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__jp-invoice-registry__catalog",
"mcp__jp-invoice-registry__invoice_registration_lookup",
"mcp__jp-invoice-registry__get_receipt"
],
"ask": [
"mcp__jp-invoice-registry__invoice_registration_changes"
],
"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-invoice-registry. Review it before you use it.
Capability tags behind 2 rules
- mcp__jp-invoice-registry__invoice_registration_lookup untrusted-input
- mcp__jp-invoice-registry__invoice_registration_changes 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-invoice-registry/verify?hash=99410b6aceb0fbdfd27c997d6a608013887f875351f7bc2872782e6ae1d5e861" | jq -e '.changed == false'Pinned hash 99410b6aceb0, from Nov 8, 2026, 22: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-invoice-registry/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.mk-career-planning/jp-invoice-registry)Source: MCP Registry. Synced Oct 23, 2026, 22:18 UTC.
Japan Qualified Invoice Issuers (Corporations) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Japan Qualified Invoice Issuers (Corporations) MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 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 Qualified Invoice Issuers (Corporations) 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 Qualified Invoice Issuers (Corporations) 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 Qualified Invoice Issuers (Corporations) MCP server have?
- 4 tools: 1 write, 3 read. invoice_registration_changes, catalog, invoice_registration_lookup and get_receipt.
Does the Japan Qualified Invoice Issuers (Corporations) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Japan Qualified Invoice Issuers (Corporations) 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 Qualified Invoice Issuers (Corporations) MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.