pypi recordantstdioupdated 2mo ago
Recordant is a patent-pending diagnostic + decisions-ledger engine for any host software system. Point it at a target's repo, changelog, and logs, and it runs a periodic scan that produces an operator brief: what changed, what looks broken, what was fixed, and a prioritized diagnosis list — plus a chat-native MCP console over the same data.
What can you do with recordant?
Recordant
Recordant is a patent-pending diagnostic + decisions-ledger engine for any host software system. Point it at a target's repo, changelog, and logs, and it runs a periodic scan that produces an operator brief: what changed, what looks broken, what was fixed, and a prioritized diagnosis list — plus a chat-native MCP console over the same data.
Bring your own LLM (Anthropic, OpenAI, or Gemini — your key, your usage, your bill). Recordant makes no provider assumption.
15-minute install and first brief
-
Install the package and your LLM provider's SDK (only the one you use):
pip install "recordant[anthropic]" # or [openai], [gemini], or [all] -
Copy
recordant.example.tomltorecordant.tomland set:repo_root— the target repo to diagnosechangelog_path— usuallyCHANGELOG.md(falls back togit logif absent)log_globs— which log files to health-scan[llm]— your provider, model, andapi_key_env(the name of the environment variable holding your key — never the key itself)
-
Export your key and run one cycle:
export RECORDANT_LLM_KEY=sk-... recordant --config recordant.tomlThe brief path prints to stdout. The brief, snapshot, and (optional) decisions ledger are written under your configured
output_dir. -
Schedule it (cron / systemd timer / your own scheduler) at the
schedule_secondscadence in your config.
That's the whole loop. See ENGINE.md for the adapter architecture, config
reference, and known limitations.
MCP console
Recordant also runs as an MCP server exposing 7 tools over stdio, for use from a chat-native MCP client:
| Tool | Purpose |
|---|---|
recordant_brief |
Latest delta brief since the prior cycle |
recordant_status |
Current status snapshot (health, cadence, active book) |
recordant_digest |
Open items, Accepted-Risk Register, fixes shipped, deadlines |
recordant_open_items |
Every open diagnosis with age, recurrence, evidence |
recordant_acknowledge |
Acknowledge a diagnosis (P0 items cannot be acknowledged) |
recordant_accept_risk |
Pin a diagnosis in the Accepted-Risk Register |
recordant_resolve |
Assert a diagnosis is resolved (audited against the changelog) |
Token-auth is on by default — there is no anonymous mode. The server
requires a valid RECORDANT_LICENSE_KEY and verifies it against the license
service at startup before registering a single tool; it will not run
unlicensed, even briefly. A short offline-grace window covers a transient
network failure to the license service, but an explicitly invalid or expired
key is refused immediately.
export RECORDANT_LICENSE_KEY=rk-...
recordant-mcp --config recordant.toml
Add it to your MCP client's config (Claude Desktop, Claude Code, etc.):
{
"mcpServers": {
"recordant": {
"command": "recordant-mcp",
"args": ["--config", "/absolute/path/to/recordant.toml"],
"env": { "RECORDANT_LICENSE_KEY": "rk-..." }
}
}
}
Licensing and pricing
Recordant is licensed software, not open source (see LICENSE). Get a key
and see current pricing at
https://mentorsentinel.ai/markets-ai-governance.html.
Docker
Recordant ships as a compiled image -- there is no engine source to build
from, so docker build is not part of a customer workflow. Pull the
licensed image (published per BUILD-RELEASE.md) and run it:
docker pull recordant/recordant:<version>
docker run -v $PWD/recordant.toml:/app/recordant.toml:ro \
-v $PWD/target-repo:/app/target-repo:ro \
-e RECORDANT_LLM_KEY \
recordant/recordant:<version> --config recordant.toml
The image is signed (cosign) and ships with an SBOM (syft) so you can audit
what it does -- dependencies, egress -- without needing readable engine
source; see BUILD-RELEASE.md for verification commands.
See docker-compose.example.yml for a compose-based setup, including the
MCP console service.
Support
Found a bug or have a feature request? Open an issue — see
.github/ISSUE_TEMPLATE/. For licensing or account questions, use the
pricing page above.
Patents
Recordant's inference loop and decisions-ledger lifecycle are patent-pending (U.S. application numbers available on request). "Patent-pending" reflects filed, unexamined provisional applications — no patent has issued.
Install
Add recordant to your client. Pick the one you use.
claude mcp add recordant -- uvx recordantcodex mcp add recordant -- uvx recordantamp mcp add recordant -- uvx recordant{
"mcpServers": {
"recordant": {
"command": "uvx",
"args": [
"recordant"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"recordant": {
"command": "uvx",
"args": [
"recordant"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"recordant","command":"uvx","args":["recordant"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"recordant": {
"command": "uvx",
"args": [
"recordant"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"recordant": {
"command": "uvx",
"args": [
"recordant"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"recordant": {
"command": "uvx",
"args": [
"recordant"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"recordant": {
"type": "local",
"command": "uvx",
"args": [
"recordant"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"recordant": {
"command": {
"path": "uvx",
"args": [
"recordant"
]
}
}
}
}Add to your Zed `settings.json`.
uvx recordantRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance16/25
- Trust9/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 57 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.2.2Latest | Jul 5, 2026 |
| 0.2.1 | Jul 5, 2026 |