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/equinoxaifinance-rgb/living-stack-mcpWrote 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/equinoxaifinance-rgb/living-stack-mcp/living-stack)<a href="https://agentmods.dev/mcp/equinoxaifinance-rgb/living-stack-mcp/living-stack"><img src="https://agentmods.dev/badge/mcp/equinoxaifinance-rgb/living-stack-mcp/living-stack/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/equinoxaifinance-rgb/living-stack-mcp/living-stack"><img src="https://agentmods.dev/badge/mcp/equinoxaifinance-rgb/living-stack-mcp/living-stack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
living-stack 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
{
"living-stack": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}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 · 9 lines scan A 09f0aea2834c
living-stack is an MCP server published in the GitHub repository equinoxaifinance-rgb/living-stack-mcp (0 stars, last pushed 9d ago), licensed Apache-2.0. 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
sandbase-harness
MCP server "sandbase-harness" as configured in sandbaseai/sandbase-harness. Runs in Docker (ghcr.io/sandbaseai/sandbase-harness-mcp:0.3.8). Needs 2 environment variables to run.
OpenWorkProof
Agent work contracts and verifiable execution protocol — Ed25519-signed, offline-verifiable proof-carrying work for AI agents. Runs locally from the openworkproof Python package.
causallayer-mcp
Deterministic AI-liability attribution: signed, Bitcoin-anchored vendor/deployer/user fault split. Remote server at causallayer-mcp-demo.zykm9qkk7j.workers.dev.
causallayer
Deterministic AI liability attribution with Bitcoin-anchored proof certificates. Runs locally from the causallayer-mcp npm package.
mcp-opa-authz
MCP server "mcp-opa-authz" as configured in kanywst/mcp-opa-authz. Runs in Docker (ghcr.io/kanywst/mcp-opa-authz:0.2.1). Needs 5 environment variables to run.
nullsec-redteam-ai
MCP server "nullsec-redteam-ai" as configured in Panda1847/NullSec-RedTeam-AI. Runs locally from the nullsec-redteam-ai Python package.