Model Context Protocol endpoint using the Streamable HTTP transport (successor to the legacy SSE+companion-POST pattern). A single URL handles both GET (optional server→client event stream) and POST (client→server JSON-RPC 2.0 messages).

Discovery: The MCP server manifest is published at https://riskmodels.app/.well-known/mcp.json for automated client discovery.

Connection:

• Transport: Streamable HTTP (stateless mode)

• Authentication: Authorization: Bearer <key> (preferred) or ?api_key=<key> query param (for EventSource, which can't set custom headers).

• Tool-call billing: charged per-invocation on the underlying REST endpoint (e.g. riskmodels_get_stock_snapshot bills the same as GET /metrics/{ticker}).

• POST requests: send Accept: application/json, text/event-stream (required by some MCP clients; omitting it can yield 406 Not Acceptable).

Usage — mcp-remote proxy:

{
  "mcpServers": {
    "riskmodels": {
      "command": "npx",
      "args": ["mcp-remote", "https://riskmodels.app/api/mcp/sse"],
      "env": { "AUTHORIZATION": "Bearer rm_agent_live_..." }
    }
  }
}