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/commands/nodeflare-app/nodeflare-mcp/logs)<a href="https://agentmods.dev/commands/nodeflare-app/nodeflare-mcp/logs"><img src="https://agentmods.dev/badge/commands/nodeflare-app/nodeflare-mcp/logs/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/commands/nodeflare-app/nodeflare-mcp/logs"><img src="https://agentmods.dev/badge/commands/nodeflare-app/nodeflare-mcp/logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00009 | $0.00250 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
logs 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 10d 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
Fetch and summarise event logs for a contract using the nodeflare MCP server.
- Parse
$ARGUMENTSinto: a contract address (required), an optional chain slug (defaultethereum), and an optional block range (fromBlock/toBlock). If no range is given, first callget_block_numberand query a recent window (e.g. the last few thousand blocks) so the range stays within limits. - Call
get_logsfor that address and range. - Summarise: how many events, grouped by the event signature (topic0). For recognisable signatures (ERC-20
Transfer/Approval, UniswapSwap, etc.) decode and count them, and highlight notable entries (largest transfers, most active addresses). get_logsneeds a keyed request — remind the user to setNODEFLARE_API_KEY(free tier: 2,000,000 CU/month at https://nodeflare.app) if the call reports the method is unavailable on the public tier.
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.
- 10d ago First seen · 12 lines · 9 tokens per session scan A 04760d2b5cc0
logs is a command published in the GitHub repository Nodeflare-app/nodeflare-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 250 once invoked, about $0.0000 per session on Opus 5. 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 commands, from other repositories
audit
Full security audit of a Solidity/Vyper/Rust contract or directory. Runs the entire vuln-skills library and dispatches DeFi specialist subagents based on detected protocol type.
audit-multi-chain
Diff the on-chain configuration of one contract deployed across multiple chains — owner, oracle, fees, timelock, pause state, proxy impl — and flag the chain that drifted.
exploit
Generate a working Foundry PoC that exploits a specific finding. Compiles and passes.
pre-deploy
Interactive pre-launch security checklist — walk the operational and code-safety gates and produce a final GO / NO-GO with each item PASS / FAIL / N-A.
rug-check
Fast owner-power / rugability scan — score how much unilateral control the deployer holds and return a 0-100 rug-risk verdict.
audit-live
Audit a deployed contract on a live chain. Pulls verified source from the block explorer, optionally forks the chain for live-state simulation.