Concepts
Protocol and transport
A standard Model Context Protocol server over HTTPS. MCP SDKs and clients handle all of this for you; this page is for calling it by hand.
Connection
| Field | Meaning |
|---|---|
Endpoint | https://mcp.optimistfi.com/mcp |
Transport | Streamable HTTP: each JSON-RPC message is a POST to the endpoint |
Headers | Content-Type: application/json and Accept: application/json, text/event-stream |
Authentication | None |
Sessions | Not required: each request stands on its own, so tools/call works without a prior initialize |
Methods
| Field | Meaning |
|---|---|
initialize | Agrees the protocol version and returns the server's name, version and capabilities. |
tools/list | Every tool with its description and the JSON Schema of its arguments. |
tools/call | Runs one tool: params are the tool's name and its arguments. |
{"jsonrpc":"2.0","id":0,"method":"initialize","params":{
"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"my-app","version":"1.0.0"}}}Replies
The server answers as server-sent events. The JSON-RPC reply is the data line:
event: message
data: {"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"{ … }"}],"isError":false}}Versions
The server reports protocol version 2025-06-18 and its own version, now 1.30.0, in the initialize reply, and tools/list always describes the tools as they are now.