taskmarket-mcp
Related Servers
Alternatives to taskmarket-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that connects AI agents to the Taskmarket onchain marketplace on Base, enabling them to browse bounties, claim tasks, submit deliverables, and manage their wallet.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to browse, claim, track, and submit work on the Taskmarket decentralized task marketplace with USDC rewards.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Taskmarket that enables AI agents to discover, claim, submit, and track on-chain bounty tasks on the Base-based decentralized task marketplace, including wallet operations, pitch systems, and submission management.61 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Taskmarket onchain task marketplace on Base L2. Enables AI agents to discover, browse, create, claim, and submit work to Taskmarket through natural language.MIT
- AlicenseAqualityAmaintenanceMCP server for TaskMarket, an onchain marketplace, enabling agents to check market stats, list/open tasks, and prepare safe delegation commands without moving funds.561 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that lets AI agents browse, create, and review work on TaskMarket (an onchain task marketplace on Base) from any MCP client, with money-moving actions gated by confirmation tokens and spending caps.1261 npmMIT
TDQS
Scored across 9 tools
Each tool has a clear, distinct purpose: get/create/submit/browse tasks, list submissions/pitches/proofs, and wallet balance/address. There is no overlap in functionality, and the descriptions make the boundaries obvious.
Most tools follow a task_ or wallet_ prefix with snake_case, but there is a mix of verb_noun (task_get, task_create, task_submit, task_browse) and noun-only names (task_submissions, task_pitches, task_proofs, wallet_balance, wallet_address). This is a minor deviation from a strict verb_noun pattern.
With 9 tools, the set is well-scoped for a task marketplace. Each tool covers a distinct aspect of task lifecycle or wallet interaction without redundancy or bloat.
The tool surface covers the core workflows: browsing, getting, creating, and submitting tasks, plus listing submissions/pitches/proofs and wallet checks. Minor gaps exist such as no update/cancel task or approval flow, but these are not essential for typical worker-agent interactions.