Taskfleet Mcp

io.github.BFAI-1Published by GitHub account BFAI-1v0.1.1Updated Oct 11, 2026

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

VerifiedSTDIODesktop onlyWeb Search & ScrapingFinanceAI & ML

Overview

AI-generated overview

Exposes TaskFleet's pay-per-call AI task APIs as MCP tools for web search, scraping, extraction, translation, code review, summarization, and wallet…

What you can do
The server loads TaskFleet's service manifest live and exposes one tool per service, named taskfleet_ , such as taskfleet_search, taskfleet_scrape, and taskfleet_wallet_intel. Each tool's input schema and price come from that manifest, so new services appear automatically. Calls are paid per use through the x402 protocol in USDC on Base.
When to use it
Use it when an MCP-capable agent should be able to discover and call TaskFleet's paid task APIs directly, including web search, scraping, structured extraction, translation, code review, summarization, and on-chain wallet intelligence. It suits operators who want per-call payment rather than accounts or API keys.
Requirements
Runs locally over stdio, typically via npx taskfleet-mcp, so Node.js is needed. Network access to TaskFleet is required; TASKFLEET_URL optionally overrides the default base URL. BUYER_WALLET_PRIVATE_KEY is optional: with an EVM key holding USDC on Base, calls auto-pay; without it, tools list but calls return x402 payment instructions for the client to settle.
Before you install
BUYER_WALLET_PRIVATE_KEY is a private key controlling funds; anyone who obtains it can spend the wallet's assets, so use a dedicated key holding only a small USDC balance on Base. Tool calls spend real USDC per use. The key is described as staying on the operator's machine, but the server does send requests to TaskFleet, and TASKFLEET_URL can redirect them elsewhere.

Installation

In SourceWeft

  1. Open Taskfleet Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.