China PolicySignal
REMOTE · POLICY-SIGNAL.ONRENDER.COM
Search Chinese government and Party documents: Xi Jinping speeches and articles, 2012 to present.
Available components
Last scanned (21 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 19 Oct 26 −5
- HTTPS: pass → unverified ▼ security
- 18 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Aug 26 0
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 4 Nov 2026 · Probed https://policy-signal.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of policy-signal.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://policy-signal.onrender.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://policy-signal.onrender.com/mcp | Inconclusive | 429 |
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 →
corpus_stats ~40
语料库覆盖情况:总篇数、时间范围、来源分布、待抓取/失败数、站点总数对比。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_article ~48
按 id 取一篇文章的完整元数据与全文。max_chars>0 时截断正文。
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | integer | yes | – |
| max_chars | integer | – | – |
No output schema declared.
No examples provided.
get_context ~84
单篇精读:返回该文章中命中 query 的段落及前后 window 段上下文(带段号)。 需要逐字引用原话时,必须从这里或 get_article 的返回文本中原样复制。
| Name | Type | Req | Description |
|---|---|---|---|
| article_id | integer | yes | – |
| query | string | yes | – |
| window | integer | – | – |
No output schema declared.
No examples provided.
list_articles ~85
按时间/来源/标题子串浏览语料库(不做全文匹配,浏览用)。
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| limit | integer | – | – |
| newest_first | boolean | – | – |
| offset | integer | – | – |
| source | string | – | – |
| title_contains | string | – | – |
No output schema declared.
No examples provided.
phrase_trend ~164
提法(tifa)趋势:每个提法在各时间桶的覆盖率(articles/per100)与强度(per10k_chars)。 提法的出现、升温、降温、消失是可观察的政策信号(CMP 方法论);时间桶零填充,消失本身即信号。 注意:per100 对高频词(如单字"党")会饱和于 100,看强度变化用 per10k_chars;小桶(of<20)噪声大。 适合对比同义/竞争提法,如 ["高质量发展","高速增长"]。
| Name | Type | Req | Description |
|---|---|---|---|
| granularity | string | – | – |
| phrases | array | yes | – |
No output schema declared.
No examples provided.
recent_signals ~121
新提法信号:近 days 天(上限365)相对之前 baseline_days 天(上限1095)基线明显升温 或全新出现的表述(锚定语料库最新文章日期)。baseline_count=0 即全新提法。 结果带 baseline_thin 标志,基线过薄时 ratio 仅供参考。用于预测前的信号扫描。
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_days | integer | – | – |
| days | integer | – | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
search ~145
全文检索语料库。query 支持多个词(空格分隔;mode="and" 全部命中 / "or" 任一命中, 可用于同义提法集合)。date_from/date_to 格式 YYYY-MM-DD;source 可选来源子串; order 可选 relevance/newest/oldest。返回 id、标题、日期、来源和命中片段。
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| limit | integer | – | – |
| mode | string | – | – |
| order | string | – | – |
| query | string | yes | – |
| source | string | – | – |
No output schema declared.
No examples provided.
topic_timeline ~94
主题证据时间线:按时间桶(year/quarter/month)返回该主题最相关的若干篇(含片段), 用于追踪他在某问题上表述的演变。研究特定场景/问题时先用这个建立证据骨架。
| Name | Type | Req | Description |
|---|---|---|---|
| granularity | string | – | – |
| per_bucket | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the China PolicySignal MCP server?
China PolicySignal is a hosted endpoint at https://policy-signal.onrender.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 · policy-signal.onrender.com
claude mcp add --transport http acee-ventures-china-policy-signal 'https://policy-signal.onrender.com/mcp'
What is the China PolicySignal MCP server?
China PolicySignal is an MCP server listed in the public MCP registry as io.github.acee-ventures/china-policy-signal. Search Chinese government and Party documents: Xi Jinping speeches and articles, 2012 to present. This page covers its hosted endpoint (https://policy-signal.onrender.com/mcp).
Is the China PolicySignal MCP server safe to use?
China PolicySignal scores 18 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 China PolicySignal MCP server expose?
China PolicySignal exposes 8 tools: search, get_article, list_articles, topic_timeline, phrase_trend, and 3 more. Their descriptions and schemas cost roughly 781 tokens of context every time the server is loaded.
Does the China PolicySignal MCP server require authentication?
Its publisher declares no required credentials for China PolicySignal. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the China PolicySignal MCP server still maintained?
China PolicySignal is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.