search_journalLABSCO SUMMARY
The warning check covers both the old tables and the new embedded marker, which is where a naive lookup goes wrong.
The upstream data changed shape: from the 2026 edition the warning status is carried inline as a field rather than published as a separate list, and the tool scans both. That matters because a journal flagged under only one scheme would otherwise come back clean. The trend tool is the other reason to use this rather than a single lookup — a partition that has slipped across editions tells you something a current-year figure hides. Note the data is a local snapshot: it is as current as your last sync.
What it is
A journal-metrics lookup built on the ShowJCR data set: JCR impact factors, the Chinese Academy of Sciences partition tables, the international journal warning lists, the CCF recommended venue catalogue, and the computing-field quality grading. The data is synced once into a local SQLite database and queried from there.
What you get
- A journal looked up by name, returning impact factor, partition and warning status together rather than from three separate sources (search_journal).
- How a journal's partition has moved across editions, which is the question a single year's figure cannot answer (get_partition_trends).
- The international journal warning list searched by keyword, scanning both the traditional warning tables and the 2026 edition's embedded warning marker, so old and new sources are covered in one call (check_warning_journals).
- Several journals compared side by side in one call rather than looked up one at a time (compare_journals).
- Database information and statistics exposed as a resource, so you can see which editions the local copy actually holds.
- A journal-analysis prompt template shipped with the server.
Requirements
Python 3.10 or newer — a hard requirement of the MCP SDK — plus SQLite, which ships with Python. Install the dependencies, then run the data sync once before first use; it downloads and imports the tables locally. After that the server runs offline against that database. No account and no key.
Setup effort
Build from source — git clone https://github.com/yosh3289/jcr_mcp.git
USE CASES
Checking a journal before submitting to it
Impact factor, partition and warning status arrive together instead of from three separate lookups.
Choosing between several candidate venues
Compare them in one call rather than opening a tab per journal.
Spotting a journal whose standing is sliding
The partition across editions shows movement that this year's number does not.
Screening a reference list for flagged venues
Search the warning list by keyword, covering both the separate tables and the newer inline marker.
Knowing how current your data actually is
The database information resource says which editions the local copy holds.
4 tools
Listed in project docs. Your client may show a different list.
get_partition_trendscheck_warning_journalscompare_journalsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
Python 3.10+
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
Requirements: Python 3.10+ (a hard requirement of the mcp SDK) and SQLite3, which usually ships with Python.
git clone https://github.com/yosh3289/jcr_mcp.git
cd jcr_mcpInstall the dependencies:
pip install -r requirements.txtSync the data once before the first run:
python data_sync.pyWhen data_sync.py asks, choose 1 to sync all data, then wait for the download and import to finish.
Start the server:
python jcr_mcp_server.pyAdd the block below to the Claude Desktop config file (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on macOS), or register it in Claude Code with the one-line command.
MCP Clients
Claude Desktop
{
"mcpServers": {
"jcr-partition": {
"command": "<YOUR_PATH_TO_PYTHON>",
"args": [
"<YOUR_PATH_TO_JCR_MCP_SERVER>"
],
"cwd": "<YOUR_PATH_TO_PROJECT>"
}
}
}Claude Code
claude mcp add -s user jcr-partition -- <YOUR_PATH_TO_PYTHON> <YOUR_PATH_TO_JCR_MCP_SERVER>