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/aotter/mantleWrote 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/aotter/mantle/mantle-cloud)<a href="https://agentmods.dev/mcp/aotter/mantle/mantle-cloud"><img src="https://agentmods.dev/badge/mcp/aotter/mantle/mantle-cloud/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/aotter/mantle/mantle-cloud"><img src="https://agentmods.dev/badge/mcp/aotter/mantle/mantle-cloud.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mantle-cloud 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 19d 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
{
"mantle-cloud": {
"type": "http",
"url": "https://cloud.mantle.tools/mcp"
}
}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.
- 19d ago First seen · 6 lines scan A 0e51a7cf06f8
mantle-cloud is an MCP server published in the GitHub repository aotter/mantle (5 stars, last pushed today), 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-09-28.
Other mcp servers, from other repositories
tailscale-mcp
Tailscale MCP server for managing your tailnet from AI assistants. Runs locally from the @yawlabs/tailscale-mcp npm package.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
ionoscloud-mcp
MCP server "ionoscloud-mcp" as configured in ionos-cloud/ionoscloud-mcp. Runs in Docker (ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1). Needs 5 environment variables to run.
ionoscloud
MCP server "ionoscloud" as configured in ionos-cloud/ionoscloud-mcp. Launched with ionoscloud-mcp. Needs 2 environment variables to run.
chainstack
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. Remote server at mcp.chainstack.com.
skykick-mcp
MCP server "skykick-mcp" as configured in Servosity/msp-skills. Launched with https://github.com/Servosity/msp-skills/releases/download/skykick-v0.1.4/skykick. Needs 6 environment variables to run.