io.github.cognitivemyriad/verified-repo-memory
Verified Repo Memory
Is the Verified Repo Memory MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Stale-proof repository memory with citations + just-in-time verification + TTL (repo-scoped).
not found down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @cognitivemyriad/vrm-local@0.1.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/cognitivemyriad/mcp-verified-repo-memory
- Registry
- active, updated 2026-02-21 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.codevanmoose/truncus-mcp-server · alive
- io.github.codevanmoose/vanmoose-mcp-server · needs env
- io.github.codyz123/schelling-protocol · alive
- LayerMap io.github.coffeecoproject/layermap · alive
- CohostSTR (MCP server for Guesty) io.github.cohoststr/cohoststr-mcp · alive
- io.github.colapsis/transfa · alive
- io.github.colincooperio/garmin-mcp · alive
- message-cp io.github.colinhallett/message-cp · alive
Servers that mention verified.
- Getlead ad.getle/leads · alive
- 1325.AI ai.1325/mcp · needs auth
- AFG: agents hire agents (test money) ai.afg/afg · alive
- Agentic Terminal Directory ai.agenticterminal/directory · alive
- ai.atlasverified/atlas-mcp · needs auth
- BotInfo — Advanced Robot Market Data ai.botinfo/robot-market-data · alive
- Caulo ai.caulo/caulo · needs auth
- Infrabase ai.infrabase/directory · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.