# QuantToGo Reason Index (remote · mcp.quanttogo.com)

QuantToGo Reason Index: every reason people buy or sell stocks, turned into an index.

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

## Components

- remote · `mcp.quanttogo.com`: 69/100, [markdown](https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2.md), [page](https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2)
- remote · `mcp.quanttogo.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2-sse.md), [page](https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2-sse)
- npm · `quanttogo-mcp`: 22/100, [markdown](https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/quanttogo-mcp.md), [page](https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/quanttogo-mcp)

## Channel facts

- Endpoint: `https://mcp.quanttogo.com/v2/sse`
- Transports: `sse`
- Auth: `none`
- Version: `1.1.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-05.

- **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 12 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**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1789 tokens (~149/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the QuantToGo Reason Index MCP server?

QuantToGo Reason Index is a hosted endpoint at https://mcp.quanttogo.com/v2/sse, 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-quanttogo-quanttogo-mcp 'https://mcp.quanttogo.com/v2/sse'
```

### Cursor

```json
{
  "mcpServers": {
    "com-quanttogo-quanttogo-mcp": {
      "url": "https://mcp.quanttogo.com/v2/sse"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-quanttogo-quanttogo-mcp": {
      "type": "http",
      "url": "https://mcp.quanttogo.com/v2/sse"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-quanttogo-quanttogo-mcp]
url = "https://mcp.quanttogo.com/v2/sse"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-quanttogo-quanttogo-mcp --url 'https://mcp.quanttogo.com/v2/sse' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-quanttogo-quanttogo-mcp:
    url: "https://mcp.quanttogo.com/v2/sse"
```

### Netclaw

```json
{
  "McpServers": {
    "com-quanttogo-quanttogo-mcp": {
      "Transport": "http",
      "Url": "https://mcp.quanttogo.com/v2/sse"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-quanttogo-quanttogo-mcp -t streamable-http -u 'https://mcp.quanttogo.com/v2/sse'
```

### Other

```json
{
  "mcpServers": {
    "com-quanttogo-quanttogo-mcp": {
      "type": "http",
      "url": "https://mcp.quanttogo.com/v2/sse"
    }
  }
}
```

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-05 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 62, +1)

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

### 2026-11-01 (score 61, +1)

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

### 2026-10-30 (score 60, +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-10-28 (score 59, +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-10-26 (score 58, +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-10-25 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 57)

First indexed and scored.

## MCP tools (12)

### `reason_index` (~206 tokens)

QuantToGo 理由指数：把买卖股票的理由做成指数（腰斩指数、放量新高指数、国家队增持指数……）。不给 q 时列出全部理由指数和今天各有多少只股票符合；给 q（短名、理由原话或其中几个字）时返回这一个指数的详情：今天符合的只数和它在过去一年里的位置、A 股和美股各自的点位、比上一个交易日涨跌、2015 年以来涨跌和同期大盘。提到某个指数时用它的短名，第一次提到时后面带理由原话。

Input parameters:

- `market` (string): 只列 A 股或美股的，默认全部
- `q` (string): 理由指数的短名或理由原话，如「腰斩指数」「已经腰斩了，可以抄底」；不填列全部

### `reason_index_stocks` (~95 tokens)

某个理由指数今天的成分股：今天符合这条理由的股票，按市值从大到小，每只带今天的读数和条件。

Input parameters:

- `market` (string): A 股或美股，默认 A 股
- `q` (string, required): 理由指数的短名或理由原话
- `top` (integer): 列前几只，默认 20

### `stock_reasons` (~65 tokens)

一只股票今天在哪几个理由指数里（今天符合哪几条买卖理由）。A 股给名字或 6 位代码，美股给代码。

Input parameters:

- `stock` (string, required): 股票名字或代码，如「贵州茅台」「600519」「NVDA」

### `qtg_risk_index` (~134 tokens)

QTG 风险指数：31 个申万一级行业过热程度（每个行业 5 个信号亮了几个）合成的一个数，0～100。返回今天的全市场风险指数和比上一个交易日、历史上同一区间之后 60 个交易日沪深300 跌 15% 以上的概率、风险最高的几个行业和今天亮红灯的行业。给 industry 时只看这个行业。

Input parameters:

- `industry` (string): 申万一级行业名，如「医药生物」；不填看全市场

### `risk_check` (~164 tokens)

查一只 A 股标的的风险读数。给一个 A 股标的：个股名字或 6 位代码、申万一级行业名、ETF/基金名字或代码、宽基指数名。返回：三个月内跌 ≥15% 的概率、平时的概率、它自己历史的概率、在不在安全区、最坏情况、过热档和红灯、警戒线三档（1.0/1.5/2.0 倍波动带）、按哪个标的代算。用户看到的标的一律写「名字（代码）」。

Input parameters:

- `target` (string, required): 标的：名字或代码，如「招商蛇口」「001979」「房地产」「沪深300」

### `verify_reasons` (~206 tokens)

核对持有理由。把用户说的理由对到九类里（周期反转、趋势延续、估值见底、产业受益、龙头集中、高股息防守、超跌反弹、题材热度、避险），返回每条理由今天成立/不成立/已证伪，以及依据的数字。如果用户的理由属于「大家都在买 / 朋友推荐 / 别人说的 / 听说有消息 / 等回本 / 拿了很久 / 这是用途」这七类，这不算能每天检查的理由，返回对应的一句话，请把那句话转给用户并再问一次真正的理由。

Input parameters:

- `no_reason_kind` (string): 用户说的其实不是理由时，填它属于哪一类
- `reasons` (array, required): 理由标签，1～4 个
- `target` (string, required): 标的名字或代码

### `create_risk_order` (~289 tokens)

建一张单子（替用户盯着这只股票和她的理由）。必须有理由：reasons 至少一个标签，没有理由不建——先用 verify_reasons 问清楚。建好后每天收盘后检查理由、过热档、警戒线，有变化才告诉她。警戒线三档 guard_k：1.0（紧，正常波动约四成会碰到）、1.5（默认）、2.0（松）。需要手机号：和网站是同一个账户，没有就按这个手机号新建。同一标的已有在盯的单不会重复建。

Input parameters:

- `amount` (number): 持有金额，元（可不填）
- `guard_k` (string): 警戒线档位，默认 1.5
- `phone` (string, required): 用户手机号（11 位）；测试用 probe_xxx
- `position` (number): 这只占总资产的仓位 %（可不填）
- `reason_text` (string): 用户理由的原话，一句
- `reasons` (array, required): 理由标签，1～4 个（必填）
- `target` (string, required): 标的名字或代码
- `tolerance` (string): 承受度：这一笔最多亏总资产的 %，默认 5

### `my_risk_orders` (~117 tokens)

查我的单子：这个手机号名下在盯的、碰线的、已结束的单，每张的警戒线、仓位、理由、建单以来涨跌、今天的过热档和概率。

Input parameters:

- `order_id` (integer): 只看这一张（看全部字段）
- `phone` (string, required): 用户手机号；测试用 probe_xxx
- `status` (string): open=在盯和碰线的（默认），closed=已结束，all=全部

### `market_now` (~92 tokens)

今天的市场环境：全市场过热档、大盘波动档、亮红灯的行业（过热档高且大盘波动不高）、新亮和熄灭的红灯、31 个申万一级行业按过热档排序和各自三个月内跌 ≥15% 的概率。

Input parameters:

- `top` (integer): 列前几个行业，默认 10

### `ledger_review` (~71 tokens)

台账复盘：红灯亮了之后真的跌了吗。返回最近几次红灯（亮灯日、行业、到今天/三个月内的最大跌幅、有没有跌过 5%）、历史比例和样本数、今天亮起和熄灭的红灯。

### `evidence_card` (~61 tokens)

行业证据卡（可选）：某个申万一级行业今天的机会分、证据充分度和打分依据，只读。

Input parameters:

- `industry` (string, required): 申万一级行业名，如「房地产」「银行」「半导体」

### `login` (~84 tokens)

用手机号登录/注册。和网站 QuantToGo 是同一套账户：手机号查到就是她，查不到就按这个手机号新建（限时免费）。返回账户状态。只有建单、查我的单需要；查读数、市场、台账不需要。

Input parameters:

- `phone` (string, required): 11 位手机号；测试用 probe_xxx

## Diagnostics

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

## Score history

- 2026-11-05: 63
- 2026-11-04: 62
- 2026-11-03: 61
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 60
- 2026-10-30: 60
- 2026-10-29: 59
- 2026-10-28: 59
- 2026-10-27: 58
- 2026-10-26: 58
- 2026-10-25: 57
- 2026-10-24: 57

## Common questions

### What is the QuantToGo Reason Index MCP server?

QuantToGo Reason Index is an MCP server listed in the public MCP registry as com.quanttogo/quanttogo-mcp. QuantToGo Reason Index: every reason people buy or sell stocks, turned into an index. This page covers its hosted endpoint (https://mcp.quanttogo.com/v2/sse).

### Is the QuantToGo Reason Index MCP server safe to use?

QuantToGo Reason Index scores 63 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 QuantToGo Reason Index MCP server expose?

QuantToGo Reason Index exposes 12 tools: reason_index, reason_index_stocks, stock_reasons, qtg_risk_index, risk_check, and 7 more. Their descriptions and schemas cost roughly 1,584 tokens of context every time the server is loaded.

### Does the QuantToGo Reason Index MCP server require authentication?

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

### Is the QuantToGo Reason Index MCP server still maintained?

QuantToGo Reason Index 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 QuantToGo Reason Index MCP server?

VerifyMCP ran 12 checks on QuantToGo Reason Index, 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 QuantToGo Reason Index: 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://mcp.quanttogo.com/v2/sse
- Repository: https://github.com/QuantToGo/quanttogo-mcp
- Website: https://quanttogo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2-sse.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2-sse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2-sse.json
- HTML version of this page: https://verifymcp.io/servers/com-quanttogo-quanttogo-mcp/v2-sse