Skip to main content
The Vol Radar API is also an MCP server (Model Context Protocol), so Claude and other MCP clients can use the Radar directly: ask “what is unusual in gas vol today, and what followed similar moves before?” and the client calls the tools below. The tools return the same data and the same numbers as the REST API, from the same daily run.
Vol Radar describes what options markets are pricing and what happened after similar days in the past. It is descriptive, never a forecast, and nothing in it is investment advice. Structures and their statistics show ways to express your own view, with placeholder costs.

Connect

The MCP endpoint is
It uses streamable HTTP and the same API key as the REST API, sent as Authorization: Key <your-key>. Create the key on allasso.app: your profile, then API Keys.
1

Add the server to Claude Code

2

Check it

Run claude mcp list: vol-radar should show as connected.
3

Ask

For example: “Give me today’s Vol Radar overview for TTF”, “Explain the latest notable Brent signal: what followed earlier cases?”, or “Plot EUA 30-day ATM vol since 2024”.
Other MCP clients that support streamable HTTP with a custom header connect the same way. Clients that connect only through a sign-in flow (OAuth) are not supported yet.

Tools

Markets can be given by id (COM.TTF.ICE), short name (TTF) or name (TTF gas). An unknown signal, market or metric returns a tool error with the API’s own message.

What the client is told

The server gives every client the same instructions: the data is descriptive statistics of past markets, never to be presented as a forecast, a probability or advice; sample sizes must be quoted; vols are decimals (0.604 = 60.4%), vol changes are decimals of vol points (−0.03 = −3 vol points), returns are log returns, and structure P&L is a fraction of the futures price on model prices.
Last modified on November 4, 2026