Apollo Proxy
Wire one MCP proxy so your coding agent can call DeFi, OSINT, crypto intel, search, and proxy tools with optional x402 micropayments instead of juggling separate APIs.
Overview
Apollo Proxy is an MCP server for the Build phase that exposes 26 DeFi, OSINT, crypto, search, and proxy tools to coding agents through one npm stdio integration with optional x402 micropayments.
What is this MCP server?
- Exposes 26 AI-oriented tools spanning DeFi, OSINT, crypto, intel feeds, search, and proxy in one MCP server
- Published as @apollo_ai/mcp-proxy 4.6.0 with stdio transport via npm
- Supports x402 micropayments for pay-per-use tool access from agents
- Central proxy pattern reduces one-off API wrappers in Claude Code, Cursor, or Codex configs
- Server version 4.6.0
- 26 AI tools described in catalog metadata
- npm package identifier @apollo_ai/mcp-proxy with stdio transport
What problem does it solve?
Indie builders waste time wiring many separate APIs and MCP servers when their agent only needs a consistent way to query markets, intel, and the open web.
Who is it for?
Solo builders prototyping agent products that need mixed research, crypto, and web proxy tools without building each connector by hand.
Skip if: Teams that only need a single REST API, cannot run npm stdio MCP, or want a curated marketplace without DeFi, OSINT, or micropayment complexity.
What do I get? / Deliverables
After you register @apollo_ai/mcp-proxy, your agent can call a unified tool surface from Claude Code or Cursor instead of maintaining a fragile pile of one-off integrations.
- One registered MCP server exposing up to 26 bundled AI tools to your agent
- Stdio-based agent sessions that can invoke search, intel, crypto, and proxy operations without custom wrappers
Recommended MCP Servers
Journey fit
Solo builders add this during the build phase when the product or agent workflow needs live external data and tool calls through the Model Context Protocol. It sits on integrations because it is a stdio npm MCP package that aggregates many third-party capabilities behind a single agent connection.
How it compares
MCP tool-bundle proxy, not a journey-wide planning skill or a hosted no-code integration.
Common Questions / FAQ
Who is apollo-proxy for?
It is for indie developers and agent builders who want one MCP entry point for DeFi, OSINT, crypto intel, search, and proxy tools instead of many separate servers.
When should I use apollo-proxy?
Use it during build when your agent workflow needs live external data and you are already standardizing on MCP with npm stdio in Claude Code, Cursor, or Codex.
How do I add apollo-proxy to my agent?
Install the npm package @apollo_ai/mcp-proxy at version 4.6.0, configure stdio transport in your MCP client, and follow the repository docs for x402 and tool enablement.