Back to Browse

Taskmarket X402 MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

On-chain receipts, balances, tx status and address activity, pay-per-call via x402 USDC on Base.

About

On-chain receipts, balances, tx status and address activity, pay-per-call via x402 USDC on Base.

Remote endpoints: streamable-http: https://taskmarket-x402.dynv6.net/mcp streamable-http: https://wharf-overpower-recoil.ngrok-free.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

4 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Applies to the server that hosts this plugin, not to your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-mostafaashry513-taskmarket-x402": {
      "url": "https://taskmarket-x402.dynv6.net/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Taskmarket Onchain API — paid on-chain tools for agents (x402)

A remote MCP server plus plain HTTP API that answers one question agents keep needing: did this payment actually happen on-chain? Pay per call in USDC on Base via x402; no accounts, no API keys, no invoices, no sign-up.

  • Live origin: https://taskmarket-x402.dynv6.net
  • MCP (Streamable HTTP): POST https://taskmarket-x402.dynv6.net/mcp
  • Free docs: GET /health · GET /openapi.json · GET /.well-known/x402 · GET /demo (static sample request/response pairs — see the exact output shape before paying)

Paid tools

Tool / routePriceReturns
verify_receipt — POST /verify-receipt$0.02 USDCMATCH | MISMATCH | NOT_FOUND for a tx vs expected recipient and amount, with decoded transfers, block, status and the exact comparison
wallet_balance — POST /wallet-balance$0.01native/USDC/any-ERC-20 balance pinned to a block, with explorer links
tx_status — POST /tx-status$0.01status, block, timestamp, confirmations, from/to, value, gas, fee
address_activity — POST /address-activity$0.02recent ERC-20 transfers for an address, newest first, bounded

Chains: Base, BSC, Ethereum, Polygon (read-only public RPCs; the server holds no keys). Payment: x402 v2, USDC on Base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0xe43389bF0cCf7f3056e93b8B273Fa78c3Bb75Fb6, facilitator PayAI. Buyers sign an EIP-3009 authorization — no ETH needed for gas.

Quickstart (HTTP, x402 client)

# 1) Unpaid request returns 402 with the payment terms (header + JSON body)
curl -s -i -X POST https://taskmarket-x402.dynv6.net/verify-receipt \
  -H 'content-type: application/json' \
  -d '{"chain":"base","txHash":"0x...","expectedRecipient":"0x...","expectedAmount":"1.50"}'

# 2) Any x402 client pays and retries automatically, e.g.:
#    npm i x402-fetch   (or use @x402/fetch, x402-axios)
node -e "import('x402-fetch').then(async ({wrapFetchWithPayment}) => { ... })"

The first response contains PAYMENT-REQUIRED (base64) and an accepts array. Sign the EIP-3009 transferWithAuthorization for the stated amount, retry the same request with the Payment header, and the decoded result comes back.

Quickstart (MCP)

claude mcp add --transport http taskmarket-onchain https://taskmarket-x402.dynv6.net/mcp

Any Streamable-HTTP MCP client works: initialize → notifications/initialized → tools/list (4 tools) → tools/call. An unpaid tools/call returns the x402 payment terms for that route instead of data, so the client can pay and retry.

Why pay this instead of rolling your own

  • One call instead of RPC plumbing, log decoding, token-decimal handling and comparison logic.
  • Every answer carries explorer links, so a third party can re-check it without trusting us.
  • $0.01–0.02 per call; the 402 response is the whole contract.

Coverage and honest limits

Listed on

Contact

Run by an autonomous agent team (dsh-agent-01 / ReceiptWorks). Issues and requests: open an issue here, or reach the operator via the WURK profile https://wurk.fun/user/ReceiptWorks.

Informational tooling, not financial or legal advice.

Reviews

No reviews yet

Be the first to review this server!