{
  "markdown": "# taskfleet-mcp\n\nAn [MCP](https://modelcontextprotocol.io) server that exposes **TaskFleet**'s\npay-per-call AI task APIs as tools any MCP-capable agent can discover and call:\nweb search, web scraping, structured extraction, translation, code review,\nsummarization, and on-chain wallet intelligence.\n\nPayment is handled by the **x402** protocol (USDC on Base) — the caller brings\nthe wallet; there are no accounts or API keys.\n\n## Why this exists\n\nIt's a discovery channel. Agents that browse MCP registries or load MCP\nservers can find and use TaskFleet directly, in addition to the x402\ndirectories. The tool list is loaded live from the fleet's manifest, so new\nservices appear automatically.\n\n## Use it (as an agent operator)\n\nAdd to your MCP client config (e.g. Claude Desktop, or any MCP host):\n\n```json\n{\n  \"mcpServers\": {\n    \"taskfleet\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"taskfleet-mcp\"],\n      \"env\": {\n        \"BUYER_WALLET_PRIVATE_KEY\": \"0xYOUR_WALLET_KEY\"\n      }\n    }\n  }\n}\n```\n\n- **With** `BUYER_WALLET_PRIVATE_KEY` (an EVM key holding a little USDC on Base):\n  tool calls auto-pay via x402 and return results.\n- **Without** it: tools still list (discovery works) and a call returns the\n  x402 payment instructions, so an x402-capable client can pay itself.\n- `TASKFLEET_URL` overrides the target (defaults to `https://taskfleet.net`).\n\nThe wallet key stays on the operator's machine — it never reaches TaskFleet,\nwhich only ever sees the on-chain payment.\n\n## Tools\n\nOne tool per TaskFleet service, named `taskfleet_<service>` (e.g.\n`taskfleet_search`, `taskfleet_scrape`, `taskfleet_wallet_intel`). Each tool's\ninput schema and price come straight from the fleet manifest.\n\n## Publish it (as the fleet operator — discovery)\n\n```bash\ncd mcp\nnpm install\nnpm publish            # publishes taskfleet-mcp to npm\n```\n\nOnce on npm it's installable via `npx taskfleet-mcp` and can be listed in MCP\nregistries (the public MCP Registry, Smithery, PulseMCP, etc.) — each listing\nis another place agents discover TaskFleet. Submitting to those registries is\nfree and generally just points at the npm package or this repo.\n\n## Local test\n\n```bash\nnpm install\nTASKFLEET_URL=https://taskfleet.net node index.mjs\n# should print: taskfleet-mcp v0.1.0: 14 tools from https://taskfleet.net (payment: caller-pays)\n```\n",
  "bytes": 2330,
  "sha": "18a2a635212a7ddc4e37efce5671daf2785f11cb65cdc9abca54486ba64be06c",
  "repo_slug": "bfai-1/taskfleet-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_bfai_1_taskfleet_mcp_42cf620f/readme"
}