Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add doublebearoliver-cyber/mihomo-ai-failover/plugin install mihomo-ai-failoverWrote 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/doublebearoliver-cyber/mihomo-ai-failover/mihomo-ai-failover-mihomo-ai-failover)<a href="https://agentmods.dev/mcp/doublebearoliver-cyber/mihomo-ai-failover/mihomo-ai-failover-mihomo-ai-failover"><img src="https://agentmods.dev/badge/mcp/doublebearoliver-cyber/mihomo-ai-failover/mihomo-ai-failover-mihomo-ai-failover/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/doublebearoliver-cyber/mihomo-ai-failover/mihomo-ai-failover-mihomo-ai-failover"><img src="https://agentmods.dev/badge/mcp/doublebearoliver-cyber/mihomo-ai-failover/mihomo-ai-failover-mihomo-ai-failover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mihomo-ai-failover 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 11d 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
{
"mihomo-ai-failover": {
"command": "/bin/sh",
"args": [
"-c",
"exec /bin/sh \"${CLAUDE_PLUGIN_ROOT:-.}/bin/mihomo-ai-failover-mcp\""
],
"cwd": "."
}
}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.
- 11d ago First seen · 10 lines scan A ee3304255ab3
mihomo-ai-failover is an MCP server published in the GitHub repository doublebearoliver-cyber/mihomo-ai-failover (0 stars, last pushed 1mo 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
klaviyo
MCP server "klaviyo", hosted remotely at mcp.klaviyo.com, as configured in minhnv0807/ai-business-skills.
mirroir
MCP server "mirroir" as configured in jfarcand/mirroir-mcp. Launched with ${workspaceFolder}/.build/release/mirroir-mcp --yolo.
graphmind
MCP server "graphmind" as configured in aouicher/graphmind. Launched with graphmind mcp.
oysterworkflow
MCP server "oysterworkflow" as configured in ShuxinYang111/oysterworkflow. Runs ./mcp/server.mjs with node.
crypto
Crypto token and narrative trend volume over time, with growth signals. Free key at trendsmcp.ai. Remote server at crypto.api.trendsmcp.ai.
seo
Spot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai. Remote server at seo.api.trendsmcp.ai.