io.github.vladic-corp/denpyo-mcp
NPM · DENPYO-MCP
Japanese invoice/receipt OCR + tax registration-number (T-number) verification, via x402.
Available components
Last scanned (1 hour ago)
Scores higher than 65% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 207 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 108 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 520 tokens (~130/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/denpyo-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 207 packages
| Packages resolved | 207 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
denpyo_catalog ~34
Free: machine-readable catalog of the Denpyo API (endpoints, prices, payment networks). No payment required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_japan_invoice ~183
OCR a Japanese invoice (請求書) into structured JSON: vendor, customer, invoice id, dates, line items with tax rates, and the 8%/10% consumption-tax breakdown. The qualified-invoice registration number (T + 13 digits) is extracted AND verified against the National Tax Agency registry (active/cancelled, registered-name match, corporate record) in the same call. Accepts a LOCAL file path (PDF/JPEG/PNG, max 8MB) or a public URL. First 2 pages analyzed. Cost: $0.04 (x402/USDC). Failed analyses are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Local path to the invoice file (PDF/JPEG/PNG/TIFF/HEIF) |
| url | string | – | Public http(s) URL of the invoice document (alternative to file) |
No output schema declared.
No examples provided.
read_japan_receipt ~169
OCR a Japanese receipt (領収書/レシート) into structured JSON: merchant, transaction date & time, items, totals and the 8%/10% consumption-tax breakdown. The qualified-invoice registration number is extracted and verified against the National Tax Agency registry, so you know instantly whether the receipt supports input-tax credit (仕入税額控除). Accepts a LOCAL file path (photo or PDF, max 8MB) or a public URL. First page analyzed. Cost: $0.03 (x402/USDC). Failed analyses are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | Local path to the receipt file (photo JPEG/PNG or PDF) |
| url | string | – | Public http(s) URL of the receipt (alternative to file) |
No output schema declared.
No examples provided.
verify_japan_invoice_number ~134
Verify a Japan qualified-invoice-issuer registration number (インボイス登録番号, "T" + 13 digits) against the National Tax Agency registry — no OCR. Returns active/cancelled/not-found, registration date, registered name, corporate registry record, and an optional fuzzy name-match. Cheapest pre-payment counterparty check for Japanese invoices. Cost: $0.01 (x402/USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Issuer name to fuzzy-match against the registered name |
| number | string | yes | Registration number, e.g. T1180301018771 (leading T optional) |
No output schema declared.
No examples provided.
How do I install the io.github.vladic-corp/denpyo-mcp server?
io.github.vladic-corp/denpyo-mcp runs locally as an npm package, launched with npx -y denpyo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · denpyo-mcp
claude mcp add vladic-corp-denpyo-mcp -- npx -y denpyo-mcp
What is the io.github.vladic-corp/denpyo-mcp server?
io.github.vladic-corp/denpyo-mcp is listed in the public MCP registry as io.github.vladic-corp/denpyo-mcp. Japanese invoice/receipt OCR + tax registration-number (T-number) verification, via x402. This page covers its npm package (denpyo-mcp).
Is the io.github.vladic-corp/denpyo-mcp server safe to use?
io.github.vladic-corp/denpyo-mcp scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.vladic-corp/denpyo-mcp server expose?
io.github.vladic-corp/denpyo-mcp exposes 4 tools: read_japan_invoice, read_japan_receipt, verify_japan_invoice_number, denpyo_catalog. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.
Is the io.github.vladic-corp/denpyo-mcp server still maintained?
io.github.vladic-corp/denpyo-mcp 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 licence is the io.github.vladic-corp/denpyo-mcp server under?
io.github.vladic-corp/denpyo-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.