RE-callBLOCK
Memory that abstains instead of guessing: agent memory on your own Postgres with a verdict, confidence and provenance on every hit, and a calibrated refusal when nothing clears the threshold.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Memory that abstains instead of guessing. RE-call is agent memory on your own PostgreSQL with pgvector. Each result carries a verdict, confidence, and provenance, while unsupported questions are refused instead of answered by the nearest match.
What it is · For agents · How it works · Try the demo · Install and integrate
What is RE-call
RE-call is agent memory on your own PostgreSQL database. It indexes source documents with pgvector and keeps validity, lineage, confidence, and provenance attached to every result.
Vector search returns nearby text. RE-call also checks whether that text is current, supported, and trustworthy enough for the query. A superseded claim is marked superseded; a result that does not clear the calibrated trust gate becomes ABSTAIN with a reason. Declared supersession makes the current memory win over sta
b5d64aa93e61OBSERVED · 2026-10-10Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add recall-rag --env RECALL_SERVING_DSN=${RECALL_SERVING_DSN} -- uvx recall-rag==0.14.0Trust audit
BLOCKgrade F · trust 41/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (4 observation(s))
- Network
- declared (4 observation(s))
- Shell
- declared (4 observation(s))
- Dependencies
- pinned
- Secrets in source
- found
Findings (25)
# RECALL_SERVING_DSN=postgresql://recall_server:...@localhost:5432/recall
# RECALL_MIGRATION_DSN=postgresql://recall_migrator:...@localhost:5432/recall
# RECALL_DSN=postgresql://recall:recall@localhost:5432/recall
value = getattr(importlib.import_module(module_name), name)
return importlib.import_module(f"{__name__}.{name}")importlib.import_module(requirement.target)
module = importlib.import_module(module_name)
tokens = random.Random(seed).sample(tokens, token_budget)
print(json.dumps(run(args.cache_dir, args.out, args.run_id, token, openrouter_key, workers=args.workers), indent=2))
"ledger", "router", "beacon", "harbor", "spindle", "lantern", "conduit", "anvil",
# # http://127.0.0.1:11434/v1 for ollama,
], secrets = concat(var.provider_secret_arn == null ? [] : [{ name = var.provider_env_name, valueFrom = var.provider_secret_arn }], var.serving_dsn_secret_arn == null ? [] : [{ name = "RECALL_SERVING_service: http://127.0.0.1:18004
lines = text.replace("\r\n", "\n").lstrip("").split("\n")RECALL_TEST_DSN: postgresql://recall:recall@localhost:5432/recall
RECALL_TEST_DSN: postgresql://recall:recall@localhost:5432/recall
secret = "do-not-serialize-this-secret-value"
secret = "sk-XX-supersecretvalue"
secret = "/corpus/private-memo.md"
secret = "/corpus/private-memo.md"
secret = "SENTINEL_CORPUS_TEXT_bd41f2"
.mcp.json.example
.squawk.toml
.terraform.lock.hcl
.nojekyll
Gates applied: no_behavioural_pass.
b5d64aa93e61full audit observations/trust-audit/mcp-server/giulioder__re-call.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | b5d64aa93e61 | BLOCK | F | 41 | first audit |
Questions
What is the RE-call MCP server?
Memory that abstains instead of guessing: agent memory on your own Postgres with a verdict, confidence and provenance on every hit, and a calibrated refusal when nothing clears the threshold.
Is RE-call safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (41/100) and found 3 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does RE-call need?
It reads DEEPSEEK_API_KEY, OPENAI_API_KEY, OPENROUTER_API_KEY, RECALL_AML_API_KEY, RECALL_AML_AUTHORIZED_USER_ID, RECALL_AML_COMPILER_MAX_TOKENS, RECALL_AML_TOKEN, RECALL_AUTH_UNDOCUMENTED_KNOB, RECALL_RESTORE_KMS_KEY_ID, RECALL_SERVING_DSN and VOYAGE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does RE-call run?
It speaks sse, stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as recall-rag.
How current is this page?
The grade is for one exact copy of the source (b5d64aa93e61), read on 2026-10-10. The repository is watched and re-audited when it changes.