io.github.infoinlet-marketplace/mcp-jp-doc-intel
NPM · @INFOINLET/MCP-JP-DOC-INTEL
Japanese document AI for agents — invoice/meishi extraction, OCR, classification (hosted API).
Available components
Last scanned (15 hours ago)
Scores higher than 62% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 158 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 627 tokens (~104/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 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.
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/@infoinlet/mcp-jp-doc-intel@0.1.0
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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
classify_text ~60
Cheaply classify pasted text into a Japanese document kind (議事録/稟議書/仕様書/履歴書/契約書/請求書/始末書/generic). No file needed.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
extract_document ~131
OCR/parse any document to text; optionally classify its Japanese document kind. Multi-page PDFs are split and processed page-by-page.
| Name | Type | Req | Description |
|---|---|---|---|
| classify | boolean | – | Also classify the JP document kind. |
| content_base64 | string | – | Alternative to path: the file bytes, base64-encoded. |
| filename | string | – | Filename (used to infer type); required with content_base64. |
| language | string | – | – |
| mime | string | – | Optional explicit content type (else inferred from the filename). |
| path | string | – | Path to a local file (PDF/image/text, ≤20MB). |
No output schema declared.
No examples provided.
extract_handwriting ~116
VLM OCR for handwriting, hanko (stamps), and faxed/scanned artifacts. Returns recognized text.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | – | Alternative to path: the file bytes, base64-encoded. |
| filename | string | – | Filename (used to infer type); required with content_base64. |
| language | string | – | – |
| mime | string | – | Optional explicit content type (else inferred from the filename). |
| path | string | – | Path to a local file (PDF/image/text, ≤20MB). |
No output schema declared.
No examples provided.
extract_invoice ~161
Extract structured fields from a Japanese (or English) invoice — vendor, invoice number, validated 適格請求書 T-number, dates (元号→Gregorian), subtotal/tax/total (zero-decimal currency aware), tax breakdown, and line items. Give a local `path` or `content_base64`+`filename`.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | – | Alternative to path: the file bytes, base64-encoded. |
| filename | string | – | Filename (used to infer type); required with content_base64. |
| language | string | – | – |
| mime | string | – | Optional explicit content type (else inferred from the filename). |
| path | string | – | Path to a local file (PDF/image/text, ≤20MB). |
No output schema declared.
No examples provided.
extract_meishi ~127
Parse a business-card (meishi) image into name, kana, company, title, email, phone, and address. Give a local `path` or `content_base64`+`filename`.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | – | Alternative to path: the file bytes, base64-encoded. |
| filename | string | – | Filename (used to infer type); required with content_base64. |
| mime | string | – | Optional explicit content type (else inferred from the filename). |
| path | string | – | Path to a local file (PDF/image/text, ≤20MB). |
No output schema declared.
No examples provided.
usage ~32
Show this API key’s usage/quota (trial keys show used/limit/remaining + expiry; subscribed keys are unlimited).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.infoinlet-marketplace/mcp-jp-doc-intel server?
io.github.infoinlet-marketplace/mcp-jp-doc-intel runs locally as an npm package, launched with npx -y @infoinlet/mcp-jp-doc-intel. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @infoinlet/mcp-jp-doc-intel
claude mcp add infoinlet-marketplace-mcp-jp-doc-intel -- npx -y @infoinlet/mcp-jp-doc-intel
What is the io.github.infoinlet-marketplace/mcp-jp-doc-intel server?
io.github.infoinlet-marketplace/mcp-jp-doc-intel is listed in the public MCP registry as io.github.infoinlet-marketplace/mcp-jp-doc-intel. Japanese document AI for agents, invoice/meishi extraction, OCR, classification (hosted API). This page covers its npm package (@infoinlet/mcp-jp-doc-intel).
Is the io.github.infoinlet-marketplace/mcp-jp-doc-intel server safe to use?
io.github.infoinlet-marketplace/mcp-jp-doc-intel scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting 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.infoinlet-marketplace/mcp-jp-doc-intel server expose?
io.github.infoinlet-marketplace/mcp-jp-doc-intel exposes 6 tools: extract_invoice, extract_document, extract_handwriting, extract_meishi, classify_text, usage. Their descriptions and schemas cost roughly 627 tokens of context every time the server is loaded.
Is the io.github.infoinlet-marketplace/mcp-jp-doc-intel server still maintained?
io.github.infoinlet-marketplace/mcp-jp-doc-intel 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.infoinlet-marketplace/mcp-jp-doc-intel server under?
io.github.infoinlet-marketplace/mcp-jp-doc-intel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.infoinlet-marketplace/mcp-jp-doc-intel server?
VerifyMCP ran 15 checks on io.github.infoinlet-marketplace/mcp-jp-doc-intel, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.infoinlet-marketplace/mcp-jp-doc-intel: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.