Back to Browse

Taskfleet MCP Server

by BFAI 1
Developer ToolsModerate6.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Pay-per-call MCP tools: web search, scraping, on-chain wallet intel, extraction. x402 USDC on Base.

About

Pay-per-call MCP tools: web search, scraping, on-chain wallet intel, extraction. x402 USDC on Base.

Security Report

6.7
Moderate6.7Moderate Risk

A well-structured MCP server that safely exposes TaskFleet's pay-per-call AI APIs through the x402 protocol. The server properly handles wallet credentials via environment variables, implements appropriate error handling, and maintains clear separation between authenticated and unauthenticated modes. The main concern is dynamic manifest loading from a remote server with minimal validation, but this is mitigated by the transparent nature of the service and proper error handling. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

4 files analyzed · 6 issues found

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

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Optional. EVM private key used to auto-pay x402 charges (USDC on Base). If omitted, tools still list and calls return x402 payment instructions for the client to settle itself.Required

Environment variable: BUYER_WALLET_PRIVATE_KEY

Optional. Override the TaskFleet base URL (default: https://taskfleet.net).Optional

Environment variable: TASKFLEET_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-bfai-1-taskfleet-mcp": {
      "env": {
        "TASKFLEET_URL": "your-taskfleet-url-here",
        "BUYER_WALLET_PRIVATE_KEY": "your-buyer-wallet-private-key-here"
      },
      "args": [
        "-y",
        "taskfleet-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

taskfleet-mcp

An MCP server that exposes TaskFleet's pay-per-call AI task APIs as tools any MCP-capable agent can discover and call: web search, web scraping, structured extraction, translation, code review, summarization, and on-chain wallet intelligence.

Payment is handled by the x402 protocol (USDC on Base) — the caller brings the wallet; there are no accounts or API keys.

Why this exists

It's a discovery channel. Agents that browse MCP registries or load MCP servers can find and use TaskFleet directly, in addition to the x402 directories. The tool list is loaded live from the fleet's manifest, so new services appear automatically.

Use it (as an agent operator)

Add to your MCP client config (e.g. Claude Desktop, or any MCP host):

{
  "mcpServers": {
    "taskfleet": {
      "command": "npx",
      "args": ["-y", "taskfleet-mcp"],
      "env": {
        "BUYER_WALLET_PRIVATE_KEY": "0xYOUR_WALLET_KEY"
      }
    }
  }
}
  • With BUYER_WALLET_PRIVATE_KEY (an EVM key holding a little USDC on Base): tool calls auto-pay via x402 and return results.
  • Without it: tools still list (discovery works) and a call returns the x402 payment instructions, so an x402-capable client can pay itself.
  • TASKFLEET_URL overrides the target (defaults to https://taskfleet.net).

The wallet key stays on the operator's machine — it never reaches TaskFleet, which only ever sees the on-chain payment.

Tools

One tool per TaskFleet service, named taskfleet_<service> (e.g. taskfleet_search, taskfleet_scrape, taskfleet_wallet_intel). Each tool's input schema and price come straight from the fleet manifest.

Publish it (as the fleet operator — discovery)

cd mcp
npm install
npm publish            # publishes taskfleet-mcp to npm

Once on npm it's installable via npx taskfleet-mcp and can be listed in MCP registries (the public MCP Registry, Smithery, PulseMCP, etc.) — each listing is another place agents discover TaskFleet. Submitting to those registries is free and generally just points at the npm package or this repo.

Local test

npm install
TASKFLEET_URL=https://taskfleet.net node index.mjs
# should print: taskfleet-mcp v0.1.0: 14 tools from https://taskfleet.net (payment: caller-pays)

Reviews

No reviews yet

Be the first to review this server!