Taskmarket Onchain API

io.github.MostafaAshry513由 GitHub 帳號 MostafaAshry513 發布v1.0.1更新於 Nov 3, 2026

鏈上收據、餘額、交易狀態和地址活動,通過 Base 上的 x402 USDC 按次付費。

AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。

原文描述

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

已驗證Streamable HTTP可網頁執行

概覽

Taskmarket Onchain API 的託管 MCP 服務(taskmarket-x402.dynv6.net);無需登入;Streamable HTTP;4 個工具。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

端點
taskmarket-x402.dynv6.net
最近檢查

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Taskmarket Onchain API,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.MostafaAshry513%2Ftaskmarket-x402/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "taskmarket-onchain-api": {
      "type": "http",
      "url": "https://taskmarket-x402.dynv6.net/mcp"
    }
  }
}

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)

bash
# 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)

bash
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.

來源:README.md,提交 900bddd

工具

4

verify_receipt

Verify an on-chain payment/transfer against an expected recipient and amount. Returns MATCH/MISMATCH/NOT_FOUND/ERROR with on-chain evidence. Paid: $0.02 USDC on Base via x402.

輸入參數chaintokentxHash必填expectedAmount必填expectedRecipient必填

wallet_balance

Read a wallet's decoded balance (native, USDC, or any ERC-20) pinned to a block number, with explorer evidence. Paid: $0.01 USDC on Base via x402.

輸入參數chaintokenaddress必填tokenDecimals

tx_status

Get a transaction's status, block, timestamp, from/to, value, gas used and fee with explorer links. Paid: $0.01 USDC on Base via x402.

輸入參數chaintxHash必填

address_activity

List recent ERC-20 transfers involving an address (bounded, newest first) with direction, decoded value, block, tx hash and explorer links. Paid: $0.02 USDC on Base via x402.

輸入參數chainlimittokenblocksaddress必填

版本歷史

2
  1. v1.0.1最新Nov 3, 2026
  2. v1.0.0Nov 3, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分