Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/riemannulus/knowledge-baseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/riemannulus/knowledge-base/kb-workflow-kb)<a href="https://agentmods.dev/mcp/riemannulus/knowledge-base/kb-workflow-kb"><img src="https://agentmods.dev/badge/mcp/riemannulus/knowledge-base/kb-workflow-kb/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/riemannulus/knowledge-base/kb-workflow-kb"><img src="https://agentmods.dev/badge/mcp/riemannulus/knowledge-base/kb-workflow-kb.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kb scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"kb": {
"type": "http",
"url": "${user_config.kb_mcp_url}",
"headers": {
"Authorization": "Bearer ${user_config.kb_auth_token}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 63a94f6ab005
kb is an MCP server published in the GitHub repository riemannulus/knowledge-base (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
fortemi
MCP server "fortemi" as configured in Fortemi/fortemi. Runs ./mcp-server/index.js with node. Needs 2 environment variables to run.
re-call
Trustworthy retrieval for an AI agent's own memory — verdict, confidence and provenance per hit, or an explicit abstention. Runs locally from the recall-rag Python package. Needs 3 environment variables to run.
recall
MCP server "recall" as configured in GiulioDER/RE-call. Launched with recall-codex-mcp.
kb
MCP server "kb", hosted remotely at 127.0.0.1, as configured in fish827-08/rag-kb.
corpus-rag
Single-user RAG framework for personal archives. Local-first, MCP-native. Runs locally from the corpus-rag Python package.
mnemon-mcp
Persistent layered memory MCP server for AI agents — SQLite + FTS5 backend. Runs locally from the mnemon-mcp npm package. Needs 3 environment variables to run.