OFD Reader (China e-invoices)
NPM · @APPMONSTER/MCP-OFD
Read Chinese OFD documents: e-invoice (fapiao) fields, official documents, statements. No keys.
Available components
Last scanned (11 hours ago)
Scores higher than 36% of npm servers
Category Documents and Files
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 Security31
- Malware scan not yet available for this package.Unverified
- 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 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to groove79/kmcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 341 tokens (~113/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 23 Oct 26 61
First indexed and scored.
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 23 Oct 2026 · Analysed npm/@appmonster/mcp-ofd@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | groove79/kmcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/groove79/kmcp/.github/workflows/publish.yml@refs/tags/ofd-v0.1.0 |
| Rekor log index | 3423337805 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bfd47450b40fed1a7c5f195ed45006ff9f7ca5e6632a9413d24d024b8f1f2633f3b8c7f7b0047412460a445e7f55dfbb4f1124fec3370b9c9aa857d5d |
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 102 packages
| Packages resolved | 102 |
|---|---|
| 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 →
ofd_info OFD file info ~96
Quick facts about an OFD file without the full text: title, author, creator software, creation date, page count, whether it is digitally signed, attachments, embedded tags.
| Name | Type | Req | Description |
|---|---|---|---|
| base64 | string | – | Base64 file contents (for clients that cannot share a path) |
| path | string | – | Local file path of a .ofd file |
| url | string | – | http(s) URL of a .ofd file |
No output schema declared.
No examples provided.
ofd_invoice_fields Read OFD e-invoice fields ~123
Extract structured fields from a Chinese OFD e-invoice (发票): invoice number and code, issue date, buyer and seller name and tax ID, amount before tax, tax, total. Uses the invoice's embedded tags, else the printed labels. Pass exactly one of path | url | base64.
| Name | Type | Req | Description |
|---|---|---|---|
| base64 | string | – | Base64 file contents (for clients that cannot share a path) |
| path | string | – | Local file path of a .ofd file |
| url | string | – | http(s) URL of a .ofd file |
No output schema declared.
No examples provided.
ofd_to_text Read OFD document ~122
Extract the text of a Chinese OFD document (GB/T 33190: e-invoices 电子发票/数电票, official documents, bank statements) in reading order, page by page. Pass exactly one of path | url | base64.
| Name | Type | Req | Description |
|---|---|---|---|
| base64 | string | – | Base64 file contents (for clients that cannot share a path) |
| maxChars | integer | – | – |
| path | string | – | Local file path of a .ofd file |
| url | string | – | http(s) URL of a .ofd file |
No output schema declared.
No examples provided.
How do I install the OFD Reader (China e-invoices) MCP server?
OFD Reader (China e-invoices) runs locally as an npm package, launched with npx -y @appmonster/mcp-ofd. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @appmonster/mcp-ofd
claude mcp add groove79-mcp-ofd -- npx -y @appmonster/mcp-ofd
What is the OFD Reader (China e-invoices) MCP server?
OFD Reader (China e-invoices) is an MCP server listed in the public MCP registry as io.github.groove79/mcp-ofd. Read Chinese OFD documents: e-invoice (fapiao) fields, official documents, statements. No keys. This page covers its npm package (@appmonster/mcp-ofd).
Is the OFD Reader (China e-invoices) MCP server safe to use?
OFD Reader (China e-invoices) scores 61 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 23 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 OFD Reader (China e-invoices) MCP server expose?
OFD Reader (China e-invoices) exposes 3 tools: ofd_to_text, ofd_invoice_fields, ofd_info. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.
Is the OFD Reader (China e-invoices) MCP server still maintained?
OFD Reader (China e-invoices) is still listed as active in the MCP registry. We last reached this channel on 23 October 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 OFD Reader (China e-invoices) MCP server under?
OFD Reader (China e-invoices) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.