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-mempalacegit clone --depth 1 https://github.com/ShaftHQ/SHAFT_ENGINEGrade A, and why
chaosengine-mempalace 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 today.
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-mempalace": {
"args": [
".chaos-engine/tool.py",
"mempalace-mcp"
],
"argsWindows": [
"-3",
".chaos-engine/tool.py",
"mempalace-mcp"
],
"command": "python3",
"commandWindows": "py",
"cwd": ".",
"env": {
"MEMPALACE_BACKEND": "sqlite_exact",
"MEMPALACE_EMBEDDING_MODEL": "minilm"
}
}
}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.
- today Changed · -8 lines cb9e16391e5b
- yesterday First seen · 28 lines scan A 097e5bd5e505
chaosengine-mempalace 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
uindow
Real signed-browser automation for AI agents, over a local stdio MCP server. Runs locally from the @uindow/cli npm package.
crawlberg
MCP server "crawlberg" as configured in xberg-io/crawlberg. Launched with ./scripts/mcp-launch.sh mcp.
mockpost
Local multi-channel message emulator for E2E testing, with an MCP server for LLM agents. Runs locally from the mockpost Python package. Needs 1 environment variable to run.
swagger-mcp-bridge
MCP server "swagger-mcp-bridge" as configured in Neo1228/spring-boot-starter-swagger-mcp. Runs in Docker (ghcr.io/neo1228/swagger-mcp-bridge-example:0.1.0).
podium-mcp
Mobile E2E MCP (51 tools): iOS + Android, native UI + canvas/WebGL, no-vision, RN debug. Runs locally from the podium-mcp npm package.
spring-fleet
MCP server "spring-fleet" as configured in talayash/spring-fleet. Runs ${CLAUDE_PLUGIN_ROOT}/scripts/mcp_server.py with python. Needs 1 environment variable to run.