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/shafthq/shaft_engine/chaosengine-memorygit clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINEWrote 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/shafthq/shaft_engine/chaosengine-memory)<a href="https://agentmods.dev/mcp/shafthq/shaft_engine/chaosengine-memory"><img src="https://agentmods.dev/badge/mcp/shafthq/shaft_engine/chaosengine-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
chaosengine-memory 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
{
"chaosengine-memory": {
"args": [
".chaos-engine/tool.py",
"memory-mcp"
],
"argsWindows": [
"-3",
".chaos-engine/tool.py",
"memory-mcp"
],
"command": "python3",
"commandWindows": "py",
"cwd": "."
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page. The 2 below are a sample.
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 · 16 lines scan A 56c188801184
chaosengine-memory is an MCP server published in the GitHub repository ShaftHQ/SHAFT_ENGINE (407 stars, last pushed today), 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
smartbear-mcp
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, API Hub, PactFlow. Runs locally from the @smartbear/mcp npm package. Needs 10 environment variables to run.
sauce-api-mcp
MCP servers for Sauce Labs APIs (Core & RDC OpenAPI). Runs locally from the sauce-api-mcp Python package. Needs 2 environment variables to run.
mcp-server
BrowserStack's Official MCP Server. Runs locally from the @browserstack/mcp-server npm package. Needs 2 environment variables to run.
zendesk-local
MCP server "zendesk-local" as configured in fruggr/zendesk-mcp-server. Launched with pnpm exec tsx src/index.ts --mode all --dev. Needs 1 environment variable to run.
kilotest
Ensemble testing of web pages for accessibility, usability, and standards conformity. Remote server at kilotest.com.
argus
Argus — the QA layer for AI-assisted development. Claude-native (MCP) Chrome audits across 67 categories — errors, visual regressions, a11y, security, performance — no test files, secrets redacted by default (Aegis). Runs locally from the argusqa-os npm package.