io.github.Tsubaki414/toolfi

Registre officiel Finance et paiements

Open API Marketplace for AI Agents. Crypto data tools with USDC payments on Base.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http toolfi 'https://web-ten-alpha-81.vercel.app/api/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "toolfi": {
            "type": "http",
            "url": "https://web-ten-alpha-81.vercel.app/api/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. ToolFi — API Marketplace for AI Agents
  2. The Problem
  3. The Solution
  4. How It Works
  5. Available Tools
  6. Integration Options
  7. For Tool Creators
  8. Contract
  9. Project Structure
  10. Development
  11. Roadmap
  12. License

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.

  1. Discovery — Agents find tools via .well-known/mcp.json, MCP registries, semantic search
  2. Selection — Rich descriptions help agents pick the right tool
  3. Payment — USDC on Base, no API keys, just pay and use
  4. Data — Structured responses optimized for LLM consumption

How It Works

Agent → GET /api/price?symbol=ETH
                ↓
Server → 402 Payment Required
         { toolId, price, paymentInstructions }
                ↓
Agent → USDC.approve() → Registry.payForCall(toolId)
                ↓
Agent → Retry with X-Payment-Tx header
                ↓
Server → Verify on-chain → Return data

Available Tools

ToolPriceWhat it does
Crypto Price Oracle0.001 USDCReal-time prices via DexScreener
Rug Pull Scanner0.003 USDCToken security via GoPlus
Bridge Router0.002 USDCCross-chain routes via Li.Fi
DeFi Yield Finder0.002 USDCBest yields via DefiLlama
Swap Router0.002 USDCDEX aggregation via Li.Fi
Trending Coins0.001 USDCWhat's hot via CoinGecko
Protocol TVL0.001 USDCDeFi TVL data via DefiLlama
Gas Tracker0.0005 USDCGas prices for EVM chains
Wallet Risk Scanner0.005 USDCAddress risk analysis
News Digest0.002 USDCCrypto news summary

Integration Options

Option 1: HTTP API (Any Agent)
# Pay on-chain, then call with payment proof
curl -H "X-Payment-Tx: 0x..." "https://toolfi.vercel.app/api/price?symbol=ETH"
Option 2: MCP Server (Claude Desktop)
cd mcp-server
uv venv && source .venv/bin/activate
uv pip install -e .

Add to Claude Desktop config:

{
  "mcpServers": {
    "toolfi": {
      "command": "/path/to/.venv/bin/python",
      "args": ["-m", "src.server"],
      "cwd": "/path/to/mcp-server"
    }
  }
}

Then ask Claude: "Check the security of token 0x... on Base"

For Tool Creators

Publish your API and earn USDC:

cast send $REGISTRY \
  "registerTool(string,string,string,uint256)" \
  "My Tool" "https://api.example.com" "Description" 10000 \
  --rpc-url https://sepolia.base.org --private-key $KEY

Price in 6 decimals: 10000 = $0.01/call

Withdraw earnings:

cast send $REGISTRY "withdraw()" --rpc-url https://sepolia.base.org

Contract

| | | |-|-| | Chain | Base Sepolia (84532) | | USDC | 0x036CbD53842c5426634e7929541eC2318f3dCF7e | | Registry | 0x3D6C600799C67b45061eCAbfD5bBF8ef57Dded88 |

Project Structure

toolfi/
├── api/           # Vercel serverless API
├── web/           # Next.js frontend
├── mcp-server/    # Python MCP server for Claude
├── src/           # Solidity contracts
├── skill/         # OpenClaw skill spec
└── script/        # Deployment scripts

Development

# Contracts
forge build
forge test -v

# API
cd api && npm install && npm start

# MCP Server
cd mcp-server && uv pip install -e . && python -m src.server

Roadmap

  • [x] Core registry contract
  • [x] Web API with 10 tools
  • [x] MCP Server for Claude Desktop
  • [ ] Mainnet deployment
  • [ ] Creator dashboard
  • [ ] Agent SDK (Python/TypeScript)
  • [ ] Idempotency keys
  • [ ] Usage analytics

License

MIT

Questions fréquentes

Qu'est-ce que io.github.Tsubaki414/toolfi ?

Open API Marketplace for AI Agents. Crypto data tools with USDC payments on Base.

Comment installer io.github.Tsubaki414/toolfi ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http toolfi 'https://web-ten-alpha-81.vercel.app/api/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.Tsubaki414/toolfi ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.Tsubaki414/toolfi est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.Tsubaki414/toolfi ?

Il est publié par Tsubaki414. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.