MCP.Market

supragnosis MCP server

by Ashon·io.github.Ashon/supragnosis·v0.11.0

Memory for AI agents that remembers who said it.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed supragnosis yet.

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

supragnosis tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How supragnosis compares

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

Safety score
88/100
higher than 75% of 48,255 servers

Release history: 3 versions in the registry since 2026-10-24, latest 2026-10-28, typically one every 4 days.

Install supragnosis in Claude Code, Cursor or VS Code

claude mcp add supragnosis -- docker run -i --rm ghcr.io/ashon/supragnosis:0.11.0
Add to Cursor

What the publisher says

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

supragnosis

Memory for AI agents that remembers who said it.

Shared project memory for coding agents, with receipts. supragnosis is a local MCP server for Claude Code, Codex, Cursor and other MCP clients. Your agents record what they learn as they work, and every claim keeps who asserted it, on whose behalf, on what basis, and how far this node trusts it. Claims that contradict each other stay side by side for you to settle, instead of the later one overwriting the earlier.

It is built for a small team that wants one project's memory on each of its machines and shared with teammates, without a vendor cloud: one binary, an embedded store, and no account. A workspace leaves your machine only when you list it.

supragnosis = supra (above) + gnosis (knowing) - knowledge about knowledge.

The problem it solves

Most agent memory answers what was remembered. It does not answer who said so.

That is fine for a single assistant remembering one user's preferences. It stops being fine the moment two agents, two machines, or two people write into the same memory:

so nothing can trace what else that summary contaminated.

  • Two agents assert opposite facts. Last write wins, and the disagreement is gone.
  • An agent summarizes a poisoned document into memory. Nothing records where it came from,

no boundary to draw, because the store has no concept of whose knowledge this is.

  • You want to share project knowledge with a teammate but not your private notes. There is
  • A credential ends up in the log. There is no way to find it and no way to get it out.

supragnosis treats an assertion and a fact as different things. What is stored is never "X is true" but "host H, at time T, on the basis of S, asserted X". The current belief is computed from those assertions by a policy you can replace, so changing your mind about how to resolve conflicts means recomputing, not rewriting.

What that buys you

Quick start

brew tap ashon/tap
brew install supragnosis-server
supragnosis service install         # MCP on :7373 + local viewer, now and at every login
supragnosis connect claude-code     # or claude-desktop, cursor, vscode, codex, gemini, opencode

Shortened. The full README is on GitHub.

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

supragnosis: common questions

Is supragnosis MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the supragnosis safety report
How do I install supragnosis?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does supragnosis need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is supragnosis maintained?
The last commit was 11 days ago (2026-10-24). The latest release is v0.11.0.