
Toolfi
io.github.Tsubaki414Published by GitHub account Tsubaki414v1.2.0Updated Oct 28, 2026
Open API Marketplace for AI Agents. Crypto data tools with USDC payments on Base.
Overview
ToolFi is a pay-per-call crypto data API marketplace for AI agents, offering price, security, DeFi and news tools paid in USDC on Base.
- What you can do
- Fetch real-time token prices and trending coins
- Scan tokens for rug-pull risk and analyze wallet address risk
- Find cross-chain bridge routes and aggregate DEX swap routes
- Look up DeFi yields and protocol TVL figures
- Check gas prices on EVM chains and read crypto news digests
- Each call is metered: the server returns a payment request, the agent pays in USDC on-chain and retries with a payment transaction header
- When to use it
- Useful when an assistant needs live crypto market, DeFi or token-safety data and you are willing to let it pay small per-call fees in USDC on Base rather than manage API keys for each provider.
- Requirements
- A remote endpoint; no account or API key is declared. Calls require an on-chain USDC payment on Base (the README references Base Sepolia) and a wallet able to approve and send payments, plus a payment transaction header on retry. The README also documents a local Python MCP server install as an alternative.
Installation
In SourceWeft
- Open Toolfi in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Tsubaki414%2Ftoolfi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"toolfi": {
"type": "http",
"url": "https://web-ten-alpha-81.vercel.app/api/mcp"
}
}
}README
ToolFi — API Marketplace for AI Agents
"The next unicorn is an API marketplace for agents... where the right API should be selected by Claude and connected automatically" — @auralix4
API marketplaces exist, but they're built for human developers. ToolFi is built for AI workflows — agents discover, select, and pay for APIs automatically, without human intervention.
🌐 Website · 📡 API · 📜 Contract · 🗺️ Roadmap
The Problem
AI agents need external data (prices, security checks, routes). Current solutions:
- RapidAPI, etc. — Built for humans. Agents can't browse and click "Subscribe"
- Hardcoded keys — Security risk, doesn't scale
- Manual integration — Every new tool needs human setup
The Solution
ToolFi = APIs that agents can discover and use autonomously.
- Discovery — Agents find tools via
.well-known/mcp.json, MCP registries, semantic search - Selection — Rich descriptions help agents pick the right tool
- Payment — USDC on Base, no API keys, just pay and use
- Data — Structured responses optimized for LLM consumption
How It Works
Available Tools
Integration Options
Option 1: HTTP API (Any Agent)
Option 2: MCP Server (Claude Desktop)
Add to Claude Desktop config:
Then ask Claude: "Check the security of token 0x... on Base"
For Tool Creators
Publish your API and earn USDC:
Price in 6 decimals: 10000 = $0.01/call
Withdraw earnings:
Contract
Project Structure
Development
Roadmap
- Core registry contract
- Web API with 10 tools
- MCP Server for Claude Desktop
- Mainnet deployment
- Creator dashboard
- Agent SDK (Python/TypeScript)
- Idempotency keys
- Usage analytics
License
MIT
Source: README.md at commit de7f7d4
Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
75% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.