Veracium runs on your own machine — the client starts it, so there is no endpoint to ping. 1 259 installs a week from pypi. Last commit 2 Nov 2026.
Provenance-aware memory for AI agents: quarantine, abstention gate, supersession-with-history.
We read the source, 43 min ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
n = len(subprocess.run(["tar", "tzf", str(f)], capture_output=True,
exec(compile(ast.Module(body=body, type_ignores=[]), str(ROOT / STEPTABLE), "exec"), ns)
src = open(os.path.join(T, "src", f), encoding="utf-8").read()
if (a[0] == sqlite3.SQLITE_SELECT and tuple(rec.acts[i + 1:i + 1 + n]) == DECLARE_VTAB_SEQ
env = dict(os.environ)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add veracium -e 'ANTHROPIC_API_KEY=<ANTHROPIC_API_KEY>' -- uvx veracium
{
"mcpServers": {
"veracium": {
"command": "uvx",
"args": [
"veracium"
],
"env": {
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>"
}
}
}
}
[mcp_servers.veracium]
command = "uvx"
args = ["veracium"]
env = { ANTHROPIC_API_KEY = "<ANTHROPIC_API_KEY>" }
{
"mcpServers": {
"veracium": {
"command": "uvx",
"args": [
"veracium"
],
"env": {
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>"
}
}
}
}
{
"servers": {
"veracium": {
"type": "stdio",
"command": "uvx",
"args": [
"veracium"
],
"env": {
"ANTHROPIC_API_KEY": "<ANTHROPIC_API_KEY>"
}
}
}
}
Put your own value in place of
<ANTHROPIC_API_KEY> (API key for the reference Anthropic provider).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
VERACIUM_DB_PATH (Path to the SQLite memory file (default: veracium.db)), VERACIUM_USER (Default user id when a tool call omits user_id).
Anti-poisoning memory for agents: provenance, conflicts, quarantine gate.
Self-hosted MCP memory for AI agents: persistent context with evidence-backed claims.
Long-term memory for AI agents: local-first PKM with provenance and hybrid search.
Yahoo Finance for AI agents: quotes, price history, options with Greeks, financials, news, movers.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
Persistent memory for AI agents. Search, store, and recall across sessions.
Auditable memory for coding agents: evidence chains, supersession history, keyless embedded SQLite
Persistent memory for AI agents - save once, recall in every session, project and tool.
Answers built from our own checks of this server.