PentaCore
An MCP server written in Rust that stores AI agent state using encrypted SQLite, supports note trees and entity queries, and is intended to replace Markdown files for managing long-term task context.
Timeline (last 90 days)
PentaCore is an MCP server written in Rust that uses an encrypted SQLite file as state storage for AI agents, in a single binary.
PentaCore bundles the all-MiniLM-L6-v2 embedding model and supports exact word search (FTS5) and semantic search.
PentaCore's MCP server uses only stdio transport by default and can be called only by the process that launched it.
PentaCore's HTTP mode listens only on the loopback address and refuses to start without a token of at least 32 characters.
PentaCore's HTTP mode requires an exact Host header to block DNS rebinding and rejects any request carrying an Origin header.
PentaCore uses SQLCipher for encryption at rest and enables secure_delete and WAL cleanup after purging.
PentaCore's SQLCipher key is compiled into the binary, so it protects the file only from someone who has just the file, not from someone who has the binary or source code.
PentaCore provides a resume call that in a single call at the start of a new session returns the last checkpoint, work in progress, blockers, failed attempts, decisions made, and all unfinished checklist items, with the response fitted to a configurable token budget.
PentaCore provides a query_entities call for field-filtered queries (such as "what has not yet passed check X"), with results independent of how the agent phrased its notes.
PentaCore provides a summarize call that records the work and results after a step is completed, and task_summary returns a summary of the entire task in tree order regardless of how many notes lie beneath it.
4 more timeline events
All Facts (14)
PentaCore is an MCP server written in Rust that uses an encrypted SQLite file as state storage for AI agents, in a single binary.
50%UnverifiedPentaCore bundles the all-MiniLM-L6-v2 embedding model and supports exact word search (FTS5) and semantic search.
50%UnverifiedPentaCore's MCP server uses only stdio transport by default and can be called only by the process that launched it.
50%UnverifiedPentaCore's HTTP mode listens only on the loopback address and refuses to start without a token of at least 32 characters.
50%UnverifiedPentaCore's HTTP mode requires an exact Host header to block DNS rebinding and rejects any request carrying an Origin header.
50%UnverifiedPentaCore uses SQLCipher for encryption at rest and enables secure_delete and WAL cleanup after purging.
50%UnverifiedPentaCore's SQLCipher key is compiled into the binary, so it protects the file only from someone who has just the file, not from someone who has the binary or source code.
50%UnverifiedPentaCore provides a resume call that in a single call at the start of a new session returns the last checkpoint, work in progress, blockers, failed attempts, decisions made, and all unfinished checklist items, with the response fitted to a configurable token budget.
50%UnverifiedPentaCore provides a query_entities call for field-filtered queries (such as "what has not yet passed check X"), with results independent of how the agent phrased its notes.
50%UnverifiedPentaCore provides a summarize call that records the work and results after a step is completed, and task_summary returns a summary of the entire task in tree order regardless of how many notes lie beneath it.
50%UnverifiedPentaCore does not plan tasks or decide the next step; it only stores what it is given and returns what is requested.
50%UnverifiedPentaCore suits scenarios where an agent pursues many similar goals across multiple sessions, undergoes context compression, and needs precise answers to "what was done, what was found, and what remains."
50%UnverifiedPentaCore is not suited to dependency-based software development task tracking (Beads or Claude Code's built-in tasks should be used), short tasks within a single session, or long-term memory about the user or the user's preferences.
50%UnverifiedPentaCore's Linux, macOS, and Windows binaries are available in GitHub Releases, including SHA256SUMS, an SBOM, and build provenance attestation.
50%