知一刻 Zhiyike
REMOTE · ZHIYIKE.CN
Free read-only Chinese AI news MCP: verified events, reports, products. No API key.
Available components
Last scanned (6 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1743 tokens (~249/item across 7 items; 6 tools + 1 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 Management30
- Stability observed for 9 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 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.
- 2 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.
- 31 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.
- 29 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.
- 28 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 69
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://zhiyike.cn/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zhiyike.cn | CN=YE1,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54a6ba24107bea62327b01222f465684c58 |
| SANs: zhiyike.cn | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 zhiyike.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | DS published | 33094 | 8 | Verified |
| zhiyike.cn. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' https: data: blob:; connect-src 'self'; object-src 'none'; frame-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zhiyike.cn/mcp | Verified | 200 | |
| http (plaintext) | http://zhiyike.cn/mcp | HTTPS enforced | 301 | https://zhiyike.cn/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 →
get_news_detail 读取新闻详情 ~64
用 list_news 返回的 id 获取文章摘要、变化、深入内容、后续观察和原文链接。text 为已排版 Markdown；有 cover 时尽量附带 image 内容块（失败则仅 Markdown 外链）。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_report 读取日报周报 ~129
读取目录中的指定一期，省略 date 返回最新已发布一期（不一定是今天）。日报日期 YYYY-MM-DD 为发布日（期号日期，内容是前一天的新闻，见 contentDate），周报 YYYY-Www。支持分页。text 为已排版 Markdown（含封面图语法）；前若干条有 cover 时尽量附缩略图 image 块（有 image 时省略 structuredContent）。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| period | string | yes | – |
No output schema declared.
No examples provided.
github_trending 读取 GitHub AI 热榜 ~53
返回站内保存的 AI 项目日榜或周榜及快照更新时间，不是实时抓取。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| period | string | yes | – |
No output schema declared.
No examples provided.
list_news 查询已发布新闻 ~127
按日期和关键词查询公开新闻，默认北京时间今天，按发布时间从新到旧排序。有图的条目带 cover（站内图片地址与图源）。text 为已排版 Markdown（含封面图语法）；前若干条有 cover 时尽量附缩略图 image 块（有 image 时省略 structuredContent）。availableDates 为可查日期，nextOffset 非空表示还有下一页。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
list_reports 查询日报周报目录 ~45
列出已发布日报 daily 或周报 weekly，从最新一期开始。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| period | string | yes | – |
No output schema declared.
No examples provided.
search_library 搜索产品或概念库 ~69
查询已公开产品或已沉淀概念；可按名称或关键词筛选，返回定义、说明与来源，不包含待复核资料。
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
How do I install the 知一刻 Zhiyike MCP server?
知一刻 Zhiyike is a hosted endpoint at https://zhiyike.cn/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 · zhiyike.cn
claude mcp add --transport http biletian-zhiyike 'https://zhiyike.cn/mcp'
What is the 知一刻 Zhiyike MCP server?
知一刻 Zhiyike is an MCP server listed in the public MCP registry as io.github.biletian/zhiyike. Free read-only Chinese AI news MCP: verified events, reports, products. No API key. This page covers its hosted endpoint (https://zhiyike.cn/mcp).
Is the 知一刻 Zhiyike MCP server safe to use?
知一刻 Zhiyike scores 73 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 知一刻 Zhiyike MCP server expose?
知一刻 Zhiyike exposes 6 tools: list_news, get_news_detail, search_library, list_reports, get_report, github_trending. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.
Does the 知一刻 Zhiyike MCP server require authentication?
No. We connected to 知一刻 Zhiyike without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 知一刻 Zhiyike MCP server still maintained?
知一刻 Zhiyike 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 知一刻 Zhiyike MCP server?
VerifyMCP ran 13 checks on 知一刻 Zhiyike, 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.