# Stratify (remote · stratify-mcp.aeon-labs.site)

Backtest NIFTY option strategies on real 1-minute data, with an honest out-of-sample panel.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `stratify-mcp.aeon-labs.site`: 83/100 (this document), [markdown](https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp.md), [page](https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp)
- npm · `stratify-mcp`: 35/100, [markdown](https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp-2.md), [page](https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp-2)

## Channel facts

- Endpoint: `https://stratify-mcp.aeon-labs.site/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2921 tokens (~108/item across 27 items; 10 tools + 17 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Stratify MCP server?

Stratify is a hosted endpoint at https://stratify-mcp.aeon-labs.site/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http site-aeon-labs-stratify 'https://stratify-mcp.aeon-labs.site/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "site-aeon-labs-stratify": {
      "url": "https://stratify-mcp.aeon-labs.site/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-aeon-labs-stratify": {
      "type": "http",
      "url": "https://stratify-mcp.aeon-labs.site/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.site-aeon-labs-stratify]
url = "https://stratify-mcp.aeon-labs.site/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-aeon-labs-stratify": {
      "type": "remote",
      "url": "https://stratify-mcp.aeon-labs.site/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-aeon-labs-stratify --url 'https://stratify-mcp.aeon-labs.site/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-aeon-labs-stratify:
    url: "https://stratify-mcp.aeon-labs.site/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "site-aeon-labs-stratify": {
      "Transport": "http",
      "Url": "https://stratify-mcp.aeon-labs.site/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-aeon-labs-stratify -t streamable-http -u 'https://stratify-mcp.aeon-labs.site/mcp'
```

### Other

```json
{
  "mcpServers": {
    "site-aeon-labs-stratify": {
      "type": "http",
      "url": "https://stratify-mcp.aeon-labs.site/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 80, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 80)

First indexed and scored.

## MCP tools (10)

### `run_backtest` (~327 tokens)

Backtest an Indian index option strategy on real 1-minute NIFTY options data. Returns P&L after real charges and slippage, return-on-margin, and an honesty panel: out-of-sample split, walk-forward folds, bootstrap interval, and a deflated Sharpe that accounts for how many variants you have already tried. Refuses windows too narrow to be meaningful, and reports no ratios below 30 trades. Two spec forms: a PRESET (structure + params) for the common shapes, or an OPEN STRATEGY (legs + rules) for anything else — any number of legs at any strikes on any expiry, strikes chosen by percent, points, premium or delta, entry at any minute, and rules that CHANGE the position while it is live (roll a tested leg, close one side, add a hedge, trail a stop) plus book-level rules like standing down after three losers. Nothing here is restricted by tier; a paid tier only widens the date window.

Input parameters:

- `detail` (string): How much per-trade data to return. 'standard' (default) is the equity curve, breakdowns and the first 25 trades with their leg prices. 'full' returns up to 300 trades — ask for it when the caller wan…
- `lots` (integer)
- `spec` (required): Either a preset spec (structure + params) or an open strategy (legs + rules). Use the open form for anything the presets cannot say.

### `describe_coverage` (~43 tokens)

What data is available: symbols, date range, resolution, structures, gates, biases, the cost model, and every known gap. Call this before building a spec.

### `explain_methodology` (~61 tokens)

How a result is produced and how to judge it: entry pricing, settlement, margin, slippage, the honesty rubric, and what each check can and cannot prove. Read this before trusting any backtest, including ours.

Input parameters:

- `topic` (string)

### `get_backtest` (~51 tokens)

Retrieve a previous backtest result by its id — honesty panel, equity curve and per-trade detail, exactly as first computed.

Input parameters:

- `backtest_id` (string, required)
- `detail` (string)

### `list_strategies` (~122 tokens)

Strategies from THIS account's history that held up under out-of-sample and walk-forward checks, not merely ones that made money. Ranked by worst walk-forward fold — consistency, not size. Call it to answer 'what has worked for me so far?' without re-running anything.

Input parameters:

- `limit` (integer)
- `order` (string): 'consistency' (default) sorts by worst walk-forward fold, then median fold. 'pnl' sorts by total P&L and is the ranking most likely to put an overfit at the top.

### `search` (~36 tokens)

Search what this service covers — symbols, dates, structures, signals, methodology. Returns ids usable with fetch.

Input parameters:

- `query` (string, required)

### `fetch` (~29 tokens)

Fetch a document or backtest result by id, as returned by search.

Input parameters:

- `id` (string, required)

### `submit_feedback` (~191 tokens)

Report a bug, request a feature, flag a data gap, or say what worked. Use this whenever the user expresses a problem with this service or wishes it did something it does not — do not just apologise to them, file it. If a backtest was involved, pass its backtest_id: that attaches the exact spec and the recent call trail so the issue can be reproduced without a reply. Tell the user you filed it and give them the returned id.

Input parameters:

- `backtest_id` (string): The result this is about, if any.
- `body` (string, required): What was expected, what happened, and any spec involved. Write it from the user's report, not from your own summary of it.
- `category` (string): Omit it and it will be inferred from the text.
- `severity` (string)
- `title` (string, required): One line naming the problem or request.

### `build_report` (~483 tokens)

Turn a stored backtest into a finished, self-contained Stratify report — one HTML document with the honesty panel, equity and drawdown curves, walk-forward folds, the gross-to-net breakdown, a month grid and the trade table. PUBLISH THE RETURNED HTML VERBATIM AS AN ARTIFACT (Claude), a canvas document (ChatGPT, Gemini), or write it to a .html file (CLI clients). Do not rewrite it, summarise it into your own chart code, or regenerate the figures — the numbers in it came from the backtest, and anything you redraw from a table is a second source that can disagree with the first. It needs no network, no libraries and no build step, and it renders on light and dark. Use it when someone asks for a report, a summary they can keep, something to share, or an artifact.

Input parameters:

- `backtest_id` (string, required): From a previous run_backtest.
- `capital` (integer): format 'full' only. Starting capital in rupees. It sets the report's OPENING view — the reader can change it in the page without a new report. Default 1,000,000.
- `deploy_pct` (number): format 'full' only. Percent of capital used as margin on any one trade. Default 10.
- `format` (string): 'artifact' (default) returns the whole document to publish. 'link' returns only the hosted URL — far cheaper in tokens, and the right choice when the user just wants to look at it rather than keep it…
- `risk_pct` (number): format 'full' only. Size by RISK instead of margin: the percent of capital the trade is allowed to lose in its worst case (2 means 'risk 2% per trade'). Only works where the position has a bounded wo…

### `my_feedback` (~35 tokens)

Reports this account has filed, and where each one stands. Use it to answer 'did that bug I reported ever get fixed?'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp#diagnostics

## Score history

- 2026-09-22: 83
- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80

## Common questions

### What is the Stratify MCP server?

Stratify is an MCP server listed in the public MCP registry as site.aeon-labs/stratify. Backtest NIFTY option strategies on real 1-minute data, with an honest out-of-sample panel. This page covers its hosted endpoint (https://stratify-mcp.aeon-labs.site/mcp).

### Is the Stratify MCP server safe to use?

Stratify scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Stratify MCP server expose?

Stratify exposes 10 tools: run_backtest, describe_coverage, explain_methodology, get_backtest, list_strategies, and 5 more. Their descriptions and schemas cost roughly 1,378 tokens of context every time the server is loaded.

### Does the Stratify MCP server require authentication?

Yes. Stratify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Stratify MCP server still maintained?

Stratify is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://stratify-mcp.aeon-labs.site/mcp
- Website: https://stratify.aeon-labs.site/
- Changelog RSS feed: https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-aeon-labs-stratify/stratify-mcp