QuantToGo 说法百科
REMOTE · MCP.QUANTTOGO.COM · 3 COMPONENTS
QuantToGo 说法百科的 MCP 服务：A 股持仓风险读数、持有理由核对、每天替你盯着的风控单。
Available components
Last scanned (14 hours ago)
Scores higher than 44% 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1160 tokens (~145/item across 8 items; 8 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 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.
- 1 Nov 26 +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.
- 30 Oct 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.
- 28 Oct 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.
- 26 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 57
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://mcp.quanttogo.com/v2/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.quanttogo.com | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 561e8f75cb8891c2f9e431d4b9d3a51fe73 |
| SANs: mcp.quanttogo.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 mcp.quanttogo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| quanttogo.com. | absent | 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 |
|---|---|---|---|---|
| sse | https://mcp.quanttogo.com/v2/sse | Verified | 200 | |
| http (plaintext) | http://mcp.quanttogo.com/v2/sse | HTTPS enforced | 301 | https://mcp.quanttogo.com/v2/sse |
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 →
create_risk_order ~283
建一张风控单（替用户盯着）。必须有理由：reasons 至少一个标签，没有理由不建——先用 verify_reasons 问清楚。建好后每天收盘后检查理由、过热档、警戒线，有变化才告诉她。警戒线三档 guard_k：1.0（紧，正常波动约四成会碰到）、1.5（默认）、2.0（松）。需要手机号：和网站是同一个账户，没有就按这个手机号新建。同一标的已有在盯的单不会重复建。
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | 持有金额，元（可不填） |
| guard_k | string | – | 警戒线档位，默认 1.5 |
| phone | string | yes | 用户手机号（11 位）；测试用 probe_xxx |
| position | number | – | 这只占总资产的仓位 %（可不填） |
| reason_text | string | – | 用户理由的原话，一句 |
| reasons | array | yes | 理由标签，1～4 个（必填） |
| target | string | yes | 标的名字或代码 |
| tolerance | string | – | 承受度：这一笔最多亏总资产的 %，默认 5 |
No output schema declared.
No examples provided.
evidence_card ~62
广成子的证据卡（可选）：某个申万一级行业今天的机会分、证据充分度和打分依据，只读。
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | yes | 申万一级行业名，如「房地产」「银行」「半导体」 |
No output schema declared.
No examples provided.
ledger_review ~71
台账复盘：红灯亮了之后真的跌了吗。返回最近几次红灯（亮灯日、行业、到今天/三个月内的最大跌幅、有没有跌过 5%）、历史比例和样本数、今天亮起和熄灭的红灯。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login ~84
用手机号登录/注册。和网站 QuantToGo 是同一套账户：手机号查到就是她，查不到就按这个手机号新建（限时免费）。返回账户状态。只有建单、查我的单需要；查读数、市场、台账不需要。
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | 11 位手机号；测试用 probe_xxx |
No output schema declared.
No examples provided.
market_now ~92
今天的市场环境：全市场过热档、大盘波动档、亮红灯的行业（过热档高且大盘波动不高）、新亮和熄灭的红灯、31 个申万一级行业按过热档排序和各自三个月内跌 ≥15% 的概率。
| Name | Type | Req | Description |
|---|---|---|---|
| top | integer | – | 列前几个行业，默认 10 |
No output schema declared.
No examples provided.
my_risk_orders ~118
查我的风控单：这个手机号名下在盯的、碰线的、已结束的单，每张的警戒线、仓位、理由、建单以来涨跌、今天的过热档和概率。
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | – | 只看这一张（看全部字段） |
| phone | string | yes | 用户手机号；测试用 probe_xxx |
| status | string | – | open=在盯和碰线的（默认），closed=已结束，all=全部 |
No output schema declared.
No examples provided.
risk_check ~163
查风险读数（鸿钧老祖）。给一个 A 股标的：个股名字或 6 位代码、申万一级行业名、ETF/基金名字或代码、宽基指数名。返回：三个月内跌 ≥15% 的概率、平时的概率、它自己历史的概率、在不在安全区、最坏情况、过热档和红灯、警戒线三档（1.0/1.5/2.0 倍波动带）、按哪个标的代算。用户看到的标的一律写「名字（代码）」。
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | 标的：名字或代码，如「招商蛇口」「001979」「房地产」「沪深300」 |
No output schema declared.
No examples provided.
verify_reasons ~206
核对持有理由。把用户说的理由对到九类里（周期反转、趋势延续、估值见底、产业受益、龙头集中、高股息防守、超跌反弹、题材热度、避险），返回每条理由今天成立/不成立/已证伪，以及依据的数字。如果用户的理由属于「大家都在买 / 朋友推荐 / 别人说的 / 听说有消息 / 等回本 / 拿了很久 / 这是用途」这七类，这不算能每天检查的理由，返回对应的一句话，请把那句话转给用户并再问一次真正的理由。
| Name | Type | Req | Description |
|---|---|---|---|
| no_reason_kind | string | – | 用户说的其实不是理由时，填它属于哪一类 |
| reasons | array | yes | 理由标签，1～4 个 |
| target | string | yes | 标的名字或代码 |
No output schema declared.
No examples provided.
How do I install the QuantToGo 说法百科 MCP server?
QuantToGo 说法百科 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.
remote · mcp.quanttogo.com
claude mcp add --transport http com-quanttogo-quanttogo-mcp 'https://mcp.quanttogo.com/v2/sse'
What is the QuantToGo 说法百科 MCP server?
QuantToGo 说法百科 is an MCP server listed in the public MCP registry as com.quanttogo/quanttogo-mcp. QuantToGo 说法百科的 MCP 服务：A 股持仓风险读数、持有理由核对、每天替你盯着的风控单。 This page covers its hosted endpoint (https://mcp.quanttogo.com/v2/sse).
Is the QuantToGo 说法百科 MCP server safe to use?
QuantToGo 说法百科 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 QuantToGo 说法百科 MCP server expose?
QuantToGo 说法百科 exposes 8 tools: risk_check, verify_reasons, create_risk_order, my_risk_orders, market_now, and 3 more. Their descriptions and schemas cost roughly 1,079 tokens of context every time the server is loaded.
Does the QuantToGo 说法百科 MCP server require authentication?
No. We connected to QuantToGo 说法百科 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QuantToGo 说法百科 MCP server still maintained?
QuantToGo 说法百科 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.