Pay-per-call MCP tools: web search, scraping, on-chain wallet intel, extraction. x402 USDC on Base.
MCPpedia last refreshed this data
io.github.BFAI-1/taskfleet-mcp is an MCP server that pay-per-call MCP tools: web search, scraping, on-chain wallet intel, extraction. x402 USDC on Base. Its tool list has not been published yet over stdio, requires no API key, and scores 84/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"taskfleet": {
"env": {
"BUYER_WALLET_PRIVATE_KEY": "0xYOUR_WALLET_KEY"
},
"args": [
"-y",
"taskfleet-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'taskfleet-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked taskfleet-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in search / finance
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
The official MCP server implementation for the Perplexity API Platform
Production ready MCP server with real-time search, extract, map & crawl.
A Model Context Protocol server for searching and analyzing arXiv papers
MCP Security Weekly
Get CVE alerts and security updates for io.github.BFAI-1/taskfleet-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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.
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"
}
}
}
}
BUYER_WALLET_PRIVATE_KEY (an EVM key holding a little USDC on Base):
tool calls auto-pay via x402 and return results.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.
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.
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.
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)