Titen
Agent memory that needs no API key, no LLM, and no embedding provider. One command on Bun and it is serving MCP over stdio against a local SQLite store. Drop-in for the MCP reference memory server. Every memory keeps its source, who may read it, and the evidence that contradicts it.
Is Titen safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Titen
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: Titen scores 53.8/100 (Grade C), ranked #833 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.8/10; 8% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Titen compares in Memory & Knowledge
- #35 MemOS 57.4 +3.6
- #36 Quivr 54.5 +0.7
- #37 Titen 53.8 this agent
- #38 inno-agent 52.9 −0.9
- #39 pgvector 52.5 −1.3
Bars show each HVTrust score; the tick marks Titen’s 53.8.
Where the 53.8 comes from
HVTrust dimensions vs the Memory & Knowledge average
53.8 / 100 · 100.0% confidenceTiten Memory & Knowledge average (44 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
52.7 / 100Supply Chain Trust
Common questions about Titen
Does Titen publish package provenance?
Does Titen have an OpenSSF Scorecard?
Is Titen actively maintained?
What license does Titen use?
Are Titen's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Titen's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Titen?
For maintainers
HVTrust scores Titen from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/titen)
<a href="https://hvtracker.net/agents/titen"><img src="https://hvtracker.net/badge/titen.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON