Denpyo Mcp

io.github.vladic-corpPublished by GitHub account vladic-corpv0.1.1Updated Oct 24, 2026

Japanese invoice/receipt OCR + tax registration-number (T-number) verification, via x402.

VerifiedSTDIODesktop onlyFiles & StorageFinance

Overview

AI-generated overview

Local MCP server that reads Japanese invoices and receipts into structured JSON and verifies invoice registration numbers, paying per call in USDC.

What you can do
Read Japanese invoices from a local file path or URL into structured JSON with vendor, line items and 8%/10% consumption-tax breakdown, first two pages only, with registration-number verification in the same call (paid). Read Japanese receipts from a photo or PDF, first page only, into structured JSON with the same verification (paid). Check a T+13-digit qualified-invoice registration number against the National Tax Agency registry, optionally matching a name (paid). Fetch a free machine-readable service catalog.
When to use it
Useful when an assistant needs to extract structured data from Japanese invoices or receipts, or confirm whether an issuer is a registered qualified-invoice issuer, without signing up for an account.
Requirements
Runs locally via npx (Node.js). Needs a wallet private key holding USDC, supplied as EVM_PRIVATE_KEY (Base, 0x format) or SVM_PRIVATE_KEY (Solana, base58); one of the two is required. Network access to the remote API and the NTA registry. Desktop only.
Before you install
Requires a private key for a wallet holding USDC; the wallet itself is the account, so anyone with the key controls the funds. Each analysis costs money ($0.04 invoice, $0.03 receipt, $0.01 number check) paid in USDC per call; failed analyses are stated not to be charged. Documents are sent to a third-party API, though stated to be processed transiently and not stored.

Installation

In SourceWeft

  1. Open Denpyo Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

denpyo-mcp

MCP server for Denpyo — Japan Invoice & Receipt Reader API (https://denpyo-api.hp-vladic.workers.dev).

OCR Japanese invoices (請求書) and receipts (領収書) from local files or URLs into structured JSON — vendor/merchant, line items, 8%/10% consumption-tax breakdown — with the qualified-invoice registration number (インボイス登録番号, T+13 digits) extracted and verified against the National Tax Agency registry in the same call.

Pays per call via x402 (USDC on Base or Solana). The wallet is the account — no signup, no API keys.

Usage

json
{  "mcpServers": {    "denpyo": {      "command": "npx",      "args": ["-y", "denpyo-mcp"],      "env": { "EVM_PRIVATE_KEY": "0x... (Base wallet holding USDC)" }    }  }}

Solana instead: set SVM_PRIVATE_KEY (base58) rather than EVM_PRIVATE_KEY.

Tools

ToolCostWhat it does
read_japan_invoice$0.04Invoice (local file path or URL) → structured JSON + NTA verification. First 2 pages
read_japan_receipt$0.03Receipt (photo/PDF, local path or URL) → structured JSON + NTA verification. First page
verify_japan_invoice_number$0.01Registry-only check of a T+13-digit number, optional name match
denpyo_catalogfreeMachine-readable service catalog

Example prompts once connected: "Read C:\scans\invoice-0712.pdf and tell me if the issuer is a registered qualified-invoice issuer" / "Process every receipt photo in this folder and total the deductible amounts by tax rate."

Failed analyses (unreadable files) return errors and are not charged. Documents are processed transiently and never stored.

Sister package: kaisha-mcp — Japan company registry lookups, new-company feeds, business-day math.

MIT — vladic-corp/denpyo-api

Source: mcp/README.md at commit 240482e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.