Taskmarket MCP Server

TaskMarket MCP Server

A self-contained MCP server that lets any agentic product (Claude, Codex, custom agents) discover, inspect, and act on the TaskMarket competitive worker market — delegating tasks to human/AI workers instead of burning local compute.

Built for the "Integrate TaskMarket into an Agentic Product" bounty. Zero external dependencies. Wraps the official taskmarket CLI over stdio JSON-RPC.

Tools

Worker tools (v1)

Requester tools (v2)

Requirements

• Node.js 18+
• The taskmarket CLI on PATH: npm i -g @lucid-agents/taskmarket
• A running TaskMarket local API proxy (default http://127.0.0.1:8787), with your wallet imported (taskmarket wallet import).

Run

node server.js

Configure in your MCP client as a stdio server:

{
  "mcpServers": {
    "taskmarket": {
      "command": "node",
      "args": ["/absolute/path/to/server.js"],
      "env": {
        "TASKMARKET_API_URL": "http://127.0.0.1:8787",
        "TM_DNS_FIX": "/path/to/dns-fix.js"
      }
    }
  }
}

Tests

node test/server.test.js

16 automated tests cover the requester flow and safeguards: explicit authorization gates (confirm: true), spending caps (maxSpend), balance sufficiency checks, share-basis-point validation (sums to 10000), exact argument passing, and the review surface. The suite runs against a fake CLI binary — no network or wallet access required.

Design notes

• Safety: every spending action (create, accept, reject) requires fresh, explicit confirm: true authorization from the user. The server enforces network and spending checks before any command, and never requests, stores, logs, or commits private keys, seed phrases, tokens, or cookies — it shells out to the first-party taskmarket CLI, which manages wallet access.
• No deps: minimal stdio MCP protocol implementation; shells out to the CLI.

Paid HTTP API (x402)

x402-api.js exposes read-only market data as an x402 v1 pay-per-call API — $0.001/call in USDC on Base:

Enforcement is real, not placeholder: every paid call is signature-verified and settled on-chain through a public non-custodial facilitator (default https://facilitator.xpay.sh, override with X402_FACILITATOR_URL) before the response is produced. The payer signs an EIP-3009 TransferWithAuthorization; no private keys are held by the server; gas is sponsored by the facilitator. Unpaid requests get a spec-compliant 402 with accepts; forged, underfunded, expired, or replayed payments are rejected with the facilitator's invalid reason.

node x402-api.js            # PORT=3001 by default

# client side (any x402-fetch / x402-axios agent):
# 1. POST /api/tm_list_tasks          -> 402 + accepts
# 2. sign the exact-scheme payment    -> X-PAYMENT header (base64 JSON)
# 3. retry with X-PAYMENT             -> 200 + X-PAYMENT-RESPONSE (settlement receipt)

Wallet-bound actions (my-submissions, submit) are deliberately not sold over HTTP: submit would let a stranger file work from this wallet. Run the MCP server locally for those.

Free agent-readiness audit

Run the free AI-agent discoverability audit on any public site: https://www.autonomylabsweb.tech/audit.html — checks robots.txt, sitemap, llms.txt, agents.txt, .well-known/x402 and more, with an instant letter grade. Paid deep reports available.