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/Nodeflare-app/nodeflare-mcpWrote 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/nodeflare-app/nodeflare-mcp/nodeflare)<a href="https://agentmods.dev/mcp/nodeflare-app/nodeflare-mcp/nodeflare"><img src="https://agentmods.dev/badge/mcp/nodeflare-app/nodeflare-mcp/nodeflare/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/nodeflare-app/nodeflare-mcp/nodeflare"><img src="https://agentmods.dev/badge/mcp/nodeflare-app/nodeflare-mcp/nodeflare.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nodeflare 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 1mo 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
{
"nodeflare": {
"command": "npx",
"args": [
"-y",
"nodeflare-mcp"
]
}
}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.
- 1mo ago First seen · 9 lines scan A 44552bea1696
nodeflare is an MCP server published in the GitHub repository Nodeflare-app/nodeflare-mcp (1 stars, last pushed 2mo 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-31.
Other mcp servers, from other repositories
evm-mcp-server
MCP server for interacting with EVM-compatible blockchains - supports 22 tools and 10 prompts across 60+ networks. Runs locally from the @mcpdotdirect/evm-mcp-server npm package.
evm-mcp-http
MCP server for interacting with EVM-compatible blockchains - supports 22 tools and 10 prompts across 60+ networks. Runs locally from the @mcpdotdirect/evm-mcp-server npm package.
etherscan-mcp-server
MCP server for Etherscan — Ethereum blockchain explorer API for AI assistants. Runs locally from the etherscan-mcp-server npm package.
evmole
Local structured analysis of deployed EVM runtime bytecode. Runs locally from the evmole-mcp npm package.
alchemy
MCP server "alchemy", hosted remotely at mcp.alchemy.com, as configured in alchemyplatform/alchemy-claude-plugin.
chainstack
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. Remote server at mcp.chainstack.com.