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/helius-labs/core-aiWrote 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/helius-labs/core-ai/helius)<a href="https://agentmods.dev/mcp/helius-labs/core-ai/helius"><img src="https://agentmods.dev/badge/mcp/helius-labs/core-ai/helius/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/helius-labs/core-ai/helius"><img src="https://agentmods.dev/badge/mcp/helius-labs/core-ai/helius.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
helius 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
{
"helius": {
"command": "npx",
"args": [
"[email protected]"
]
}
}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 Changed 1be9ef570e18
- 1mo ago Changed fe70a6ec97c0
- 1mo ago First seen · 8 lines scan A b560a04daa68
helius is an MCP server published in the GitHub repository helius-labs/core-ai (29 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
solana
Solana MCP server for wallet, transactions & programs. Runs locally from the solana-mcp-server npm package.
evmscope
EVM blockchain intelligence toolkit for AI agents. 20 tools across 5 chains. Zero config. Runs locally from the evmscope npm package.
mcp-server
WAVE MCP Server - Exposes WAVE streaming APIs as tools for AI agents. Runs locally from the @wave-av/mcp-server npm package.
clawphunks
Mint and trade ClawPhunks NFTs - 10k pixel punks for AI agents. x402 payment, ethscriptions on L1. Runs locally from the clawphunks-mcp npm package.
thryx-mcp-server
ThryxProtocol v3.1 — gasless AI agent launchpad on Base. 21 tools wrap thryx.fun HTTP API. Runs locally from the @thryx/mcp-server npm package. Needs 2 environment variables to run.
regex-lab-mcp
Test, explain, and generate regular expressions. Runs locally from the regex-lab-mcp npm package.