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/layeroinfra/layero-claude/layerogit clone --depth 1 https://github.com/LayeroInfra/layero-claudeGrade A, and why
layero 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 2d 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
{
"layero": {
"type": "http",
"url": "https://mcp.layero.ru/mcp",
"headers": {
"Authorization": "Bearer ${LAYERO_TOKEN}"
}
}
}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.
- 2d ago First seen · 9 lines scan A 56da8c3ea8d6
layero is an MCP server published in the GitHub repository LayeroInfra/layero-claude (0 stars, last pushed 26d 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-31.
Other mcp servers, from other repositories
openpouch
Agent-native hosting: deploy any folder to a live URL in one command. No approve tool. Runs locally from the @openpouch/mcp npm package.
openpouch
openpouch 🦘 MCP server — agent-native deploy tools for any MCP-capable harness (Claude Code, Codex, Cursor, Windsurf, …). stdio, open standard. No approve tool — production approval stays human-only. Runs locally from the @openpouch/mcp npm package.
moose-dev
MCP server "moose-dev", hosted remotely at localhost, as configured in 514-labs/moosestack.
defang
MCP server "defang" as configured in DefangLabs/defang. Launched with defang mcp serve.
mcp
Deploy static websites from AI agents. Free at mcp.shipstatic.com — no install, no signup. Runs locally from the @shipstatic/mcp npm package. Needs 1 environment variable to run.
architect-to-product
MCP server that turns software architectures into tested, secure products. Runs locally from the architect-to-product npm package.