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/ldclabs/KIPWrote 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/ldclabs/kip/kip-mcp-server-kip)<a href="https://agentmods.dev/mcp/ldclabs/kip/kip-mcp-server-kip"><img src="https://agentmods.dev/badge/mcp/ldclabs/kip/kip-mcp-server-kip.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
KIP 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 8d 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
{
"KIP": {
"command": "npx",
"args": [
"-y",
"@ldclabs/kip-mcp-server"
],
"env": {
"KIP_BACKEND_URL": "",
"KIP_API_KEY": ""
}
}
}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.
- 8d ago First seen · 13 lines scan A 49d3dd999e52
KIP is an MCP server published in the GitHub repository ldclabs/KIP (81 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
rawthink-mcp
Persistent memory MCP server for AI development workflows — hybrid search, knowledge graph, session lifecycle. Runs locally from the rawthink-mcp Python package. Needs 9 environment variables to run.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
chatcrystal
Local-first AI PKM memory for coding conversations. Runs locally from the chatcrystal npm package. Needs 2 environment variables to run.
halomem
MCP server "halomem", hosted remotely, as configured in halofyai/halofy.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
synapse-layer
Persistent memory infrastructure for AI agents — AES-256-GCM encrypted at rest, semantic search, MCP-native. Runs locally from the synapse-layer Python package. Needs 3 environment variables to run.