# 知一刻 Zhiyike (remote · zhiyike.cn)

Free read-only Chinese AI news MCP: verified events, reports, products. No API key.

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

## Components

- remote · `zhiyike.cn`: 73/100 (this document), [markdown](https://verifymcp.io/servers/biletian-zhiyike/zhiyike.md), [page](https://verifymcp.io/servers/biletian-zhiyike/zhiyike)

## Channel facts

- Endpoint: `https://zhiyike.cn/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.4`

## 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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 知一刻 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.

### Claude

```bash
claude mcp add --transport http biletian-zhiyike 'https://zhiyike.cn/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "biletian-zhiyike": {
      "url": "https://zhiyike.cn/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "biletian-zhiyike": {
      "type": "http",
      "url": "https://zhiyike.cn/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.biletian-zhiyike]
url = "https://zhiyike.cn/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "biletian-zhiyike": {
      "type": "remote",
      "url": "https://zhiyike.cn/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add biletian-zhiyike --url 'https://zhiyike.cn/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  biletian-zhiyike:
    url: "https://zhiyike.cn/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "biletian-zhiyike": {
      "Transport": "http",
      "Url": "https://zhiyike.cn/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add biletian-zhiyike -t streamable-http -u 'https://zhiyike.cn/mcp'
```

### Other

```json
{
  "mcpServers": {
    "biletian-zhiyike": {
      "type": "http",
      "url": "https://zhiyike.cn/mcp"
    }
  }
}
```

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-04 (score 73, +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-11-02 (score 72, +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-31 (score 71, +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-29 (score 70, +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-28 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 69)

First indexed and scored.

## MCP tools (6)

### `list_news` (~127 tokens)

查询已发布新闻

按日期和关键词查询公开新闻，默认北京时间今天，按发布时间从新到旧排序。有图的条目带 cover（站内图片地址与图源）。text 为已排版 Markdown（含封面图语法）；前若干条有 cover 时尽量附缩略图 image 块（有 image 时省略 structuredContent）。availableDates 为可查日期，nextOffset 非空表示还有下一页。

Input parameters:

- `date` (string)
- `limit` (integer)
- `offset` (integer)
- `query` (string)

### `get_news_detail` (~64 tokens)

读取新闻详情

用 list_news 返回的 id 获取文章摘要、变化、深入内容、后续观察和原文链接。text 为已排版 Markdown；有 cover 时尽量附带 image 内容块（失败则仅 Markdown 外链）。

Input parameters:

- `id` (string, required)

### `search_library` (~69 tokens)

搜索产品或概念库

查询已公开产品或已沉淀概念；可按名称或关键词筛选，返回定义、说明与来源，不包含待复核资料。

Input parameters:

- `kind` (string, required)
- `limit` (integer)
- `offset` (integer)
- `query` (string)

### `list_reports` (~45 tokens)

查询日报周报目录

列出已发布日报 daily 或周报 weekly，从最新一期开始。

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `period` (string, required)

### `get_report` (~129 tokens)

读取日报周报

读取目录中的指定一期，省略 date 返回最新已发布一期（不一定是今天）。日报日期 YYYY-MM-DD 为发布日（期号日期，内容是前一天的新闻，见 contentDate），周报 YYYY-Www。支持分页。text 为已排版 Markdown（含封面图语法）；前若干条有 cover 时尽量附缩略图 image 块（有 image 时省略 structuredContent）。

Input parameters:

- `date` (string)
- `limit` (integer)
- `offset` (integer)
- `period` (string, required)

### `github_trending` (~53 tokens)

读取 GitHub AI 热榜

返回站内保存的 AI 项目日榜或周榜及快照更新时间，不是实时抓取。

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `period` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/biletian-zhiyike/zhiyike#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 69
- 2026-10-27: 69

## Common questions

### 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.

## Links

- Remote endpoint: https://zhiyike.cn/mcp
- Repository: https://github.com/biletian/zhiyike-connect
- Website: https://zhiyike.cn/
- Changelog RSS feed: https://verifymcp.io/servers/biletian-zhiyike/zhiyike.xml
- Changelog JSON feed: https://verifymcp.io/servers/biletian-zhiyike/zhiyike/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/biletian-zhiyike/zhiyike.json
- HTML version of this page: https://verifymcp.io/servers/biletian-zhiyike/zhiyike