JiZhiMCP
REMOTE · MCP.XN--5KVTWV52D.COM
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Available components
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (todo_manage) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- 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 Usability87
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2912 tokens (~138/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +2
- Tool “settlement.transfer” is now declared destructive security
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −1
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “sdfdsf” was removed ▼ security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- Destructive annotations: pass → 0 functional
- New tool “audit.record” functional
- New tool “dns_lookup” functional
- New tool “metering.record” functional
- New tool “settlement.account” functional
- New tool “settlement.ledger” functional
- New tool “settlement.transfer” functional
- New tool “timestamp_convert” functional
- 30 Oct 26 0
- Schema quality: 1145 → 1445 ▼ functional
- New tool “github_search” functional
- New tool “stackoverflow_search” functional
- 29 Oct 26 +3
- Tool “currency_convert” rewrote its description, which is the text the model reads security
- Tool “exchange_rate” rewrote its description, which is the text the model reads security
- Tool “hacker_news_search” rewrote its description, which is the text the model reads security
- Tool “holiday_cn” rewrote its description, which is the text the model reads security
- Tool “ip_info” rewrote its description, which is the text the model reads security
- Tool “ip_locate” rewrote its description, which is the text the model reads security
- Tool “time_now” rewrote its description, which is the text the model reads security
- Tool “todo_manage” rewrote its description, which is the text the model reads security
- Tool “unit_convert” rewrote its description, which is the text the model reads security
- Tool “weather_query” rewrote its description, which is the text the model reads security
- Tool “web_fetch” rewrote its description, which is the text the model reads security
- Tool “world_time” rewrote its description, which is the text the model reads security
- Schema quality: fail → pass ▲ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: excellent → good functional
- New tool “sdfdsf” functional
- 27 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.
- 26 Oct 26 +2
- HSTS header: fail → pass ▲ security
- Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (todo_manage) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
- Tool “exchange_rate” rewrote its description, which is the text the model reads security
- Tool “hacker_news_search” rewrote its description, which is the text the model reads security
- Tool “ip_info” rewrote its description, which is the text the model reads security
- Tool “world_time” rewrote its description, which is the text the model reads security
- Tool “todo_manage” is now declared destructive security
- Schema quality: 111 → 134 ▼ functional
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://mcp.xn--5kvtwv52d.com/mcp/gateway
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.xn--5kvtwv52d.com | CN=ZeroSSL ECC DV SSL CA 2,O=ZeroSSL GmbH,C=AT | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9479067d77bccf965465b2e48b09623c |
| SANs: mcp.xn--5kvtwv52d.com | ||||||
| CN=ZeroSSL ECC DV SSL CA 2,O=ZeroSSL GmbH,C=AT (CA) | CN=Sectigo Public Server Authentication Root E46,O=Sectigo Limited,C=GB | 24 Sept 2025 | 23 Sept 2035 | ECDSA 256 | ECDSA-SHA384 | c4e1c5bb00f0278f347be4f85d63fcca |
| CN=Sectigo Public Server Authentication Root E46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust ECC Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | ECDSA 384 | ECDSA-SHA384 | 1a9eafec6de8e19b5c193141b68d90dd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.xn--5kvtwv52d.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| xn--5kvtwv52d.com. | absent | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.xn--5kvtwv52d.com/mcp/gateway | Verified | 200 | |
| http (plaintext) | http://mcp.xn--5kvtwv52d.com/mcp/gateway | HTTPS enforced | 308 | https://mcp.xn--5kvtwv52d.com/mcp/gateway |
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 →
audit.record 调用存证审计 ~237
记录一次跨 Agent 协作的调用存证，返回不可篡改的内容哈希（SHA-256）。用于多 Agent 任务结算前的存证审计：当需要证明某 Agent 在何时对何资源执行了何操作、或为跨 Agent 任务结算留痕时使用。参数：actor（执行方标识）、action（操作）、target（目标资源，可选）、detail（补充信息对象，可选）。返回 record_id、digest（内容哈希）、created_at（UTC 时间）。Example: {"actor":"agent-a","action":"tool.call","target":"weather_query","detail":{"cost":0.01}}
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 执行的操作，如 tool.call、task.complete、resource.read |
| actor | string | yes | 执行方标识（Agent 名/ID/角色），如 agent-a |
| detail | object | – | 补充信息，如 cost、tokens、备注（可选） |
| target | string | – | 目标资源，如工具名、接口路径、资源 ID（可选） |
No output schema declared.
{"action":"tool.call","actor":"agent-a","detail":{"cost":0.01},"target":"weather_query"}currency_convert 汇率换算 ~120
按最新或指定日期汇率换算两种货币金额，货币用 ISO 三字母代码。Example: {"amount":100,"from":"USD","to":"CNY"}
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | 金额，默认 1 |
| date | string | – | 历史日期 YYYY-MM-DD，留空取最新 |
| from | string | yes | 源货币代码，如 USD、CNY、JPY |
| to | string | yes | 目标货币代码，如 CNY、EUR、HKD |
No output schema declared.
{"amount":100,"from":"USD","to":"CNY"}dns_lookup DNS 解析查询 ~168
通过 DNS-over-HTTPS 查询域名的 DNS 解析记录（A/AAAA/CNAME/MX/TXT/NS），返回解析结果、TTL 与查询状态。用于排查域名解析故障、验证 DNS 配置、查看 MX 邮件服务器或 TXT 记录（如 SPF/DKIM）。典型输入：域名如 example.com、记录类型如 MX。数据源：Cloudflare DNS-over-HTTPS（免费无需 key，不可达时自动回退腾讯 DNSPod DoH）。Example: {"domain":"example.com","type":"MX"}
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 域名，如 example.com、www.baidu.com |
| type | string | – | 记录类型 A/AAAA/CNAME/MX/TXT/NS，默认 A |
No output schema declared.
{"domain":"example.com","type":"MX"}exchange_rate 汇率查询 ~59
查询主要货币兑基准货币的实时汇率，返回主流币种汇率。Example: {"base":"USD"}
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | 基准货币代码，默认 USD，如 USD、CNY、EUR |
No output schema declared.
{"base":"USD"}github_search GitHub 仓库搜索 ~158
在 GitHub 上搜索开源仓库（按名称/描述/语言匹配，按 Star/更新时间排序），返回仓库简介、主要语言、Star 数、Fork 数与链接。当任务涉及查找开源项目、代码库、框架或比较某类库的流行度时使用。Example: {"query":"mcp server","sort":"stars","per_page":5}
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | 返回条数 1-10，默认 5 |
| query | string | yes | 搜索关键词，如 "mcp server"、"weather api"、"language:python fastapi" |
| sort | string | – | 排序字段：stars / forks / updated，默认 stars |
No output schema declared.
{"per_page":5,"query":"mcp server","sort":"stars"}hacker_news_search 科技资讯搜索 ~96
搜索 Hacker News 科技资讯与讨论，返回标题/链接/热度/评论数。Example: {"query":"MCP","hitsPerPage":10}
| Name | Type | Req | Description |
|---|---|---|---|
| hitsPerPage | number | – | 返回条数，默认 10 |
| query | string | yes | 搜索关键词，如 AI agent、MCP |
| tags | string | – | 内容类型过滤，如 story、show_hn、ask_hn |
No output schema declared.
{"hitsPerPage":10,"query":"MCP"}holiday_cn 中国节假日查询 ~58
查询中国法定节假日与调休安排：某天是否放假、节日名称。Example: {"date":"2026-10-01"}
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | 日期 YYYY-MM-DD，留空为今天 |
No output schema declared.
{"date":"2026-10-01"}ip_info IP 定位信息 ~77
查询 IPv4 地址的地理位置与网络信息（国家/省市/运营商/时区），ip 留空查出口 IP。Example: {"ip":"8.8.8.8"}
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | – | IPv4 地址，如 8.8.8.8；留空查询当前出口 IP |
No output schema declared.
{"ip":"8.8.8.8"}ip_locate IP 定位查询 ~78
查询 IPv4 地址的归属地（国家/省市/运营商/时区），ip 留空查调用方出口 IP。Example: {"ip":"8.8.8.8"}
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | – | IPv4 地址，如 8.8.8.8；留空查询调用方自身 IP |
No output schema declared.
{"ip":"8.8.8.8"}metering.record 调用计量 ~213
记录或查询跨 Agent 任务的用量计量，用于跨 Agent 任务结算/分账。mode=record 时写入一条计量（参数：actor 执行方、metric 指标名、units 用量数）；mode=query 时按 actor 聚合查询累计用量（返回 total_units 与 by_metric 分组）。当多 Agent 协作需要计量各方资源消耗、或做任务结算/分账时使用。Example: {"mode":"record","actor":"agent-a","metric":"tokens","units":1200}
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | 执行方标识（Agent 名/ID/角色） |
| metric | string | – | 计量指标名，如 tokens、calls、duration_ms（record 时用） |
| mode | string | yes | record=写入计量；query=查询聚合用量 |
| units | number | – | 用量数（record 时用，必须为数字） |
No output schema declared.
{"actor":"agent-a","metric":"tokens","mode":"record","units":1200}settlement.account 结算账户 ~137
开立或查询跨 Agent 结算账户。mode=open 时开立账户（幂等，已存在则返回现有账户与余额）；mode=balance 时查询账户余额。所有 Agent 自动获得一个以账户标识命名的结算账户，初始余额为 0，可经 settlement.credit 授信或 settlement.transfer 转入 credits。Example: {"mode":"open","account_id":"agent-a"}
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | 账户标识（Agent 名/组织 ID，如 agent-a） |
| mode | string | yes | open=开户（幂等）；balance=查询余额 |
No output schema declared.
{"account_id":"agent-a","mode":"open"}settlement.ledger 结算流水对账 ~165
查询结算账户的余额与该账户的往来流水（含哈希链凭证），用于多 Agent 结算对账：核对某 Agent 的收入/支出、验证链完整性（每条流水 digest 含前一条 prev_hash）。参数：account_id 账户标识、limit 返回条数（默认 50，最大 200）。返回余额、流水列表（direction=in/out、counterparty 对手方、amount、digest、prev_hash）。Example: {"account_id":"agent-a","limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | 账户标识（Agent 名/组织 ID） |
| limit | integer | – | 返回最近 N 条流水，默认 50，最大 200（可选） |
No output schema declared.
{"account_id":"agent-a","limit":20}settlement.transfer 跨 Agent 结算转账 ~361
在任意两个跨 Agent 结算账户之间转账 credits（双边结算）。原子扣减付款方余额并增加收款方余额，写入不可篡改哈希链流水。幂等键（idempotency_key）保证重试不会重复结算。适用于多 Agent 协作后的任务结算 / 分账：Agent A 完成子任务后，由调度方调用本工具向 A 结算 credits，形成可审计的债权债务账本。参数：from_account 付款方、to_account 收款方、amount 金额（正数）、reason 原因（可选）、unit 单位（默认 credits）、idempotency_key 幂等键（强烈建议）。返回 tx_id、双方最新余额、digest（哈希链凭证）。Example: {"from_account":"orchestrator","to_account":"agent-a","amount":5,"reason":"task.complete","idempotency_key":"settle-001"}
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | 结算金额（credits，正数，最多 6 位小数） |
| from_account | string | yes | 付款方账户（发起结算的 Agent/组织） |
| idempotency_key | string | – | 幂等键：重复提交同一键不会重复结算，直接返回原交易（强烈建议，用于网络重试安全） |
| reason | string | – | 结算原因，如 task.complete、tool.cost、resource.read（可选） |
| to_account | string | yes | 收款方账户（被结算的 Agent/组织） |
| unit | string | – | 结算单位，默认 credits（可选） |
No output schema declared.
{"amount":5,"from_account":"orchestrator","idempotency_key":"settle-001","reason":"task.complete","to_account":"agent-a"}stackoverflow_search Stack Overflow 搜索 ~142
搜索 Stack Overflow 上的技术问答（按相关度排序），返回问题标题、摘要、答案数、得分、标签与链接。当任务涉及排查代码报错、查技术方案、找最佳实践时使用。Example: {"query":"javascript array deduplicate","answers":1,"limit":5}
| Name | Type | Req | Description |
|---|---|---|---|
| answers | integer | – | 最少答案数过滤（1=只要有答案，0=不限），默认 1 |
| limit | integer | – | 返回条数 1-10，默认 5 |
| query | string | yes | 搜索关键词，如 "python dict sort"、"react hooks error" |
No output schema declared.
{"answers":1,"limit":5,"query":"javascript array deduplicate"}time_now 时间时区查询 ~89
查询指定时区的当前日期时间，用于问现在几点、今天日期或某时区时间。Example: {"timezone":"Asia/Shanghai"}
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | 输出格式：iso（默认）或 human（中文可读） |
| timezone | string | – | IANA 时区名（如 Asia/Shanghai）或中文城市名（如 东京），默认 Asia/Shanghai |
No output schema declared.
{"timezone":"Asia/Shanghai"}timestamp_convert 时间戳转换 ~212
在秒级 Unix 时间戳与日期时间之间互相转换，可指定时区（默认 Asia/Shanghai）。用于把日志或 API 返回的时间戳转成可读日期，或把某日期转成时间戳做比较与计算。典型输入：时间戳 1700000000 或日期 2026-01-01。数据源：本地计算（JS Date，零外部依赖）。Example: {"mode":"to_date","value":1700000000,"timezone":"Asia/Shanghai"}
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | 转换方向：to_date 时间戳转日期 / to_ts 日期转时间戳，默认 to_date |
| timezone | string | – | IANA 时区名，默认 Asia/Shanghai |
| value | string | yes | 秒级时间戳（数字，to_date 时）或日期字符串 YYYY-MM-DD（to_ts 时），如 1700000000 或 2026-01-01 |
No output schema declared.
{"mode":"to_date","timezone":"Asia/Shanghai","value":1700000000}todo_manage 待办管理 ~157
管理待办事项清单：新增/查看/完成/删除/清空，数据按调用方隔离。Example: {"action":"add","title":"周五前提交周报"}
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 操作：add 新增 / list 查看 / complete 完成 / delete 删除 / clear 清空已完成 |
| id | integer | – | 待办 ID（complete/delete 时必填，list 结果中可见） |
| include_done | boolean | – | list 时是否包含已完成，默认 true |
| list | string | – | 清单名，默认 default |
| title | string | – | 待办内容（add 时必填），如 周五前提交周报 |
No output schema declared.
{"action":"add","title":"周五前提交周报"}unit_convert 单位换算 ~106
在长度/重量/温度/体积/速度/面积/数据量单位间换算，单位支持中英文。Example: {"value":100,"from":"km","to":"mi"}
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 源单位（中英文均可），如 km、公斤、°C、GB |
| to | string | yes | 目标单位，如 mi、斤、°F、MB |
| value | number | yes | 数值，如 100 |
No output schema declared.
{"from":"km","to":"mi","value":100}weather_query 天气查询 ~88
查询指定城市的当前天气与未来数日预报（温度/天气现象/风力/湿度）。Example: {"city":"北京","days":3}
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | 城市名，如 北京、上海、深圳、Hangzhou |
| days | integer | – | 预报天数 1-7，默认 1（仅当前天气） |
No output schema declared.
{"city":"北京","days":3}web_fetch 网页内容抓取 ~87
抓取指定 URL 网页并提取正文纯文本（去脚本/样式/标签）。Example: {"url":"https://example.com","max_chars":3000}
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | 返回正文最大字符数，默认 3000，上限 10000 |
| url | string | yes | 完整 URL（含 http:// 或 https://） |
No output schema declared.
{"max_chars":3000,"url":"https://example.com"}world_time 世界时间时区 ~58
查询指定时区的当前日期时间、星期与夏令时状态。Example: {"timezone":"Asia/Shanghai"}
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | yes | IANA 时区名，如 Asia/Shanghai、America/New_York、Europe/London |
No output schema declared.
{"timezone":"Asia/Shanghai"}How do I install the JiZhiMCP MCP server?
JiZhiMCP is a hosted endpoint at https://mcp.xn--5kvtwv52d.com/mcp/gateway, 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 · mcp.xn--5kvtwv52d.com
claude mcp add --transport http alanwang100-jizhineng-mcp 'https://mcp.xn--5kvtwv52d.com/mcp/gateway'
What is the JiZhiMCP MCP server?
JiZhiMCP is an MCP server listed in the public MCP registry as io.github.alanwang100/jizhineng-mcp. Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms. This page covers its hosted endpoint (https://mcp.xn--5kvtwv52d.com/mcp/gateway).
Is the JiZhiMCP MCP server safe to use?
JiZhiMCP scores 75 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 JiZhiMCP MCP server expose?
JiZhiMCP exposes 21 tools: weather_query, time_now, unit_convert, currency_convert, holiday_cn, and 16 more. Their descriptions and schemas cost roughly 2,866 tokens of context every time the server is loaded.
Does the JiZhiMCP MCP server require authentication?
No. We connected to JiZhiMCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the JiZhiMCP MCP server still maintained?
JiZhiMCP 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.