Prumo MCP server

by TomD4vs·io.github.TomD4vs/prumo·v0.9.7·5 stars

No reviews yet

Checks the context files a coding agent reads against the git index, and reports what drifted.

A89/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A89/100

full report

Adoption

Growing

5 stars405 downloads/wk

Reviews

Write one

Nobody has reviewed Prumo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Prumo tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

prumo_budget
Reports what the context files cost the agent: bytes, lines, words and an estimate of tokens at four characters each, and when each is read, at every session with the files a CLAUDE.md imports, or only when used, as a skill, the note of a folder or a scoped rule is, the cost at every session first; how much each grew since an earlier commit, the one thirty days ago unless `since` names another; an
prumo_check
Checks the context files a coding agent reads (CLAUDE.md, AGENTS.md, SKILL.md, .cursor/rules and the rest) against the git index of a repository. Reports paths whose letter case disagrees with git, broken [[wikilinks]], markdown links, heading anchors and @ imports of a CLAUDE.md, paths that no longer exist, commands naming a script or target no package.json, Makefile or composer.json defines, age
prumo_coverage
Reports the folders of the code that no context file mentions: every top-level folder, or every package of a workspace, that no context file cites a path in and that holds no context file of its own, with the files git tracks in it, its commits in the last ninety days and its last commit, the most active first. It is what the agent is never told about, never a finding: a folder may be left out of
prumo_drift
Reports which sections of the context files describe code that changed after the section was last written: for every section that cites a file or a folder the repository has, when the section last changed according to git blame, how many of the files it cites changed since, and how many commits touched them. Sections come back ordered, the most moved first. It is a reading order for a review, neve
prumo_fix
Rewrites case mismatches in place to the spelling the git index holds, and a missing path, a markdown link or an @ import to the name git recorded when it renamed the file, then reports what remains. Nothing else is touched: a link suggested from a name, a missing path with no history and a deleted file are never edited.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings

Code scan28 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 4 days ago15/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Prumo compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 89/100; higher than 80% of 1,119 Developer tools servers
Tools: 5; the typical Developer tools server has 7
Tools that change things: 0%; typical: 5%. Fewer write tools means less an agent can break
GitHub stars: 5; more than 78% of 855 Developer tools servers
Downloads a week: 405; more than 82% of 436 Developer tools servers with a package

What its tools let an agent do: 5 read

Release history: 2 versions in the registry since 2026-09-07, latest 2026-10-11, typically one every 34 days.

Install Prumo in Claude Code, Cursor or VS Code

Runs npx -y @tomd4vs/prumo on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add prumo -- npx -y @tomd4vs/prumo

Add to Cursor

What the publisher says

From the Prumo repository's README, as published. We do not edit it. Read it on GitHub

Checks the context files your coding agent reads against the code beside them.

The problem

Three months ago someone wrote this in CLAUDE.md:

The sidebar logo lives in `layouts/AppLayout.vue`.

The folder has since been renamed to Layouts, with a capital L. Windows and macOS still open that path, so nothing ever complained. Linux and CI don't, and every agent that reads the file gets sent somewhere that doesn't exist.

That line survived six hand-run audits of the same files. prumo found it in four seconds.

Quick start

If you already have Node.js 18+ and git, you are ready. Nothing to install, nothing to configure, no account to create. From a terminal inside any git repository:

npx @tomd4vs/prumo

prumo locates your context files on its own: CLAUDE.md, AGENTS.md, .cursor/rules, .github/copilot-instructions.md, installed skills in .claude/skills/ and the rest. Every file and folder it looks for is in the reference.

For frequent use, install it once:

npm install -g @tomd4vs/prumo             # available everywhere on your machine
npm install --save-dev @tomd4vs/prumo     # or as a dev dependency of one project

Either way the command is prumo, with zero dependencies. Errors at this step, such as an old Node or a folder that isn't a git repository, are in Troubleshooting.

Reading the result

A clean run:

prumo — 1 context file, 401 files tracked by git

nothing to review.

A run with findings, annotated:

prumo — 3 context files, 412 files tracked by git             ← what it read
        1 historical entry exempt from path checks            ← what it skipped on purpose

CASE MISMATCH  (1)   wrong letter case: works on Windows and macOS, fails on Linux and CI
  CLAUDE.md:18                                                ← file and line
      layouts/AppLayout.vue                                   ← what the note says
      ->  resources/js/Layouts/AppLayout.vue                  ← what the repository has

BROKEN LINK  (2)   points at a page or heading that is not there; 1 with a likely destination
  CLAUDE.md:21  [[deploy-checklist]]   ->  deploy_checklist   ← the file it probably meant
  CLAUDE.md:30  [[old-architecture]]                          ← no candidate: renamed or deleted

MISSING PATH  (1)   the note cites it, but git tracks no such file or folder
  docs/setup.md:44  config/database.php                       ← file, line, dead path
      Copy the template into `config/database.php`…           ← the sentence, so you can judge

4 to review, --fix corrects 1                                 ← 1 + 2 + 1

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Prumo: common questions

Is Prumo MCP server safe?: Yes, by our scan: it is graded A (89/100). Read the Prumo safety report
How do I install Prumo?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Prumo need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Prumo maintained?: The last commit was 24 days ago (2026-10-11). The latest release is v0.9.7.
What can I use instead of Prumo?: Servers from other publishers that do the same job: argot MCP server, Gnt MCP server and Repowise MCP server. Compare all Prumo alternatives.
How does Prumo compare with other Developer tools MCP servers?: safety score 89/100 (higher than 80% of 1,119 Developer tools servers); tools 5 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Prumo

Same job from other publishers: the closest match first, then the best rated.

All Prumo alternatives →

argot
Read-only context and complete checks against patterns learned from git history. Local; no LLM.
not reviewed
Established
B
Gnt
Git-native policy layer for AI agents: check_action verdicts against rules approved via PR.
not reviewed
Growing
A
Repowise
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
not reviewed
Established
B
uploads.sh
Host files from coding agents; stage on a branch and attach to GitHub PRs.
not reviewed
Established
A
Foremerge
Coordinate parallel coding agents, above Git
not reviewed
Growing
A