agentfuel
Registry code: c328736b81d983cf
Rug-check risk scores for Solana tokens and a live feed of new pump.fun launches.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.agentfuel.eu/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is agentfuel live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is agentfuel free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does agentfuel have?
- 5 tools: x402_check, presign_check, injection_check, rugcheck, latest_launches.
- Is agentfuel safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
latest_launches open 1h ago
Newest pump.fun token launches with creator, dev-buy share and risk score, newest first.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum number of launches, default 20" }, "maxRisk": { "type": "number", "maximum": 100, "minimum": 0, "description": "Only launches with risk score at or below this" }, "sinceMs": { "type": "number", "description": "Only launches after this unix time in milliseconds" } } }arguments 22 linesx402_check unknown never probed
Does this paid x402 endpoint work for a paying agent? Pass, warn or fail with the main problems. Never pays the endpoint. Powered by x402 Doctor (x402-doctor.fizzl.eu), which has the full report.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "format": "uri", "description": "The x402 endpoint, e.g. https://api.example.com/paid" }, "method": { "enum": [ "GET", "POST" ], "type": "string" } } }arguments 21 linespresign_check unknown never probed
Green, orange or red verdict for a Solana transaction your bot is about to sign, such as the buy after a rug-check. Red: do not sign. Orange: ask the user first. Nothing is signed or sent. Powered by Presign Guard (presign-guard.onrender.com), which has the full report with reasons.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "transaction" ], "properties": { "intent": { "type": "string", "maxLength": 500, "description": "What the transaction should do, e.g. \"buy 0.1 SOL of <mint> on pump.fun\"" }, "transaction": { "type": "string", "maxLength": 12000, "minLength": 1, "description": "The base64 wire transaction about to be signed" } } }arguments 20 linesinjection_check unknown 1h ago
Green, orange or red verdict for a text your agent received (a token description, web page, tool result or another agent's message): does it try to make the agent ignore its instructions, pay or hand over keys? Powered by Presign Guard.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "text" ], "properties": { "task": { "type": "string", "maxLength": 500, "description": "One sentence: what the agent is doing for its user" }, "text": { "type": "string", "maxLength": 8000, "minLength": 1, "description": "The text the agent received and is about to act on" }, "source": { "enum": [ "web", "email", "tool", "api", "agent", "chat", "document", "other" ], "type": "string" } } }arguments 33 linesrugcheck unknown 1h ago
Risk score (0-100) for a Solana token mint: mint/freeze authority and holder concentration. Automated on-chain checks, not financial advice.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "mint" ], "properties": { "mint": { "type": "string", "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,44}$", "description": "Token mint address (base58)" }, "exclude": { "type": "array", "items": { "type": "string", "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,44}$" }, "description": "Token accounts to leave out of the holder check, such as a pool or bonding curve" } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc328736b81d983cf.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c328736b81d983cf/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c328736b81d983cf?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.