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/XFuel-Lab/xfuel-protocolWrote 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/xfuel-lab/xfuel-protocol/mcp-xfuel-mcp)<a href="https://agentmods.dev/mcp/xfuel-lab/xfuel-protocol/mcp-xfuel-mcp"><img src="https://agentmods.dev/badge/mcp/xfuel-lab/xfuel-protocol/mcp-xfuel-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/xfuel-lab/xfuel-protocol/mcp-xfuel-mcp"><img src="https://agentmods.dev/badge/mcp/xfuel-lab/xfuel-protocol/mcp-xfuel-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xfuel-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 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
{
"xfuel-mcp": {
"command": "npx",
"args": [
"-y",
"xfuel-mcp"
],
"env": {
"XFUEL_API_URL": "https://api-testnet.xfuel.app",
"XFUEL_API_KEY": "xfuel-demo",
"XFUEL_MCP_AUTH_TOKEN": "",
"XFUEL_RPC_URL": "",
"ZK_VERIFIER_ADDRESS": "",
"XFUEL_PAYER_PRIVATE_KEY": ""
}
}
}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 · 17 lines scan A e78197c17c65
xfuel-mcp is an MCP server published in the GitHub repository XFuel-Lab/xfuel-protocol (1 stars, last pushed 10d 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-31.
Other mcp servers, from other repositories
agoragentic
Triptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base. Runs locally from the agoragentic-mcp npm package. Needs 3 environment variables to run.
hive-mcp-vault
A2A ZK wallet recovery — guardian swarm, no seed phrase, HiveLaw enforcement. Remote server at hive-mcp-vault.onrender.com.
xenarch-mcp
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2. Runs locally from the @xenarch/agent-mcp npm package. Needs 4 environment variables to run.
hive-mcp-swap
Cross-chain token swaps for autonomous agents on Base L2 and partner rails. Remote server at hive-mcp-swap.onrender.com.
hive-mcp-depin
MCP server: DePIN reward routing, capacity verification, settlement reports · Hive Civilization. Remote server at hive-mcp-gateway.onrender.com.
hive-mcp-evaluator
MCP server: NEED + YIELD + CLEAN-MONEY gates with EIP-3009 attestations · Hive Civilization. Remote server at hive-mcp-gateway.onrender.com.