# QuantWorlds (remote · api.quantworlds.com)

Option, backtest, portfolio, and pairs checks for agents.

- Trust score: 62/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.quantworlds.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api.md), [page](https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api)
- remote · `api.quantworlds.com`: 56/100, [markdown](https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api-2.md), [page](https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api-2)

## Channel facts

- Endpoint: `https://api.quantworlds.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 527 tokens (~131/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

QuantWorlds is a hosted endpoint at https://api.quantworlds.com/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 com-quantworlds-api-quantworlds 'https://api.quantworlds.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-quantworlds-api-quantworlds": {
      "url": "https://api.quantworlds.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-quantworlds-api-quantworlds": {
      "type": "http",
      "url": "https://api.quantworlds.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-quantworlds-api-quantworlds]
url = "https://api.quantworlds.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-quantworlds-api-quantworlds": {
      "type": "remote",
      "url": "https://api.quantworlds.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-quantworlds-api-quantworlds --url 'https://api.quantworlds.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-quantworlds-api-quantworlds:
    url: "https://api.quantworlds.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-quantworlds-api-quantworlds": {
      "Transport": "http",
      "Url": "https://api.quantworlds.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-quantworlds-api-quantworlds -t streamable-http -u 'https://api.quantworlds.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-quantworlds-api-quantworlds": {
      "type": "http",
      "url": "https://api.quantworlds.com/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-11-20 (score 62, +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-11-18 (score 61, +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-11-16 (score 60, +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-11-15 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 59)

First indexed and scored.

## MCP tools (4)

### `options_surface_pricer` (~157 tokens)

Use this instead of estimating Greeks or adding a handmade American premium. European prices are Black-Scholes. American puts, and calls with dividends, use a 128-step binomial tree plus a European control variate. A zero-dividend American call matches the European call. The call surface is checked for arbitrage. Supply spot, strikes, and implied volatilities. Not investment advice.

Input parameters:

- `dividend_yield` (number, required)
- `is_american` (boolean)
- `iv_array` (array, required)
- `option_type` (string)
- `risk_free_rate` (number, required)
- `spot` (number, required)
- `strikes` (array, required)
- `time_to_expiry_years` (number, required)

### `instant_signal_backtest` (~133 tokens)

Verify a signal before recommending it. The signal earns the next bar only, so same-bar prices are not treated as tradable. Slippage is one square-root impact from depth and size, not a live order book. Returns Sharpe, Sortino, drawdown, and an approximate deflated Sharpe. Not investment advice.

Input parameters:

- `fee_bps` (number)
- `order_book_depth_usd` (number)
- `prices` (array, required)
- `raw_signals` (array, required)
- `trade_size_usd` (number)
- `trials_tested_by_agent` (integer)

### `portfolio_stress_verifier` (~137 tokens)

Run this before suggesting a rebalance. Normal VaR understates the tail: the report also returns a Student-t copula CVaR and Euler risk contributions. Crisis shocks repair the correlation matrix before applying the shock. Supply weights, vols, betas, and a correlation matrix. Not a historical path replay and not investment advice.

Input parameters:

- `asset_betas` (array, required)
- `asset_vols_annual` (array, required)
- `confidence_level` (number)
- `correlation_matrix` (array, required)
- `current_weights` (array, required)
- `proposed_weights` (array, required)
- `scenario` (string)

### `microstructure_coint_test` (~100 tokens)

Use this for a two-asset pairs check instead of eyeballing a hedge ratio. Returns an Engle-Granger Dickey-Fuller p-value, OLS and Kalman hedge ratios, half-life, and z-score. Two series only. Not a Johansen test and not investment advice.

Input parameters:

- `ask_volumes`
- `bid_volumes`
- `series_x` (array, required)
- `series_y` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api#diagnostics

## Score history

- 2026-11-21: 62
- 2026-11-20: 62
- 2026-11-19: 61
- 2026-11-18: 61
- 2026-11-17: 60
- 2026-11-16: 60
- 2026-11-15: 59
- 2026-11-14: 59

## Common questions

### What is the QuantWorlds MCP server?

QuantWorlds is an MCP server listed in the public MCP registry as com.quantworlds.api/quantworlds. Option, backtest, portfolio, and pairs checks for agents. This page covers its hosted endpoint (https://api.quantworlds.com/mcp).

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

QuantWorlds scores 62 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 QuantWorlds MCP server expose?

QuantWorlds exposes 4 tools: options_surface_pricer, instant_signal_backtest, portfolio_stress_verifier, microstructure_coint_test. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.

### Does the QuantWorlds MCP server require authentication?

No. We connected to QuantWorlds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the QuantWorlds MCP server still maintained?

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

### What did VerifyMCP test on the QuantWorlds MCP server?

VerifyMCP ran 12 checks on QuantWorlds, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about QuantWorlds: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.quantworlds.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api.json
- HTML version of this page: https://verifymcp.io/servers/com-quantworlds-api-quantworlds/api
