MCP transport (Streamable HTTP) — session teardown
The Model Context Protocol server, hoodgrow-mcp, as a stateless Streamable-HTTP endpoint — GET/POST/DELETE all route to the same handler. Requires a bearer token on every call (free or paid API key); unlike every other endpoint on this page, there is no x402 fallback here. Registers 8 read-only tools: get_catalog, get_token, get_corporate_actions, get_defi, get_holders, get_slippage, get_ohlc, get_base_tokens — each returning the same JSON shape as its REST counterpart above, wrapped as MCP tool content. One rate-limit check applies per HTTP request, not per individual tool call within a batched JSON-RPC request.
Responses
- 200
MCP JSON-RPC response.
- application/json
- application/json
Request Example for delete/api/mcp
curl https://www.hoodgrow.com/api/mcp \
--request DELETE \
--header 'Authorization: Bearer YOUR_SECRET_TOKEN'
No Body