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.
npx agentmods add mcp/kit4some/oh-my-claudeclaw/knowledge-enginegit clone --depth 1 https://github.com/Kit4Some/Oh-my-ClaudeClawWrote 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/kit4some/oh-my-claudeclaw/knowledge-engine)<a href="https://agentmods.dev/mcp/kit4some/oh-my-claudeclaw/knowledge-engine"><img src="https://agentmods.dev/badge/mcp/kit4some/oh-my-claudeclaw/knowledge-engine.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
knowledge-engine 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 3d 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
{
"knowledge-engine": {
"type": "stdio",
"command": "node",
"args": [
"./mcp-servers/knowledge-engine/src/index.js"
],
"env": {
"MEMORY_ROOT": "./memory-store"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 12 lines scan A e14b06d4f706
knowledge-engine is an MCP server published in the GitHub repository Kit4Some/Oh-my-ClaudeClaw (4 stars, last pushed 5mo 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
tokenmizer
MCP server "tokenmizer" as configured in Shweta-Mishra-ai/tokenmizer. Runs tokenmizer.mcp.server with python3. Needs 2 environment variables to run.
furl
MCP server "furl" as configured in omar-y-abdi/furl-ctx. Launched with sh -c PATH="$PATH:$HOME/.local/bin:$HOME/.cargo/bin:/opt/homebrew/bin:/usr/local. Needs 3 environment variables to run.
localkeep
Local memory banks you keep — a localhost Hub UI + MCP connector for Claude. You curate titled, dated memory banks on your machine; Claude recalls them via MCP. Runs locally from the localkeep Python package. Needs 2 environment variables to run.
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
dt
DomainTome — the living knowledge graph for your software project. A programmatic MCP-backed graph of business logic, flows, events and rules. Runs locally from the domaintome Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.