A
licenseNot graded
qualityF
maintenanceLocal stdio MCP server for x402-powered paid crypto intelligence, decision verification, and agent automation search over USDC micropayments on Base.
77 npm
MIT
Frantic
by gofrantic
Related Servers
Alternatives to Frantic
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables stdio-only MCP clients to connect to Agent Community's hosted Streamable HTTP MCP server for accessing hosted agents and tools.11 npmMIT
- AlicenseAqualityDmaintenanceConnects Claude and other MCP-compatible AI assistants to the AI Bounty Board, enabling natural language discovery, claiming, and submission of bounties.5MIT
GenieOS MCP Serverofficial
AlicenseAqualityCmaintenanceStdio bridge for editors to connect to the GenieOS MCP server, enabling AI agents to interact with GenieOS via Streamable HTTP transport.645 npmMIT
PoYo MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceLocal stdio bridge to the hosted PoYo MCP server, enabling discovery and execution of AI models via chat, generation tasks, and agent skills.1MIT
@opsmaxx/mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables stdio-only MCP clients like Claude Desktop to connect to a running OpsMaxx desktop app by relaying messages to its authenticated HTTP MCP bridge, so they receive the same access controls, approvals, secret redaction, and audit logging as HTTP clients.-
TDQS
A4.3/5.0
Scored across 14 tools
Disambiguation4/5
Each tool targets a distinct action and resource, so the core workflow is easy to navigate. The only mild ambiguity is between read_ledger and read_board, since both expose receipt/feed-style data, but their descriptions clarify the board projection versus the raw ledger feed.
Naming Consistency5/5
All 14 tools use a consistent snake_case verb_noun pattern, from post_bounty and fund_bounty to claim_bounty and judge_delivery. The small read/get variation still follows a readable convention, with 'read' for public feeds/projections and 'get' for single-resource lookups.
Tool Count5/5
Fourteen tools is well within the ideal range and each tool covers a necessary step in the bounty and agent lifecycle. The set covers intake, funding, public reads, onboarding, profile/payout management, claims, delivery, and judging without unnecessary bloat.
Completeness4/5
The main bounty lifecycle of post, fund, claim, deliver, judge is fully represented, and the agent-facing flow from enlistment through seals, payout, and status is well covered. Minor gaps include no direct claim/delivery read-back tool or bounty update/cancel action, but these are workable through board, ledger, and status endpoints.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive