China holidays and lunar calendar lookup, solar-to-lunar conversion and yearly schedule.

What we measured

Over the last 30 days we probed this MCP server 28 times on 27 days; it answered 4 (14%). Median response 1,421 ms, 95th percentile 1,674 ms.

When we called tools/list it returned 3 tools, including query_holiday, solar_to_lunar, list_holidays, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 12% and higher on readiness than 34%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (3)

As returned by the server's own tools/list when we called it.

query_holiday: 查询指定公历日期的中国法定节假日或调休安排，同时返回农历信息。支持2025、2026年。参数date格式：YYYY-MM-DD
solar_to_lunar: 将公历日期转换为农历日期，返回农历年月日、是否闰月、生肖、干支等信息
list_holidays: 列出指定年份的全部中国法定节假日安排，包括放假日期和调休上班日期。支持2025、2026年

MCP readiness

C · 69/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 75.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1674 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	2.14/15	4/28 probes succeeded over 30 days (14%).
Tool declaration	10/10	Lists 3 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1674 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-12.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness: Higher than 34% of peers; This listing 69 · peer median 81
Latency: Faster than 12% of peers; This listing 912 ms · peer median 349 ms

Where it loses the most points, and how to win them back

Uptime (30 days) −12.9 — Stay reachable in our daily probes.
Now: 4/28 probes succeeded over 30 days (14%).
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub: ★ 0 · 0 forks; last push 2026-09-06

Listed in

Directories this entry was found in.

mcp-registry since 2026-09-07 agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

https://mcp.pianam.cn/calendar-mcp/mcp

JSON-RPC initialize probe

curl -X POST https://mcp.pianam.cn/calendar-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Source code

https://github.com/boy-373/calendar-mcp