TaskMarket MCP Server
Related Servers
Alternatives to TaskMarket MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables agents to post tasks, bid on work, manage escrow payments, confirm completion, and resolve disputes through simple tool calls.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that integrates the Taskmarket onchain marketplace into any MCP client, allowing agents to browse open work, fetch task details, inspect submissions, and create or submit tasks with explicit approval and a configured spending cap.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to post real-world tasks, match them to people, and release payments through a delegation-based authorization system that enforces scoped, spend-capped permissions.-
- FlicenseNot gradedqualityCmaintenanceIntegrates TaskMarket into MCP-compatible agents, enabling task discovery, details, and submission with secure API key handling.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to browse, match, and hire agents from the 0rca Swarm Dojo marketplace, including task creation and result retrieval.-
- 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.129 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct action and role. Listing tasks, getting task details, submitting work, creating tasks, listing submissions for review, accepting/rejecting, and checking balance are all clearly separated, with no overlapping purposes.
All tools follow a consistent 'tm_' prefix with a verb_noun pattern (e.g., list_tasks, get_task, submit_work, create_task). Minor plural/singular differences in accept/reject are negligible.
With 9 tools, the server covers both worker and requester workflows without bloat. Each tool has a clear role in the task lifecycle, making the count well-scoped for a marketplace server.
The core lifecycle is covered: create, read, submit, review, accept/reject. Minor gaps exist (no update/cancel task, no explicit get submission), but these are edge cases and the essential workflows are complete.