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/mericcintosun/AvaKitWrote 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/mericcintosun/avakit/mcp-avalanche)<a href="https://agentmods.dev/mcp/mericcintosun/avakit/mcp-avalanche"><img src="https://agentmods.dev/badge/mcp/mericcintosun/avakit/mcp-avalanche/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/mericcintosun/avakit/mcp-avalanche"><img src="https://agentmods.dev/badge/mcp/mericcintosun/avakit/mcp-avalanche.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
avalanche 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 9d 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
{
"avalanche": {
"command": "npx",
"args": [
"-y",
"@avakit/mcp"
],
"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.
- 9d ago First seen · 10 lines scan A d834654e3580
avalanche is an MCP server published in the GitHub repository mericcintosun/AvaKit (12 stars, last pushed 6d 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-30.
Other mcp servers, from other repositories
nft-log-analyzer
MCP server "nft-log-analyzer" as configured in mashish/nft-log-analyzer. Runs mcp_server/server.py with python. Needs 5 environment variables to run.
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
mcp
MCP server "mcp" as configured in grokloop/grokchain-mcp. Runs locally from the @grokchain/mcp npm package.
mcp
MCP server that lets AI agents create, fetch, verify, and publish Molpha oracle data. Runs locally from the @molpha/mcp npm package. Needs 20 environment variables to run.
oddsrail
MCP server giving AI trading agents access to prediction markets (Polymarket, Kalshi) with on-chain builder-code attribution and trading signals. Runs locally from the oddsrail Python package. Needs 1 environment variable to run.
fibx
Swap, transfer, track a portfolio and use Aave V3 on Base, HyperEVM and Monad. Runs locally from the fibx npm package. Needs 2 environment variables to run.