Recordant
Patent-pending diagnostic + decisions-ledger engine for any host software system — operator briefs and a severity-gated MCP console.
README
Recordant
<!-- mcp-name: io.github.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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。