Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

QuantWorlds

REMOTE · API.QUANTWORLDS.COM · 2 COMPONENTS

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

+3 this week 62 Trust /100

Last scanned (23 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • 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. 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

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 →

Changelog

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.

  • 20 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.

  • 18 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.

  • 16 Nov 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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 59

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.quantworlds.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.quantworlds.com CN=YE2,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 6d26a5d0f3725f4f26328a73e1e224b33ce
SANs: api.quantworlds.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.quantworlds.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
quantworlds.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.quantworlds.com/mcp Verified 200
http (plaintext) http://api.quantworlds.com/mcp HTTPS enforced 301 https://api.quantworlds.com/mcp
MCP tools · 4 exposed · ~527 tokens

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 →

Tool Tokens
instant_signal_backtest ~133

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.

NameTypeReqDescription
fee_bpsnumber––
order_book_depth_usdnumber––
pricesarrayyes–
raw_signalsarrayyes–
trade_size_usdnumber––
trials_tested_by_agentinteger––

No output schema declared.

No examples provided.

microstructure_coint_test ~100

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.

NameTypeReqDescription
ask_volumes–––
bid_volumes–––
series_xarrayyes–
series_yarrayyes–

No output schema declared.

No examples provided.

options_surface_pricer ~157

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.

NameTypeReqDescription
dividend_yieldnumberyes–
is_americanboolean––
iv_arrayarrayyes–
option_typestring––
risk_free_ratenumberyes–
spotnumberyes–
strikesarrayyes–
time_to_expiry_yearsnumberyes–

No output schema declared.

No examples provided.

portfolio_stress_verifier ~137

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.

NameTypeReqDescription
asset_betasarrayyes–
asset_vols_annualarrayyes–
confidence_levelnumber––
correlation_matrixarrayyes–
current_weightsarrayyes–
proposed_weightsarrayyes–
scenariostring––

No output schema declared.

No examples provided.

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.

remote · api.quantworlds.com

# add to Claude Code
claude mcp add --transport http com-quantworlds-api-quantworlds 'https://api.quantworlds.com/mcp'
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.