Cognos Session Memory MCP server
CognOS trust scoring (C=p·(1-Ue-Ua)) and session trace storage as MCP tools.
1 stars23 downloads/wk
Reviews
Write oneNobody has reviewed Cognos Session Memory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cognos Session Memory tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
count_tracesReturn the total number of traces stored in the session database.
get_recent_tracesRetrieve the N most recent session traces from the SQLite store.
get_traceRetrieve a single session trace by its trace ID.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan10 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancerepository archived0/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highRepository is archived
maint.archived
How Cognos Session Memory compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 66/100
- higher than 23% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 28,688 servers
- Downloads a week
- 23
- more than 9% of 12,191 servers with a package
What its tools let an agent do: 3 read
Install Cognos Session Memory in Claude Code, Cursor or VS Code
claude mcp add cognos-session-memory -- uvx cognos-session-memory-mcp
What the publisher says
From the Cognos Session Memory repository's README, as published. We do not edit it. Read it on GitHub
CognOS Session Memory
mcp-name: io.github.base76-research-lab/cognos-session-memory
Verified context injection via epistemic trust scoring for LLMs.
Solves session fragmentation by maintaining verified, high-confidence session context between conversations.
Problem
Large language models suffer from session fragmentation: each new conversation starts without verified context of previous work. This forces repeated explanations, loses decision history, and breaks long-running workflows.
Existing solutions (persistent memory systems, vector retrieval) either:
- Lack trust scores before injection → hallucinations propagate
- Don't audit which context was injected → compliance gaps
- Treat all past information equally → noise overwhelms signal
Solution
A plan-mode gateway that:
- Extracts structured context from 3-5 recent traces
- Scores context quality via CognOS epistemic formula: C = p · (1 − Ue − Ua)
- Injects as system prompt only if C > threshold
- Flags for manual review if C < threshold
- Audits every context injection with trace IDs → EU AI Act compliance
Architecture
recent_traces (n=5)
↓
extract_context() → ContextField + coverage
↓
compute_trust_score(p, ue, ua) → C, R, decision
↓
if C > threshold:
system_prompt ← inject
else:
flagged_reason ← manual reviewCore Formula
C = p · (1 − Ue − Ua)
R = 1 − C
where:
p = prediction confidence (coverage of required fields)
Ue = epistemic uncertainty (divergence between traces)
Ua = aleatoric uncertainty (mean risk in traces)Action Gate
R < 0.25 → PASS (inject without review)
0.25 ≤ R < 0.60 → REFINE (inject with caution)
R ≥ 0.60 → ESCALATE (flag for manual review)API
POST /v1/plan
Extract and score context.
Request:
{
"n": 5,
"trust_threshold": 0.75,
"mode": "auto"
}Response (if injected):
{
"status": "injected",
"trust_score": 0.82,
"confidence": 0.82,
"risk": 0.18,
"decision": "PASS",
"context": {
"active_project": "CognOS mHC research",
"last_decision": "Verify P1 hypothesis",
"open_questions": ["How does routing entropy scale?"],
"current_output": "exp_008 complete",
"recent_models": ["gpt-4", "claude-3", "mistral"]
},
"system_prompt": "## CognOS Context...",
"trace_ids": ["uuid-1", "uuid-2", ...]
}Response (if flagged):
{
"status": "flagged",
"trust_score": 0.45,
"decision": "REFINE",
"flagged_reason": "Trust score 0.45 below threshold 0.75. Manual review recommended.",
"trace_ids": [...]
}Modes
- auto (default) — inject if trust_score ≥ threshold, else flag
- force — always inject (for testing)
- dryrun** — compute score but never inject
Claude Code Integration
As a /compact replacement
# In any Claude Code session:
/saveClaude writes a structured summary, trust-scores it, and persists it to SQLite. Next session: automatically injected as SESSION_CONTEXT before your first prompt.
See docs/COMPACT_ALTERNATIVE.md for a full comparison.
As an MCP server
Add to ~/.claude/settings.json:
{
"mcpServers": {
"cognos-session-memory": {
"command": "python3",
"args": ["/path/to/cognos-session-memory/mcp_server.py"]
}
}
}Tools exposed:
Quick Start
Installation
git clone https://github.com/base76-research-lab/cognos-session-memory
cd cognos-session-memory
pip install -e .Run Gateway
python3 -m uvicorn --app-dir src main:app --port 8788Test /v1/plan (dry_run)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Cognos Session Memory: common questions
- Is Cognos Session Memory MCP server safe?
- With care: it is graded C, so read the findings first (66/100). Read the Cognos Session Memory safety report
- How do I install Cognos Session Memory?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Cognos Session Memory need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Cognos Session Memory maintained?
- The last commit was 246 days ago (2026-03-03). The latest release is v0.1.0.
- What can I use instead of Cognos Session Memory?
- Servers from other publishers that do the same job: Deja Vu MCP server.
- How does Cognos Session Memory compare with other MCP servers?
- safety score 66/100 (higher than 23% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Cognos Session Memory
Same job from other publishers: the closest match first, then the best rated.
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA