MCP
What is Apogee MCP?
Model Context Protocol is an open standard. Apogee implements a Streamable HTTP server that exposes Robinhood Chain tools to compatible hosts.
MCP (the protocol)
Model Context Protocol lets AI applications connect to external tools, data, and capabilities. MCP servers expose tools, resources, and (optionally) prompts that compatible hosts can use. MCP itself is a technical protocol. Legal and regulatory obligations depend on the product, the data, the jurisdictions, and how the service is operated — not on the fact that MCP is used.
Apogee (this implementation)
Server name apogee, version 2.0.0. Protocol 2025-03-26. Transport streamable-http. Auth none. The AI model does not magically know Apogee data; it only sees results after the host calls a tool.
- AI application
- MCP client (Cursor, Claude, VS Code, custom)
- Apogee MCP server · POST /api/mcp
- Listed tools + 3000 catalog aliases
- RPC · DexScreener · Gecko · RHJ · pons factories
- Structured JSON result
- AI application
Transport
POST JSON-RPC to https://apogeemcp.digital/api/mcp. GET returns a discovery document. Notifications return HTTP 202. vercel.json rewrites /mcp to /api/mcp. There is no stdio server in this repository and no legacy HTTP+SSE subscribe transport. Do not configure sse as the transport for Apogee.
Methods actually implemented
- initialize — protocolVersion 2025-03-26, capabilities.tools, serverInfo apogee@2.0.0, instructions
- ping — empty object
- tools/list — listed tools (58) with name, description, inputSchema
- tools/call — content[] text JSON + structuredContent; isError on thrown failures
- resources/list — apogee://docs/usage, apogee://mcp
- resources/read — markdown usage or canonical MCP URL
This server advertises protocol 2025-03-26. It does not claim later MCP spec revisions until the code is upgraded.