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/neus/networkWrote 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/neus/network/npm-dist-neus-mcp)<a href="https://agentmods.dev/mcp/neus/network/npm-dist-neus-mcp"><img src="https://agentmods.dev/badge/mcp/neus/network/npm-dist-neus-mcp/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/neus/network/npm-dist-neus-mcp"><img src="https://agentmods.dev/badge/mcp/neus/network/npm-dist-neus-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
neus-mcp 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
{
"neus-mcp": {
"url": "https://mcp.neus.network/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 826b6210bf91
neus-mcp is an MCP server published in the GitHub repository neus/network (23 stars, last pushed 6d 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-08-30.
Other mcp servers, from other repositories
evmole
Local structured analysis of deployed EVM runtime bytecode. Runs locally from the evmole-mcp npm package.
bug-bounty-intelligence-mcp
AI security scanner for Solidity + free CC0 dataset of Sherlock audit-competition acceptance rates. Remote server at wazir-x402.duckdns.org.
3ilm-mcp
Search 1,032 verified smart contract vulnerability findings from Sherlock audits by pattern. Runs locally from the 3ilm-mcp npm package.
pentagonal-mcp
AI smart contract forge — 8-agent security audits, generation, and compilation across 8 chains. Runs locally from the pentagonal-mcp npm package. Needs 1 environment variable to run.
pumpclaw
Free token launcher on Base. Deploy ERC-20 tokens via Uniswap V4 with 80% creator fees. Runs locally from the pumpclaw-mcp npm package. Needs 2 environment variables to run.
infura-mcp
A MCP server for interacting with blockchains via Infura APIs. Runs locally from the infura-mcp npm package.