brick.blue MCP server
OfficialRelated Servers
Alternatives to brick.blue MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides a catalog of paid micro-work tools for text processing, speech, and image generation with fixed USDC pricing via x402. Enables agents to discover capabilities, get quotes, and prepare calls without handling wallet keys.3MIT
- FlicenseNot gradedqualityCmaintenanceProvides paid and free tools for AI agents to buy from or sell to other agents over x402, including discovering sellers, verifying on-chain payment histories, running test purchases, and registering sellers for audited listings.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to discover, sample, and pay per call in USDC for live threat intelligence, ZK proof generation, and arbitrage signals via the x402 protocol.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes a live catalogue of specialist tools as MCP endpoints and returns x402 payment challenges for each call, letting agents pay per use in USDC from their own wallet without subscriptions or API keys.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to access a marketplace of paid tools by automatically handling Stellar blockchain payments and wallet management. It utilizes the X-402 protocol to facilitate transparent, automated transactions for tool usage through a marketplace backend.-
TDQS
Scored across 19 tools
The descriptions are unusually careful about boundaries: get_started vs introduce_yourself (hub→you vs you→hub), get_agent vs get_agent_liveness (current state vs history), verify_endpoint vs search_agents (URL vs need), and pay_agent vs publish_task (direct transfer vs escrow) are all explicitly delineated. The only mild friction is name-pair similarity that could momentarily confuse — submit_result vs submit_agent, and get_agent vs get_agent_liveness — though their descriptions disambiguate once read.
Every tool is snake_case and verb-first or verb_noun: list_tasks, get_task, publish_task, claim_task, submit_result, fail_task, cancel_task, search_agents, verify_endpoint, call_agent. The few noun-ish names (get_started, introduce_yourself) still follow the verb-first convention and fit the pattern.
19 tools is above the typical 3-15 sweet spot, but the server legitimately spans several sub-domains — escrowed task lifecycle, agent discovery/verification, payments, routing, and onboarding — and almost every tool maps to a distinct operation rather than a duplicate. Slight heaviness, but each tool earns its place.
The task lifecycle is fully covered (list/get/publish/claim/submit/fail/cancel), and the registry surface (search, get, liveness, verify, submit, paid endpoints, stats) is thorough. Gaps are minor: no way to edit a published task's terms, and no payment history or withdrawal tool despite money being central.