Mcp Jp Doc Intel

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.0Updated Oct 24, 2026

Japanese document AI for agents — invoice/meishi extraction, OCR, classification (hosted API).

VerifiedSTDIODesktop onlyFiles & StorageAI & ML

Overview

AI-generated overview

A local MCP server that gives an assistant Japanese document AI tools for invoice and business-card extraction, OCR, and classification via a hosted API.

What you can do
It exposes Japanese document intelligence capabilities to an assistant: extracting structured data from invoices and meishi (business cards), running OCR on document images, and classifying documents. The work is performed by a hosted API rather than locally, with the server acting as the local stdio bridge. No individual tools are listed in the supplied manifest.
When to use it
Worth adding when an assistant needs to read or organize Japanese business documents such as invoices and business cards, or to run OCR and document classification on Japanese-language files. It is a narrow, document-focused server rather than a general file or OCR toolkit.
Requirements
Runs as a local process on the user's machine via the npm package @infoinlet/mcp-jp-doc-intel over stdio, so Node.js and npm are needed. It is desktop-only and not web-executable. The manifest declares no authentication, environment variables, or headers, but the description says it uses a hosted API, so network access and any credentials that API requires should be confirmed before installing.
Before you install
The description states the extraction, OCR, and classification work is done by a hosted API, so document contents are sent to a third party; avoid feeding it sensitive or confidential documents unless that handling is acceptable. The manifest declares no credentials, yet a hosted API normally needs some form of key or account, so verify what is actually requested at install time. No tools are listed, so the exact read/write behavior cannot be confirmed from the supplied information.

Installation

In SourceWeft

  1. Open Mcp Jp Doc Intel 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

This repository has no README.

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.