io.github.CloudCorpRecords/jpverify

jpverify

Is the io.github.CloudCorpRecords/jpverify MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-10.

Verify Japanese companies: corporate numbers, invoice registrations, profiles and addresses.

alive probed 2026-11-14 · unchanged since 2026-11-10

6tools

2.5ktokens in Claude Opus 5.5

1.2 %of Claude's 200k window

1.0×the median server

289 msto initialize

5 msto list tools

Run it: npx -y @reneturcios/jpverify@0.1.0 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: jpverify 0.1.0
Capabilities: tools
Instructions: none
Of a 1M window: 0.2 % of a 1M context window
Count: 2.5k tokens in Claude Opus 5.5, exact, measured 2026-11-10. With the Claude Code prefix mcp__…__ on each tool name: 2.5k. The o200k_base estimate is 1.7k. Counted again when the tool definitions change. Method.
Repository: https://github.com/CloudCorpRecords/jpverify
Registry: active, updated 2026-11-10 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.47×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
jp_calendar	553	376	22 %
normalize_address	509	346	21 %
verify_invoice_number	454	309	18 %
resolve_company	409	278	17 %
verify_company	281	191	11 %

These registry entries have the same tool names and the same schema sizes.

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention jpverify or registrations or addresses.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.