mcp server
Nahuali
Trust-aware agent memory with evidence-backed recall, self-inspection, and audit history.
Description as published by the maintainer. Source
- version 0.8.0-beta.10
- active
- memory and context
active — Most recent push to the repository was 2026-07-30. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 3 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-30 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.8.0-beta.10 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-30 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-30 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.chernistry/bernstein
— last commit 2026-08-06, shares provenance, tamper-evident
Declarative agent orchestration for engineering teams
-
Palimpsest — censorship and model-eval observatory
— last commit 2026-08-06, shares tamper-evident
Live internet-censorship signals and tamper-evident, pre-registered, hash-chained AI model evals.
-
io.github.cruxible-ai/cruxible-core
— last commit 2026-08-05, shares local-first, provenance
Deterministic decision engine with receipts. Define rules in YAML, query a graph, get proof.
-
dev.tatastu/proof
— last commit 2026-07-19, shares provenance
Stamp content with permanent, verifiable provenance. Hash locally, verify free forever.
-
io.github.Abracadabrastartup/deusproof-mcp
— last commit 2026-08-05, shares provenance
Prove your AI work existed first: timestamped, Bitcoin-anchored. Free, no account.
-
AnchorRegistry
— last commit 2026-06-13, shares provenance
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
-
io.github.beeswaxpat/chronoverify
— last commit 2026-08-03, shares provenance
Verify a photo's capture time and provenance: C2PA validation, EXIF/XMP, and pixel forensics.
-
io.github.blackwell-systems/knowing
— last commit 2026-07-08, shares provenance
Content-addressed code graph with 22 MCP tools for AI agents.
-
ActionProof
— last commit 2026-07-01, shares provenance
Tamper-proof audit trail for AI agents. Signed receipts, offline-verifiable, zero backend.
-
io.github.Christebob/meta-stamp-pockets
— last commit 2026-07-29, shares provenance
Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP.
These share tags the maintainers applied themselves, such as provenance, tamper-evident, local-first. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agent-memory, ai-agents, local-first, mcp, mcp-server, memory-governance, provenance, rust, self-inspection, surrealdb, tamper-evident, trust-layer.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab