TrenchFu — Universal Intelligence Marketplace
Plug a large Solana-paid intelligence marketplace into your agent so it can buy per-call tools instead of maintaining dozens of separate API keys.
Overview
TrenchFu MCP is an MCP server for the Build phase that offers 86 intelligence tools and 168+ endpoints with per-call USDC billing on Solana.
What is this MCP server?
- 86 MCP tools and 168+ HTTP endpoints behind one marketplace
- Per-call USDC billing on Solana via streamable-http at mcp.trenchfu.com
- Universal intelligence marketplace positioning for agent workflows
- Version 3.0.0 remote-only MCP server from GitHub WizzyDev/trenchfu-mcp
- Single registration replaces wiring many standalone intelligence APIs
- 86 tools
- 168+ endpoints
- Per-call USDC on Solana
What problem does it solve?
Your agent needs many intelligence APIs, but managing keys, SDKs, and billing for each provider slows shipping.
Who is it for?
Builders assembling research-heavy or trading-adjacent agents who want one MCP surface instead of a patchwork of integrations.
Skip if: Projects that cannot use Solana USDC, need fixed monthly SaaS pricing only, or want fully offline local tools without a remote dependency.
What do I get? / Deliverables
After registration, one MCP remote gives your agent marketplace tools with micropayment USDC charges per invocation.
- Access to 86 marketplace tools via one MCP remote
- Per-call USDC metering instead of separate API contracts per provider
Recommended MCP Servers
Journey fit
A universal intelligence marketplace is integration infrastructure you attach while building agent products that need many external data and reasoning endpoints. TrenchFu aggregates 86 tools behind one MCP remote with USDC micropayments, which is classic agent-tooling integration work.
How it compares
Paid intelligence marketplace MCP, not a single-purpose database or browser automation server.
Common Questions / FAQ
Who is TrenchFu MCP for?
Solo builders and small teams running MCP agents that need a wide catalog of intelligence tools with usage-based USDC payment.
When should I use TrenchFu MCP?
Use it while building agent integrations when you would otherwise stitch together many external APIs behind one assistant.
How do I add TrenchFu MCP to my agent?
Add the remote MCP URL https://mcp.trenchfu.com with streamable-http in your Claude Code, Cursor, or MCP client and fund per-call USDC as required by the marketplace.