看雪山 Kanxueshan
io.github.geoxing/kanxueshangeoxingstreamable-httpv1.0.0Scanned
日照金山预报：中国雪山 7 天内的日出/日落金光时段与可见度评分。Golden-hour forecasts for snow mountains in China.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
forecast_peak查询某山峰未来 N 天（1-7）的日照金山预报。 参数 peak: 山峰名；days: 预报天数；viewpoint: 观景点名（可选，如子梅垭口）； date: 起始日期 YYYY-MM-DD，缺省今天。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 查询某山峰未来 N 天（1-7）的日照金山预报。 参数 peak: 山峰名；days: 预报天数；viewpoint: 观景点名（可选，如子梅垭口）； date: 起始日期 YYYY-MM-DD，缺省今天。
Only reads 2Show 2 read-only tools
query_peaks按经纬度查询周边可见雪山及今日日照金山预报（金光时段、0-100 评分、天气因子）。 参数 lat/lng: WGS-84 十进制度坐标；date: YYYY-MM-DD，缺省今天。No findings
Why it is in this group
- The name "query_peaks" says "query": a word for reading.
Description, as the server wrote it 按经纬度查询周边可见雪山及今日日照金山预报（金光时段、0-100 评分、天气因子）。 参数 lat/lng: WGS-84 十进制度坐标；date: YYYY-MM-DD，缺省今天。
search_peak搜索中国雪山，返回匹配的山峰及其观景点（子梅垭口、飞来寺、台怀镇等）。 参数 name: 山峰名关键词（贡嘎山、幺妹峰、卡瓦格博、慕士塔格等）。No findings
Why it is in this group
- The name "search_peak" says "search": a word for reading.
Description, as the server wrote it 搜索中国雪山，返回匹配的山峰及其观景点（子梅垭口、飞来寺、台怀镇等）。 参数 name: 山峰名关键词（贡嘎山、幺妹峰、卡瓦格博、慕士塔格等）。
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 14:59 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.yilong.art/mcp: tools/list returned 3 tools to an anonymous client, including forecast_peak (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http kanxueshan https://www.yilong.art/mcpclaude mcp add --transport http kanxueshan https://www.yilong.art/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__kanxueshan__search_peak",
"mcp__kanxueshan__query_peaks"
],
"ask": [
"mcp__kanxueshan__forecast_peak"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kanxueshan. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.geoxing/kanxueshan/verify?hash=8ccadd1ec6030c718a97c5cd5f40103b208ec9402ac09209e6fb35cca9e1c5d6" | jq -e '.changed == false'Pinned hash 8ccadd1ec603, from Oct 21, 2026, 19:22 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.geoxing/kanxueshan/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.geoxing/kanxueshan)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.