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/BrainDAO/mcp-near-agentWrote 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/braindao/mcp-near-agent/mcp-near)<a href="https://agentmods.dev/mcp/braindao/mcp-near-agent/mcp-near"><img src="https://agentmods.dev/badge/mcp/braindao/mcp-near-agent/mcp-near/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/braindao/mcp-near-agent/mcp-near"><img src="https://agentmods.dev/badge/mcp/braindao/mcp-near-agent/mcp-near.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-near 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 9 lines scan A 3c842e6b31d3
mcp-near is an MCP server published in the GitHub repository BrainDAO/mcp-near-agent (1 stars, last pushed 2mo ago), with no licence file. 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
sui-mcp-server
53-tool MCP server for Sui blockchain — wallets, DeFi, Move contracts, staking, SuiNS, analytics. Runs locally from the sui-mcp-server npm package.
base-intel-mcp
Read-only on-chain intel for AI agents on Base: balances, tokens, gas, tx status. No API keys. Remote server at base.datakoot.com.
evmscope
EVM blockchain intelligence toolkit for AI agents. 20 tools across 5 chains. Zero config. Runs locally from the evmscope npm package.
mtrkr-mcp-server
MCP server exposing MTRKR wallet intelligence tools for MegaETH. Runs locally from the mtrkr-mcp-server npm package.
mcp-server-debank
MCP server "mcp-server-debank" as configured in caiovicentino/debank-mcp-server. Runs locally from the mcp-server-debank Python package.
voltix-mcp
DeFi intelligence for Claude: whale tracking, alpha signals, yields, token safety. USDC on Base. Runs locally from the voltix-mcp npm package. Needs 1 environment variable to run.