MCP servers › io.github.alanwang100 › jizhineng-mcp

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.github.alanwang100/jizhineng-mcp

Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-24version 1.0.0streamable HTTP12 tools

Summary

io.github.alanwang100/jizhineng-mcp is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 12 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: link does not open publicly
Tools: 12
Last tested: 2026-10-24

Add to your client

Worth knowing before you connect it

The linked repository does not open publicly, so the code cannot be reviewed through it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-24
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-23 (registry, as of the 2026-10-24 snapshot)
First listed version: 2026-10-23 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-24
Package and repository: checked 2026-10-24
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.0.0 (published 2026-10-23).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

12tools

0resources

0prompts

None of its 12 tools are described as changing anything. For 12 the reading was uncertain, so no mark is shown.

weather_query
“查询任意中文/英文城市的当前天气与未来数日预报（温度、天气现象、风力、湿度）。当任务涉及"某地天气/要不要带伞/未来几天温度"时使用。典型输入：{"city":"北京","days":3}；城市直接用名称，无需经纬度。”
Publisher declares: read-only yes
2 inputs, 1 required
- citystringrequired“城市名，如北京、上海、深圳、Hangzhou”
- daysinteger“预报天数 1-7，默认 1（仅当前天气）”
time_nowon 3 other servers
“获取指定时区的当前日期时间。当任务涉及"现在几点/今天日期/某时区当前时间/时差换算"时使用。典型输入：{"timezone":"Asia/Shanghai"}；也接受中文城市名如"东京"、"纽约"，缺省为北京时间。”
Publisher declares: read-only yes
2 inputs
- timezonestring“IANA 时区名（如 Asia/Shanghai）或中文城市名（如东京），默认 Asia/Shanghai”
- formatstring“输出格式：iso（默认）或 human（中文可读）”
unit_converton 15 other servers
“在长度/重量/温度/体积/速度/面积/数据量单位之间换算。当任务出现"多少公里等于多少英里/磅换算公斤/华氏度转摄氏度"等需求时使用。典型输入：{"value":100,"from":"km","to":"mi"}；单位支持中英文（如公里、kg、°C、GB）。”
Publisher declares: read-only yes
3 inputs, 3 required
- valuenumberrequired“数值，如 100”
- fromstringrequired“源单位（中英文均可），如 km、公斤、°C、GB”
- tostringrequired“目标单位，如 mi、斤、°F、MB”
currency_converton 8 other servers
“按最新（或指定日期）参考汇率换算两种货币金额。当任务涉及"100美元等于多少人民币/汇率多少"时使用。典型输入：{"amount":100,"from":"USD","to":"CNY"}；货币用 ISO 三字母代码。数据源为欧洲央行参考汇率（免费）。”
Publisher declares: read-only yes
4 inputs, 2 required
- amountnumber“金额，默认 1”
- fromstringrequired“源货币代码，如 USD、CNY、JPY”
- tostringrequired“目标货币代码，如 CNY、EUR、HKD”
- datestring“历史日期 YYYY-MM-DD，留空取最新”
holiday_cn
“查询中国法定节假日与调休安排：某天是否放假、节日名称、调班信息。当任务涉及"国庆放几天/某天是否上班/下个假期"时使用。典型输入：{"date":"2026-10-01"}；date 留空查询今天。2026 年数据内置离线可查。”
Publisher declares: read-only yes
1 input
- datestring“日期 YYYY-MM-DD，留空为今天”
ip_locateon 1 other server
“查询 IPv4 地址的归属地（国家/省市/运营商/时区）。当任务涉及"这个 IP 是哪里的/来源归属"时使用。典型输入：{"ip":"8.8.8.8"}；ip 留空则查询调用方自身出口 IP。”
Publisher declares: read-only yes
1 input
- ipstring“IPv4 地址，如 8.8.8.8；留空查询调用方自身 IP”
todo_manage
“管理待办事项清单：新增/查看/完成/删除/清空。当任务涉及"记个待办/我还有哪些事/把某条标记完成"时使用。典型输入：{"action":"add","title":"周五前提交周报"}；数据按调用方隔离，可用 list 参数分清单（默认 default）。”
Publisher declares: read-only no
5 inputs, 1 required
- actionstringrequired“操作：add 新增 / list 查看 / complete 完成 / delete 删除 / clear 清空已完成”
- titlestring“待办内容（add 时必填），如周五前提交周报”
- idinteger“待办 ID（complete/delete 时必填，list 结果中可见）”
- liststring“清单名，默认 default”
- include_doneboolean“list 时是否包含已完成，默认 true”
web_fetchon 14 other servers
“抓取指定 URL 网页并提取正文纯文本（去脚本/样式/标签，自动截断）。当任务涉及"总结这个链接/读取网页内容/提取文章正文"时使用。典型输入：{"url":"https://example.com","max_chars":3000}。仅支持公开可访问的 http/https 页面。”
Publisher declares: read-only yes
2 inputs, 1 required
- urlstringrequired“完整 URL（含 http:// 或 https://）”
- max_charsinteger“返回正文最大字符数，默认 3000，上限 10000”
exchange_rateon 3 other servers
“查询主要货币兑某基准货币的实时汇率（open.er-api.com）”
Publisher declares: read-only yes
1 input
- basestring“基准货币代码，默认 USD，如 USD、CNY、EUR”
hacker_news_search
“搜索 Hacker News 最新科技资讯与讨论（Algolia HN Search）”
Publisher declares: read-only yes
3 inputs, 1 required
- tagsstring“内容类型过滤，如 story、show_hn、ask_hn”
- querystringrequired“搜索关键词，如 AI agent、MCP”
- hitsPerPagenumber“返回条数，默认 10”
ip_infoon 5 other servers
“查询指定 IP 的地理位置与网络信息（ip-api.com）”
Publisher declares: read-only yes
1 input
- ipstring“IPv4 地址，如 8.8.8.8；留空查询当前出口 IP”
world_time
“查询指定时区的当前时间（worldtimeapi.org）”
Publisher declares: read-only yes
1 input, 1 required
- timezonestringrequired“IANA 时区名，如 Asia/Shanghai、America/New_York、Europe/London”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 26
Tools with a description: 100% of 12
Typical description length: 91 characters

The tool set

Counted from the listing

Tools: 12
Size of the list: about 1,312 tokens for an agent to load (characters ÷ 4)
Naming: 12 of 12 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 12 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.xn--5kvtwv52d.com/mcp/gateway

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "jizhineng-mcp": {
      "url": "https://mcp.xn--5kvtwv52d.com/mcp/gateway"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "jizhineng-mcp": {
      "type": "http",
      "url": "https://mcp.xn--5kvtwv52d.com/mcp/gateway"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"jizhineng-mcp","type":"http","url":"https://mcp.xn--5kvtwv52d.com/mcp/gateway"}'

Claude Code

claude mcp add --transport http jizhineng-mcp https://mcp.xn--5kvtwv52d.com/mcp/gateway

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.xn--5kvtwv52d.com/mcp/gateway --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.xn--5kvtwv52d.com/mcp/gateway	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/alanwang100/jizhineng-mcp	Does not open (not found or private)	differs	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.alanwang100

Repository: github.com/alanwang100/jizhineng-mcp — does not open publicly

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe linked repository returned HTTP 404: it does not exist or is private.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.alanwang100/jizhineng-mcp

Answered from the data above

Is io.github.alanwang100/jizhineng-mcp safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: The repository it links to does not open publicly, so its code cannot be inspected through that link. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.alanwang100/jizhineng-mcp need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.alanwang100/jizhineng-mcp been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Where is the source code of io.github.alanwang100/jizhineng-mcp?

The registry links to github.com/alanwang100/jizhineng-mcp, but that link does not open publicly, so the code cannot be inspected through it.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
3,488 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 12 tools, 0 resources, 0 prompts.
7,237 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

does not apply

no existing GitHub repository

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

not stated

repository link is dead (HTTP 404), so activity cannot be read

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.alanwang100/jizhineng-mcp: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.github.alanwang100/jizhineng-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.alanwang100/jizhineng-mcp)](https://protocolprobe.com/mcp/servers/io.github.alanwang100/jizhineng-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology