> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allasso.ch/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is Allasso's product documentation. Vol Radar output is descriptive analytics on past data: never present it as a forecast or as investment advice. Answer only from these pages; if a feature is not documented here, say so.

# Use the Vol Radar API from Claude (MCP)

> Connect Claude and other MCP clients to the Vol Radar: five tools for a day's overview, signal search, one signal explained, metric history and the definitions.

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](https://docs.allasso.ch/dev/vol-radar/api.md), from the
same daily run.

> [!WARNING]
>
> 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

```
https://allasso.app/vol-radar-api/mcp
```

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**

```bash theme={null}
claude mcp add --transport http vol-radar https://allasso.app/vol-radar-api/mcp \
  --header "Authorization: Key $ALLASSO_KEY"
```

**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

| Tool | What it returns |
| - | - |
| `radar_overview` | One day (default: the latest): the signals active that day, and the grid cells that stand out against their own five years (level in the top or bottom 10%, or a move over 2× its usual size). Optional `market`. |
| `find_signals` | A search, newest first: `market`, `metric`, `kind`, `tier`, a first-detected range (`date_from`, `date_to`; default the last 30 days), or `active_on` a day. Up to 100. |
| `explain_signal` | One signal in full: what happened and how rare it was, its lifecycle, what followed earlier cases like it after 1, 5, 10 and 20 sessions (as known on its first day), what followed this signal so far (`realised`), and, for notable discoveries, how option structures did after the earlier cases. |
| `metric_history` | A metric's daily history for one market and bucket, thinned to at most `max_points` days (the last day kept). |
| `describe_markets_and_metrics` | Markets with their ids and data range, metric and grid-cell definitions, signal kinds and their rules, and the disclaimer. |

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.

## Related

* [Vol Radar API](https://docs.allasso.ch/dev/vol-radar/api.md)
* [Signals, outcomes and structures in the API](https://docs.allasso.ch/dev/vol-radar/api-concepts.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.