io.github.infoinlet-marketplace/mcp-jp-doc-intel
NPM · @INFOINLET/MCP-JP-DOC-INTEL · SCANNED AUG 3
Japanese document AI for agents — invoice/meishi extraction, OCR, classification (hosted API).
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 64 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @infoinlet/mcp-jp-doc-intel
claude mcp add infoinlet-marketplace-mcp-jp-doc-intel -- npx -y @infoinlet/mcp-jp-doc-intel
codex mcp add infoinlet-marketplace-mcp-jp-doc-intel -- npx -y @infoinlet/mcp-jp-doc-intel
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"infoinlet-marketplace-mcp-jp-doc-intel": {
"type": "local",
"command": [
"npx",
"-y",
"@infoinlet/mcp-jp-doc-intel"
],
"enabled": true
}
}
} openclaw mcp add infoinlet-marketplace-mcp-jp-doc-intel --command npx --arg -y --arg @infoinlet/mcp-jp-doc-intel
mcp_servers:
infoinlet-marketplace-mcp-jp-doc-intel:
command: "npx"
args: ["-y", "@infoinlet/mcp-jp-doc-intel"] {
"mcpServers": {
"infoinlet-marketplace-mcp-jp-doc-intel": {
"command": "npx",
"args": [
"-y",
"@infoinlet/mcp-jp-doc-intel"
]
}
}
} 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.
- 2 Aug 26 +62
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 1 Aug 26 −15
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 39
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 3 Aug 2026 · Analysed npm/@infoinlet/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.