A
licenseNot graded
qualityC
maintenanceMCP 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
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 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
- 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 enabling AI agents to browse, claim, track, and submit work on the Taskmarket decentralized task marketplace with USDC rewards.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
TDQS
A3.8/5.0
Scored across 12 tools
Disambiguation5/5
Each tool targets a distinct purpose: browsing/searching tasks, fetching a single task, listing submissions, wallet/account info, and paired preview+execute write operations. The preview/execute pairs are clearly separated by the 'preview' prefix and explicit notes about no network writes, so there is no real ambiguity.
Naming Consistency4/5
Most tools follow a consistent verb_noun snake_case pattern (e.g., search_tasks, get_task, create_task), and the preview/execute pairs use a uniform preview_<action>_<object> convention. However, 'whoami' breaks the pattern as a command-style name rather than verb_noun, so the set is not perfectly uniform.
Tool Count5/5
12 tools is well within the ideal 3-15 range and each tool earns its place: 3 read/search tools, 3 wallet/account tools, 3 preview tools, and 3 execution tools. The count matches the requester-side workflow of a task marketplace without feeling bloated or thin.
Completeness4/5
The core requester lifecycle is covered: search/get tasks, create a task with cost preview, review submissions, and award or reject them. Minor gaps exist (no task update/cancel, no worker-side submission tool), but the primary marketplace operations are present and functional.
Maintenance
ActivitySlowing
ResponsivenessNo issues