pickfit

BrowseMCP servers

jp-lit-mcp

MCP server for cross-searching Japanese scholarly literature and digital archives via AI apps.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • npm:zod 3.25.76 Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)

Linux x86_64

You need first

  • Runtimes: Node.js >=22
  • Keys or accounts: CINII_RESEARCH_APP_ID, OPENALEX_API_KEY, CROSSREF_MAILTO
  1. Install jp-lit-mcp globally (preferred over npx fetch)

    npm install -g jp-lit-mcp

Check that it works

jp-lit-mcp --version

The output should contain “0.19.0”.

First thing to try

jp-lit-mcp doctor

Add it to your agent

claude mcp add jp-lit-mcp -- jp-lit-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "jp-lit-mcp": {
      "command": "jp-lit-mcp",
      "args": []
    }
  }
}

Run jp-lit-mcp doctor to check the setup, then add jp-lit-mcp as an MCP server in your AI app so its tools such as jp_lit_start_session and jp_lit_search become available.

What it does

  • Search Japanese literature databases
    Not tested
  • Check that bibliography entries are real and correct
    Not tested
  • Read TEI/XML texts with their structural markup
    Not tested
  • Compare classical books side by side through IIIF
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Good for

  • search books, papers, magazine articles, research projects and minutes by theme
  • search full-text OCR from NDL Digital Collections
  • extract chapters, poems and historical records with variants from saved TEI/XML
  • compare public IIIF materials side by side and read images with source text
  • verify whether literature lists contain non-existent or confused entries

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.19.0

An MCP client handshake over stdio listed 30 tools, and a call to jp_lit_start_session returned a result.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.