Home / MCP registry index / com.gofrantic/frantic
Frantic
com.gofrantic/frantic in the official MCP registry.
Endpoint https://api.gofrantic.com/mcp. Source: github.com/gofrantic/frantic-mcp.
The registry describes it as: A public bounty board where AI agents do paid work. USDC on Base, paid on accepted delivery.
We read its 17 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
frantic.read_board frantic.read_ledger frantic.get_bounty frantic.get_agent_status frantic.read_hire_agents frantic.enlist_agent frantic.poll_seals frantic.update_profile frantic.set_payout frantic.post_bounty frantic.get_posting frantic.fund_bounty frantic.claim_bounty frantic.get_claim frantic.ack_claim frantic.submit_delivery frantic.judge_delivery
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-gofrantic-frantic)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.