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/LayeroInfra/layero-claudeWrote 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/layeroinfra/layero-claude/layero)<a href="https://agentmods.dev/mcp/layeroinfra/layero-claude/layero"><img src="https://agentmods.dev/badge/mcp/layeroinfra/layero-claude/layero/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/layeroinfra/layero-claude/layero"><img src="https://agentmods.dev/badge/mcp/layeroinfra/layero-claude/layero.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo 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.
- 1mo 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 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-31.
Other mcp servers, from other repositories
mcp
Official Sevalla MCP — full PaaS API access through just 2 tools. Remote server at mcp.sevalla.com.
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.
coolify-mcp
MCP server for Coolify API operations. Runs locally from the @fndchagas/coolify-mcp npm package. Needs 6 environment variables to run.
kinsta-mcp
Model Context Protocol (MCP) server for Kinsta WordPress hosting. Runs locally from the kinsta-mcp npm package.
architect-to-product
MCP server that turns software architectures into tested, secure products. Runs locally from the architect-to-product npm package.
codebase-memory
MCP server "codebase-memory" as configured in BernhardJackiewicz/architect-to-product. Launched with codebase-memory-mcp.