China Context MCP
PYPI · CHINA-CONTEXT-MCP
中国节假日与调休（单日+年度聚合）、历史上的今天、随机诗词、身份证号校验（GB 11643，本地零网络）。零凭证。
Available components
Last scanned (3 hours ago)
Scores higher than 91% of PyPI servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 37 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mouseart2025/china-context-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 843 tokens (~168/item across 5 items; 5 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 33 to 53. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 28 Sept 26 +10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 68
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 17 Oct 2026 · Analysed pypi/china-context-mcp@0.1.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mouseart2025/china-context-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mouseart2025/china-context-mcp/.github/workflows/release.yml@refs/tags/v0.1.5 |
| Rekor log index | 2968046062 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:fcd83c589d13584b3a4ddde3c699e07f2a5ca57014f2e0b48b8f3044aaa98230 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 37 packages
| Packages resolved | 37 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
history_today History Today ~117
返回「历史上的今天」：某月某日发生的历史事件列表（标题 + 年份 + 简述）。 参数 date：可选，格式 "MM-DD"（如 "09-25"）或 "YYYY-MM-DD"（如 "2026-09-25"）。 省略则使用今天。 适用：历史问答、内容创作、文化类 AI 陪练。 数据来自 60s-api.viki.moe（公开、零凭证）。
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
holiday_info Holiday Info ~258
查询中国某日期的节假日 / 调休 / 是否工作日信息。 参数 date：YYYY-MM-DD，例如 "2026-10-01"。 返回：节假日名称、是否法定假日、是否调休补班工作日、工资倍率。 数据来自 timor.tech（公开、零凭证）+《全国年节及纪念日放假办法》法规常量层（离线）。 ★ 三态语义（本工具的核心契约，不得退化）： - 该年份有权威数据 ⇒ 正常给出法定假日 / 工作日 / 倍率。 - 该年份无数据，但日期是《放假办法》规定的**公历固定法定节假日** （元旦 1/1、劳动节 5/1-5/2、国庆 10/1-10/3）⇒ 法定假日**是**，并注明放假起止与调休待公布。 - 其余无数据情况 ⇒ 明确说「暂无权威数据、无法判断」，**绝不说「否」**。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
holiday_summary Holiday Summary ~211
返回中国某年的节假日与调休摘要——聚合推导，不是单日查询。 与 holiday_info 的区别：本工具对 timor 全年扁平数据做聚合，给出 holiday_info 拿不到、而 AI 自身容易算错的结论——连续假期区间与天数、 法定 3 倍工资天数与**具体是哪几天**、全部调休补班日、全年总休假天数。 每条区间的逐日明细按工资倍率分组输出，例如 `3倍 4 天：02-16、02-17 初一、02-18 初二、02-19 初三`。 参数 year：4 位年份，省略则用当前年。 适用：年度休假规划、考勤与排班、HR 与薪酬核算。 数据来自 timor.tech（公开、零凭证）。
| Name | Type | Req | Description |
|---|---|---|---|
| year | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
idcard_check Idcard Check ~192
校验中国居民身份证号（GB 11643），并解析国标公开字段。 ★ 纯本地算法，不联网、零凭证：按 ISO 7064 MOD 11-2 加权算法验证末位校验码。 这类 17 位加权求和 + 模 11 查表，**AI 自行计算极易出错**（因子表或索引错位）。 因此本工具的价值不在"包 API"（它无 API 可包），而在**替 AI 算对**。 参数 id_number：18 位身份证号，末位 X/x 大小写均可。 隐私：仅解析国标公开字段（出生日期/性别/省级），不触姓名与住址；回显做中间掩码。
| Name | Type | Req | Description |
|---|---|---|---|
| id_number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
random_poem Random Poem ~65
随机返回一句中国古典诗词，含作者、出处与分类。 适用：中文创作灵感、文化问答、语文/国学类 AI 陪练。 数据来自 jinrishici.com（公开、零凭证）。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the China Context MCP server?
China Context MCP runs locally as a PyPI package, launched with uvx china-context-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · china-context-mcp
claude mcp add mouseart2025-china-context-mcp -- uvx china-context-mcp
What is the China Context MCP server?
China Context MCP is listed in the public MCP registry as io.github.mouseart2025/china-context-mcp. 中国节假日与调休（单日+年度聚合）、历史上的今天、随机诗词、身份证号校验（GB 11643，本地零网络）。零凭证。 This page covers its PyPI package (china-context-mcp).
Is the China Context MCP server safe to use?
China Context MCP scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. 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 Context MCP server expose?
China Context MCP exposes 5 tools: random_poem, holiday_info, holiday_summary, history_today, idcard_check. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.
Is the China Context MCP server still maintained?
China Context MCP is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the China Context MCP server under?
China Context MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.