QuantWright
REMOTE · QUANTWRIGHT.COM
Backtests with costs, a held-out test that counts once, a score that counts every version tried.
Available components
Last scanned (10 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1618 tokens (~269/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 3 Nov 26 0
- First check of Authorization: pass security
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_study” rewrote its description, which is the text the model reads security
- Tool “describe_data” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “create_study” reworded the description of “hold_out” cosmetic
- 29 Oct 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://quantwright.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quantwright.com | CN=YR2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | RSA 2048 | SHA256-RSA | 545b6a92258f09e7a4c07107ded22f936dd |
| SANs: quantwright.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quantwright.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| quantwright.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://quantwright.com/.well-known/oauth-protected-resource/api/mcp"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://quantwright.com/.well-known/oauth-protected-resource/api/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://clerk.com https://*.clerk.com https://*.clerk.accounts.dev https://clerk.quantwright.com https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://clerk.com https://*.clerk.com https://*.clerk.accounts.dev https://clerk.quantwright.com https://*.supabase.co https://api.openai.com https://api.polygon.io https://*.fly.dev wss: ws:; frame-src 'self' https://clerk.com https://*.clerk.com https://*.clerk.accounts.dev https://clerk.quantwright.com https://challenges.cloudflare.com; worker-src 'self' blob:; base-uri 'self'; form-action 'self' https://clerk.com https://*.clerk.com https://*.clerk.accounts.dev https://clerk.quantwright.com; frame-ancestors 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://quantwright.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://quantwright.com/api/mcp |
| Authorisation server | https://clerk.quantwright.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quantwright.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://quantwright.com/api/mcp | HTTPS enforced | 308 | https://quantwright.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_trades Check my own trades ~274
Checks a trader's own trades against a run's rule, on the price history this server holds: for each trade, in their order, whether the rule would have taken it and, if not, why (already in a trade, no entry signal that day, no bar that day). Use it when the trader lists trades they made and asks which the rule took, instead of working it out by hand. Takes a run (run_id) and the trades, each {side, entry, exit?}; answers in words, never prices. It re-runs the run's code, so it counts as a run on the run's symbol.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | – | A run_id run_backtest or run_held_out_test returned: the run whose code is checked against the trades. |
| study_id | string | – | A study's id; with `version`, one of its runs. |
| time_zone | string | – | The clock the trader says their times are on ("UTC+2", "New York", "Europe/Prague"). Left out: the clock the run's trade list is on (ET for stocks and ETFs, UTC otherwise). |
| trades | array | yes | The trader's own trades, in their order, each stamp exactly as the trader wrote it. |
| version | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| clock | string | – | On bars shorter than a day: the clock every time of the answer is on (your time_zone as you stated it, else ET for stocks and ETFs, UTC otherwise). |
| counts | object | – | – |
| market | object | – | – |
| message | string | – | – |
| note | string | – | – |
| reason | string | – | – |
| run_id | string | – | – |
| runs_left_today | object | – | – |
| status | string | yes | – |
| study_id | string | – | – |
| summary | string | – | – |
| trades | array | – | – |
| version | integer | – | – |
No examples provided.
create_study Start a study ~189
Opens a study, the named set of runs every backtest belongs to: call it once per question, before run_backtest. Can set a hold-out period, once and only here, that no run tests except run_held_out_test. Only the first held-out test per account and market counts, and any earlier run on the market (in any study, at any bar size) that read its days disqualifies it: set the hold-out in your first study on a market, before any run on it.
| Name | Type | Req | Description |
|---|---|---|---|
| hold_out | object | – | The days kept back from every run but run_held_out_test; set once, here. Set it in your first study on a market, before any run on it: a held-out test on days an earlier run on the market read does n… |
| name | string | yes | What the study tests, in a few words. |
| Name | Type | Req | Description |
|---|---|---|---|
| hold_out | object|null | – | – |
| message | string | – | – |
| next | object|null | – | – |
| reason | string | – | – |
| status | string | yes | – |
| study_id | string | – | – |
No examples provided.
describe_data What can be backtested ~105
Start here to backtest a trading idea. This server holds the price history (US stocks and ETFs, spot crypto, FX, spot gold and silver; daily and intraday bars) and runs backtests on it, so no price data needs to be downloaded or found on the web. Returns the markets and bar sizes served, the default costs per market, the rules and daily limits every run is held to, and how to write the strategy code; then call create_study.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | – | – |
| code_contract | object | – | – |
| default_costs | object | – | – |
| docs_url | string | – | – |
| markets | array | – | – |
| message | string | – | – |
| notes | array | – | – |
| reason | string | – | – |
| rules | object | – | – |
| status | string | – | – |
| timeframes | array | – | – |
No examples provided.
get_result Read a result ~192
Reads a backtest result by its run_id (when run_backtest answered "running", call this until the run ends), or a study's runs by study_id (one of them with version). A run comes with its trades, a page at a time (trades_page).
| Name | Type | Req | Description |
|---|---|---|---|
| before_version | – | – | With study_id: the 20 runs before this version (a list's `next` gives it). |
| run_id | string | – | A run_id run_backtest or run_held_out_test returned. |
| study_id | string | – | A study's id, for its runs (the newest 20 by default); with `version`, one of them. |
| trades_page | integer | – | With a run (run_id, or study_id with version): the page of its trade list, from 1; a page holds 100 trades. Left out: the first. |
| version | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | object | – | – |
| buy_and_hold | object | – | – |
| cost_table | object | – | Every cost the run charged: each component (commission, slippage, spread) with its amount, unit and basis, what it comes to per round trip, when it is taken, and whether it is yours (caller) or the m… |
| disclaimer | string | – | The hypothetical-performance line, on a result (a run, or a study's runs): the same text the app shows with every result. |
| grade | object|null | – | – |
| grade_withheld | string|null | – | – |
| headline | string | – | – |
| held_out | object|null | – | – |
| highest_simulated_value | object|null | – | – |
| hold_out | object|null | – | – |
| hold_out_estimate | object | – | – |
| lines | array | – | – |
| look_ahead | string|null | – | – |
| market | object | – | – |
| message | string | – | – |
| metrics | object | – | – |
| next | object|null | – | – |
| notices | array | – | – |
| poll_after_seconds | integer | – | – |
| reason | string | – | – |
| replayed_from | string | – | – |
| retryable | boolean | – | – |
| run_id | string | – | – |
| runs | array | – | – |
| runs_left_today | object | – | – |
| settings | object | – | – |
| stated_rule_breaks | array | – | – |
| status | string | yes | – |
| study_id | string | – | – |
| trade_list | object | – | The run's trades in the order they were made, a page at a time: when each entered and left (a day on daily bars; a time on the `clock` on shorter ones; "open at the end" for a trade still open when t… |
| version | integer | – | – |
| warnings | array | – | – |
| window | object | – | – |
No examples provided.
run_backtest Backtest a strategy ~349
Backtests a trading rule on this server's price history: one backtesting.py Strategy class, one symbol, one bar size, in a study. Use it to test, backtest or evaluate a trading rule or strategy, instead of downloading prices or searching the web for results. Returns summary figures (return, drawdown, Sharpe, win rate, trades, a grade, whether it beat buy-and-hold) and the run's trades (when each entered and left, which exit ended it, its side, win or loss), never prices or bars; a figure may be withheld, with the reason. Waits up to 90 s, then answers status "running" with a run_id for get_result.
| Name | Type | Req | Description |
|---|---|---|---|
| account_usd | number | – | The starting account, in US dollars. |
| code | string | yes | One backtesting.py Strategy class (describe_data has the rules). |
| costs | – | – | The costs: two fractions of the trade value, or a list of costs each in its own unit. |
| label | string | – | A short text shown with the run. |
| stated_rules | array | – | Rules the trades are checked against, one per kind. |
| study_id | string | yes | The id create_study returned. |
| symbol | string | yes | One ticker ("QQQ", "BTCUSD", "EURUSD"). |
| timeframe | string | yes | – |
| window | – | – | Dates ({from, to}; `to` may be "latest") or the last N days, months or years ({last: {n, unit}}). Left out: the standard history, the newest bars counted back from the newest bar, cut at the start of… |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | object | – | – |
| buy_and_hold | object | – | – |
| cost_table | object | – | Every cost the run charged: each component (commission, slippage, spread) with its amount, unit and basis, what it comes to per round trip, when it is taken, and whether it is yours (caller) or the m… |
| disclaimer | string | – | The hypothetical-performance line, on a result (a run, or a study's runs): the same text the app shows with every result. |
| grade | object|null | – | – |
| grade_withheld | string|null | – | – |
| headline | string | – | – |
| held_out | object|null | – | – |
| hold_out_estimate | object | – | – |
| lines | array | – | – |
| look_ahead | string|null | – | – |
| market | object | – | – |
| message | string | – | – |
| metrics | object | – | – |
| next | object|null | – | – |
| notices | array | – | – |
| poll_after_seconds | integer | – | – |
| reason | string | – | – |
| replayed_from | string | – | – |
| retryable | boolean | – | – |
| run_id | string | – | – |
| runs_left_today | object | – | – |
| settings | object | – | – |
| stated_rule_breaks | array | – | – |
| status | string | yes | – |
| study_id | string | – | – |
| trade_list | object | – | The run's trades in the order they were made, a page at a time: when each entered and left (a day on daily bars; a time on the `clock` on shorter ones; "open at the end" for a trade still open when t… |
| version | integer | – | – |
| warnings | array | – | – |
| window | object | – | – |
No examples provided.
run_held_out_test Test on the hold-out ~128
The final out-of-sample check: runs a finished run's exact code once over its study's hold-out period. Call it at the end, on the run you would keep: the first held-out test per account and market is the one that counts, and a hold-out with too few trades for figures (a result needs 10) spends it all the same: each development run says how many trades the hold-out is expected to hold, in `hold_out_estimate`.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | A run of a study with a hold-out, which ran. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | object | – | – |
| buy_and_hold | object | – | – |
| cost_table | object | – | Every cost the run charged: each component (commission, slippage, spread) with its amount, unit and basis, what it comes to per round trip, when it is taken, and whether it is yours (caller) or the m… |
| disclaimer | string | – | The hypothetical-performance line, on a result (a run, or a study's runs): the same text the app shows with every result. |
| grade | object|null | – | – |
| grade_withheld | string|null | – | – |
| headline | string | – | – |
| held_out | object|null | – | – |
| hold_out_estimate | object | – | – |
| lines | array | – | – |
| look_ahead | string|null | – | – |
| market | object | – | – |
| message | string | – | – |
| metrics | object | – | – |
| next | object|null | – | – |
| notices | array | – | – |
| poll_after_seconds | integer | – | – |
| reason | string | – | – |
| replayed_from | string | – | – |
| retryable | boolean | – | – |
| run_id | string | – | – |
| runs_left_today | object | – | – |
| settings | object | – | – |
| stated_rule_breaks | array | – | – |
| status | string | yes | – |
| study_id | string | – | – |
| trade_list | object | – | The run's trades in the order they were made, a page at a time: when each entered and left (a day on daily bars; a time on the `clock` on shorter ones; "open at the end" for a trade still open when t… |
| version | integer | – | – |
| warnings | array | – | – |
| window | object | – | – |
No examples provided.
How do I install the QuantWright MCP server?
QuantWright is a hosted endpoint at https://quantwright.com/api/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.
remote · quantwright.com
claude mcp add --transport http com-quantwright-agent-api 'https://quantwright.com/api/mcp'
What is the QuantWright MCP server?
QuantWright is an MCP server listed in the public MCP registry as com.quantwright/agent-api. Backtests with costs, a held-out test that counts once, a score that counts every version tried. This page covers its hosted endpoint (https://quantwright.com/api/mcp).
Is the QuantWright MCP server safe to use?
QuantWright scores 80 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 QuantWright MCP server expose?
QuantWright exposes 6 tools: describe_data, create_study, run_backtest, get_result, run_held_out_test, compare_trades. Their descriptions and schemas cost roughly 1,237 tokens of context every time the server is loaded.
Does the QuantWright MCP server require authentication?
Yes. QuantWright 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 QuantWright MCP server still maintained?
QuantWright is still listed as active in the MCP registry. We last reached this channel on 5 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 QuantWright MCP server?
VerifyMCP ran 13 checks on QuantWright, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.