Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
RepoCanon is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
35
downloads a day
local
runs on your machine
1k
downloads in 30d
What it does
Verified AGENTS.md and project memory for AI coding agents: context packs and freshness checks
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user repocanon-mcp '--' npx -y repocanon mcp
# 2 — ask your agent for something these tools do
# rc_context, rc_module, rc_find_owner and 7 more
RepoCanon costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts RepoCanon as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user repocanon-mcp '--' npx -y repocanon mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Budgeted context pack for a task: PROJECT + relevant module docs + DOMAIN/CONVENTIONS/STATE. Call this FIRST instead of scanning the repo. Docs that may not match the code carry a stale/broken/unverified label — trust the code there.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | task description / keywords |
| files | array | no | repo-relative files you expect to touch |
| max_tokens | number | no | — |
Full knowledge doc for one module (purpose, invariants, flow, code map).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Which module owns a repo-relative file path, and its doc.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | — |
Freshness of every .ai doc (fresh/stale/broken/unverified) vs git.
No parameter schema on file.
Evidence-loaded brief for writing/filling the .ai/ knowledge docs (stack playbook, files to inspect, per-doc instructions). Call this, then write the .ai/*.md files yourself with your own file tools — do not ask the human to paste anything.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| compact | boolean | no | short form instead of the full brief |
What changed in the repo since each doc was last verified, and which docs likely need updating. Call this before rc_prepare_fill when the task is "update the docs after code changes", then write the affected .ai/*.md files yourself.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | git ref to diff from (defaults to each doc's verified_at commit) |
Record an architecture decision in its own file, .ai/decisions/<date>-<slug>.md (id D-<date>-<slug>), so parallel branches never conflict; the AGENTS.md rules digest is updated. Use when a task settled a choice future work must respect. One line per field; refused if it contains secrets, pasted…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | short name of the decision (max 80 chars) |
| decision | string | yes | what was decided (one line) |
| why | string | yes | the reason (one line) |
| revisit | string | no | when to reconsider (optional) |
| supersedes | string | no | id of a decision this replaces, e.g. D-2026-10-28-bill-in-cents or a legacy D-003 (optional) |
Record where work stands in .ai/STATE.md so the next session can pick up: current focus, in-progress items, known issues, and one line for a significant change. Only the sections you pass change. This does NOT mark any doc verified.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| focus | string | no | what the project is working on now (one line) |
| in_progress | array | no | replaces the In progress list (max 8) |
| known_issues | array | no | replaces the Known issues list (max 8) |
| change | string | no | one significant change to log with today's date |
Mark docs verified against the current commit (verified_by: agent). Only after you have read the code and updated each doc so it matches; commit the code first — docs with uncommitted code changes are refused. Name every doc (module slug or core doc name such as STATE).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| docs | array | yes | — |
Am I done? Checks the knowledge layer: doctor errors and warnings, stale or broken docs, the Freshness Score. Ends with PASS or FAIL. Call before finishing a task that changed code or docs; pass docs to check only those.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| docs | array | no | module slugs or core doc names (optional) |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RepoCanon or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 0.7.1 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digestda192532a34a115eb066383bb796f921970cefcf21c873944cc7bad359222ccf
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can start a fixed program (a process-spawning capability, not arbitrary code execution)
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestda192532a34a115e
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.7.1. Pin a release below and the command asks for exactly that one.
0.7.1
2 Nov 2026
latestNo release note was published with this version.
0.7.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish RepoCanon can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.