veracium
io.github.veracium-ai/veracium
About veracium
veracium is an MCP server published by the GitHub account veracium-ai. Provenance-aware memory for AI agents: quarantine, abstention gate, supersession-with-history.
It runs on your own machine: your AI client starts it from the PyPI package veracium at version 0.16.0.
It asks for one secret: ANTHROPIC_API_KEY. Give it a key with the least access that still works.
Version 0.16.0 was published on 26 August 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
ANTHROPIC_API_KEY | Yes | Yes | API key for the reference Anthropic provider |
VERACIUM_DB_PATH | No | No | Path to the SQLite memory file (default: veracium.db) |
VERACIUM_USER | No | No | Default user id when a tool call omits user_id |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/veracium-ai/Veracium |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 1 secret: ANTHROPIC_API_KEY |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account veracium-ai |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | veracium 0.16.0 has no setup.py; nothing runs at install |
| Code red flags | Pass | Read 334 files in veracium 0.16.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 334 files, including comments and the README |
Popularity & health: 67 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
3 forks, 4 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.veracium-ai/veracium |
|---|---|
| Publisher | GitHub account veracium-ai |
| How the name is verified | Name verified via GitHub account veracium-ai. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | pypi veracium 0.16.0 (stdio) |
| Version | 0.16.0 |
| Published | |
| Last updated | |
| Source repository | https://github.com/veracium-ai/Veracium |
| Website | https://docs.veracium.ai |
| Category | Productivity & notes (assigned by keyword rule, not by hand) |
Related servers in Productivity & notes
- devin-memory7/7Anti-poisoning memory for agents: provenance, conflicts, quarantine…
- understanding-graph7/7Persistent understanding via workflow prompts, typed updates,…
- Handoff7/7Cross-session memory for Claude over MCP — prioritised briefs,…
- Tugra7/7Provenance-aware memory format for AI agents: every claim carries…
- Nahuali4/4Trust-aware agent memory with evidence-backed recall,…
inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail5/7Self-correcting agent memory: recall, supersede, revert, forget,…