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/gethelio/helioWrote 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/gethelio/helio/proxy-helio)<a href="https://agentmods.dev/mcp/gethelio/helio/proxy-helio"><img src="https://agentmods.dev/badge/mcp/gethelio/helio/proxy-helio/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/gethelio/helio/proxy-helio"><img src="https://agentmods.dev/badge/mcp/gethelio/helio/proxy-helio.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
helio 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
{
"helio": {
"command": "npx",
"args": [
"-y",
"@gethelio/proxy"
],
"env": {}
}
}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 · 10 lines scan A 0ad1c054906f
helio is an MCP server published in the GitHub repository gethelio/helio (14 stars, last pushed 3d 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-10-30.
Other mcp servers, from other repositories
iikona-mcp-proxy
MCP server "iikona-mcp-proxy" as configured in andromanpro/1c-ai-connector-mcp-proxy. Runs locally from the iikona-mcp-proxy npm package.
levitate
Levitate is an exploit development platform. Runs locally from the levitate npm package.
quantumproxies-mcp
MCP server for the QuantumProxies API — scrape, search, map, and crawl the web through residential proxies, and hand AI agents ready-to-use proxies of every type (residential, mobile, datacenter, ISP, IPv6). Connect QuantumProxies to Claude, Cursor, and a. Runs locally from the quantumproxies-mcp npm package.
evomi-mcp
MCP server for the Evomi proxy and web scraping APIs. Runs locally from the evomi-mcp Python package.
nodemaven-mcp
MCP server "nodemaven-mcp" as configured in Artirain/nodemaven-mcp. Runs locally from the nodemaven-mcp Python package.
dynamic-mcp
MCP server "dynamic-mcp" as configured in asyrjasalo/dynamic-mcp. Launched with ./target/debug/dmcp. Needs 1 environment variable to run.