TaskMarket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TM_DNS_FIX | No | Optional path to a DNS fix script to work around network issues. | |
| TASKMARKET_API_URL | No | URL of the TaskMarket local API proxy. Defaults to http://127.0.0.1:8787. | http://127.0.0.1:8787 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tm_list_tasksA | List available TaskMarket tasks (bounties/benchmarks/auctions). |
| tm_get_taskB | Get full details of one TaskMarket task. |
| tm_my_submissionsA | List all submissions made by this wallet. |
| tm_wallet_balanceA | Show the worker USDC balance. |
| tm_submit_workB | Submit work (a file) for a TaskMarket task. Requires TASKMARKET_API_URL and worker wallet. |
| tm_create_taskA | Create a TaskMarket task (costs the reward in USDC, escrowed on Base). SAFETY: requires confirm:true after reviewing the exact description, reward, deadline, deliverables, network and maximum spend. The server refuses to create if the wallet balance is below reward + platform fee, if the network is not Base, or if confirm is not exactly true. Never retries a payment with unknown settlement. |
| tm_task_submissionsB | List submissions for a task you posted (requester review). Presents work for human review; never auto-accepts. |
| tm_accept_submissionsA | Accept winners on a bounty/benchmark task with explicit share basis points (sums to 10000). Requires confirm:true and explicit winner specs. Costs 0.001 USDC relay fee. |
| tm_reject_submissionB | Reject a spam or low-quality submission (costs 0.001 USDC relay fee). Requires confirm:true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.