RepoMemory MCP server

• Registry namedev.repomemory/repomemoryverified in the MCP registry

The registry name sits under repomemory.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools5
• Server calls itselfrepomemory
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 231 ms.

• Its tools do every use case we checked: Record why a change was reverted so agents avoid it; Check past decisions and guardrails before changing code; Claim tasks so parallel agent sessions do not overlap.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer225 ms
• Space in an agent's context≈ 2,281 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• record_entry

  Write down something the next agent or teammate on this project must know: a decision and why it was made, a lesson from something that broke or was reverted, a guardrail (a rule not to break), a note, or a task to be done. Record a…

• recall

  Before planning a change, removing code that looks unnecessary, or repeating an approach, search the project's ledger for what was already decided, tried or forbidden. Put the area or change in `query`: any of its words match, best…

• brief

  Call this first, at the start of a session, before planning any change. It returns every active guardrail (rules not to break, each with its title and the start of its reasoning, rather than left to a word match), the open and claimed…

• claim_task

  Take a task before starting it, so another agent or teammate doesn't work on the same one. Give the task's `id` (TASK-n), or leave it out to take the oldest open task. `agent` names who is working on it ("claude-code on dimaino's…

• retire_entry

  Retire a decision, lesson, guardrail or note that is no longer true, so recall stops returning it, or mark a task done. Give its `id` and, for anything but a finished task, a short `reason`. To replace an entry with a new one, use…