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/timothywarner-org/context-engineering/claudedesktop-warnerco-schematicagit clone --depth 1 https://github.com/timothywarner-org/context-engineeringWrote 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/timothywarner-org/context-engineering/claudedesktop-warnerco-schematica)<a href="https://agentmods.dev/mcp/timothywarner-org/context-engineering/claudedesktop-warnerco-schematica"><img src="https://agentmods.dev/badge/mcp/timothywarner-org/context-engineering/claudedesktop-warnerco-schematica.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claudedesktop-warnerco-schematica 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 5d 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
{
"claudedesktop-warnerco-schematica": {
"command": "uv",
"args": [
"run",
"warnerco-mcp"
],
"cwd": "C:/github/context-engineering/src/warnerco/backend",
"env": {
"MEMORY_BACKEND": "chroma"
}
}
}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.
- 5d ago First seen · 13 lines scan A 94fc3c502f01
claudedesktop-warnerco-schematica is an MCP server published in the GitHub repository timothywarner-org/context-engineering (27 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-30.
Other mcp servers, from other repositories
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
myco-brain
Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres. Runs locally from the @mycobrain/mcp-server npm package.
genesys-memory
The intelligence layer for AI memory — scoring, causal inference, lifecycle management, and active forgetting. Runs locally from the genesys-memory Python package. Needs 3 environment variables to run.
honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens. Remote server at mcp.honcho.dev.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.