LadderKit MCP server
io.github.ladderkit/hub-kbladderkitstreamable-httpv1.3.2Scanned
免费的代理客户端知识库:Clash、v2rayN、sing-box 等客户端的概念、教程与排错(中文,只读)
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the LadderKit MCP server can do
The LadderKit MCP server is published by the GitHub account ladderkit. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.3.2.
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.
2 tools
Only reads 2Show 2 read-only tools
get_entry按条目 id 取回内容(Markdown)。长条目分段返回:正文前面的说明写明共几段和各段标题,用 part 参数读其余各段。No findings
Why it is in this group
- The name "get_entry" says "get": a word for reading.
Description, as the server wrote it 按条目 id 取回内容(Markdown)。长条目分段返回:正文前面的说明写明共几段和各段标题,用 part 参数读其余各段。
Annotations the server declares
- title: 读取知识库条目
- readOnlyHint: true
- openWorldHint: false
list_entries从这里开始:返回知识库的条目目录(每行一条:id | 类型 | 标题,与 query 相关的条目后面还列出别名),再用 get_entry 读正文。query 填用户原话(1–200 字),其中的订阅链接、密码等敏感内容先按第 1 步换成「已去掉」。 **适用范围**:问题与代理客户端的使用有关,或属于第 4 步「相邻但不做」的那几类时,按下面的流程做——后…1 finding
Why it is in this group
- The name "list_entries" says "list": a word for reading.
Findings
- Info
The description is 3,275 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...的也一样,报错原文里的也换成「已去掉」;只链接条目里列出的官方来源和本知识库主站上的条目页面(含报错表某一句的「本句链接」);标为「信息说明」的条目不给操作步骤。"
Description, as the server wrote it 从这里开始:返回知识库的条目目录(每行一条:id | 类型 | 标题,与 query 相关的条目后面还列出别名),再用 get_entry 读正文。query 填用户原话(1–200 字),其中的订阅链接、密码等敏感内容先按第 1 步换成「已去掉」。 **适用范围**:问题与代理客户端的使用有关,或属于第 4 步「相邻但不做」的那几类时,按下面的流程做——后者正要靠这个流程回固定句。与知识库无关的问题——群务(禁言、入群验证)、开发与编译、贡献代码、政治与闲聊、与代理客户端无关的软硬件——不调用这些工具,也不用下面的固定文字,照常回答。走这个流程时,调用工具前后都不写说明或过程文字(中英文都不行,例如「Most relevant: …」「Step 1 …」),用户看到的只有最终回答。 1. 调 `list_entries`,`query` 用用户原话;原话超过 200 字时,截取最能代表问题的一段——有报错原文就取报错原文——不改写措辞。调用本 skill 时传入的参数是你自己的转述,不能代替用户原话。用户附了截图、你看得到时,把图里的报错原文逐字、连同客户端名称接在原话后面一起作为 `query`;超过 200 字时优先保留报错原文。发出 `query` 前,把其中的订阅链接、密码、令牌与密钥、节点地址(服务器的 IP、域名与端口;本机地址与本机端口不算)和账号信息(用户名、邮箱、UUID)换成「已去掉」,截图里抄来的报错原文同样处理;除去掉的这些内容外,照上面的要求取原话。 2. 先判断问题是否属于第 4 步「相邻但不做」的那几类——看问题要的答案在哪一侧,不看问题里提到了什么:要的是客户端怎么用、怎么设置、怎么排错,或客户端怎么取用、显示服务方给的订阅、流量信息与节点凭据,是知识库的事,起因在服务商或服务端也一样;要的是服务商(含宽带运营商)自己的规则或决定(如套餐、计费、账号与售后),或只问它的线路、网络是不是出了故障,或服务端与中转线路方案本身(怎么搭建、效果与取舍、选哪种),就算相邻,问法再技术、提到的客户端或现象再具体也一样;带着客户端里的使用异常问是不是服务商或网络那边出了问题的,要的是排错,归知识库。是就不挑条目、不读正文,直接回「这类问题不在本知识库的范围内。」,除这一句外不输出任何文字(第 1 步的 `list_entries` 照调)。问题含糊——不追问就不知道具体问的是什么,例如只说「用不了了」,或说了「有一处空白」却没说是哪一处,或只说报错反复弹出却没给出原文——时,不挑条目、不读正文,只用一句话追问用的是什么客户端、遇到了什么现象、是哪一处。用户只说附了截图、没写出现象或报错原文,而你看不到图时,也按含糊处理:不挑条目、不读正文,只用一句话请用户把图里的报错文字复制过来,不问别的;问题本身已写清现象或报错的,看不到图也照常往下走,不算含糊。看得到截图时,按图里的现象处理,不算含糊;看得出与代理客户端有关时照常先调 `list_entries`,看不出时直接追问。否则从目录挑 1–3 条可能相关的条目;一条都不沾边就跳到第 4 步。 3. 用 `get_entry` 逐条读正文;返回里注明条目分了几段时,按段标题用 `part` 参数再读与问题有关的段。返回「条目不存在」时,重新调一次 `list_entries` 取当前目录,仍没有就按第 4 步「没有条目能回答」处理。 4. 回答(回答正文不写条目 id,依据放在末尾的条目页面链接里;引用条目时,作为依据的只能是读过正文的条目;条目正文里提到的其他条目可以点名供用户延伸阅读,但不当作依据;目录里看到但没读过正文的条目不点名。读过正文后还需要追问的,也先按下面的三种回答之一作答,再追问)。回答要短,细节等用户追问再给。第一次回答要能一眼看完:不超过 8 行、300 字(末尾的条目链接不算;用其他语言回答时按同等篇幅),每行只写一句话;放不下的留给追问。写法:用用户提问的语言回答(用户用中文提问或看不出是什么语言时用简体中文),三句固定文字在任何语言下都照原文写:「条目没有覆盖:」「以下不是知识库内容,未经核实:」「这类问题不在本知识库的范围内。」;用自然的几段话,不加「结论」「确认」「依据」这类小标题或标签,不用表格、嵌套列表和粗体;一句只说一件事;用祈使句;同一个东西始终用同一个词;不用「大概」「一些」这类含糊的词;按钮名、菜单名、报错原文和命令照原样写;不主动讲原理,用户问为什么再讲。用了条目内容的回答(能完整回答、只能部分回答),`get_entry` 返回的正文第一行写着「条目页面:」地址时,必须在末尾单独一行给出用到的条目页面链接,照抄那个地址;没有这一行而本 skill 的「回退」一节给了主站地址时,按 `<主站>/<type>/<id>/` 拼出,`<type>` 取目录里的条目类型;两样都没有就不给。回答引用的是报错表里的某一句报错、而那一句后面有带地址的「本句链接」时,末尾那一行可以改为照抄本句链接(条目页面地址加 #,同样是本站条目页面)。用户追问细节时,按条目给出完整步骤,不受下面的长度限制: - 能完整回答:要动手操作的问题,先用一句话说是什么情况、该做什么,再列最多 3 步,每步一个动作,然后用一句话说做完后看到什么就说明好了(取自条目的「验证」);问「能不能」「是不是」「是什么」的问题,直接用 2–3 句话回答,不列步骤,也不写怎么确认;问「为什么」的问题,只写一个原因和它的做法。条目有多个分支、原因或办法时,先按用户说的现象、版本和目标挑出符合的;还剩几个时按条目写的排查顺序挑第一个,条目没写顺序的挑最常见的一个;别的不展开,只把仍符合用户情况的在短答正文末尾(「条目没有覆盖:」那一行与条目链接之前)用一行点名,最多 3 种,让用户选(例如「如果你看到的是 A 或 B,告诉我是哪个」);没有这样的备选时,最后一句告诉用户还能怎么继续。不写用户没问的提醒和注意事项;步骤之后不追加「另外检查」这类与用户说的现象无关的检查; - 只能部分回答:条目对这个问题有实质帮助(答案或排查步骤的一部分)、但答不全——回答里用了条目里的排查步骤,就按这一种作答;条目覆盖的部分按上面的短答写,并以固定前缀「条目没有覆盖:」用一句话写出缺的部分(前缀单独起一行写在行首,不写成标题);条目没写或没核实的内容只在这一行说,不在别处换成自己的话(例如「知识库里没有说…」「知识库没有核实…」);缺的部分要用自己的知识补,就在前缀后先写固定标注「以下不是知识库内容,未经核实:」再补,「以下不是知识库内容,未经核实:」不能代替前缀,自己补的只写 1–2 句; - 没有条目能回答(主题相近、却答不了用户具体问题的条目也算没有):回答以固定标注「以下不是知识库内容,未经核实:」开头——要自答,就在标注后用自己的知识回答,只写 1–2 句,并与条目内容分开;不自答,就在标注后说明知识库没有覆盖; - 与知识库相邻但刻意不做——推荐或比较机场、服务商(含宽带运营商);服务商(机场、VPS / 云服务器商)的账号与售后(续费、退款、封号,含服务商自己的群组与频道);服务端搭建与运维(VPS、面板、xray / sing-box 服务端)——不作答,也不用自己的知识补,只回答「这类问题不在本知识库的范围内。」。这条优先于前面三种回答:即使目录里有看起来相关的条目,也不按条目作答、不部分作答、不自答;相邻问题不走「没有条目能回答」那条路,带上「以下不是知识库内容,未经核实:」标注自答同样不行。 5. 不回显订阅链接、密码、令牌与密钥、节点地址和账号信息(范围同第 1 步),截图里的也一样,报错原文里的也换成「已去掉」;只链接条目里列出的官方来源和本知识库主站上的条目页面(含报错表某一句的「本句链接」);标为「信息说明」的条目不给操作步骤。
Annotations the server declares
- title: 列出知识库条目
- readOnlyHint: true
- openWorldHint: false
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 Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 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
- 0
- 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
Findings
Matches of fixed checks, with the text they matched.
- Infolist_entries
The description is 3,275 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...的也一样,报错原文里的也换成「已去掉」;只链接条目里列出的官方来源和本知识库主站上的条目页面(含报错表某一句的「本句链接」);标为「信息说明」的条目不给操作步骤。"
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.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http hub-kb https://mcp.ladderkit.dev/mcp?ch=mcp-registryclaude mcp add --transport http hub-kb https://mcp.ladderkit.dev/mcp?ch=mcp-registryRun 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__hub-kb__list_entries",
"mcp__hub-kb__get_entry"
],
"ask": [],
"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 hub-kb. 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://radar.anlyon.com/api/v1/servers/io.github.ladderkit/hub-kb/verify?hash=437847346d322fd9e43b5a3d7be21016f49667cf1f2dbd2a41b585f42b8615f0" | jq -e '.changed == false'Pinned hash 437847346d32, from Nov 20, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ladderkit/hub-kb/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ladderkit/hub-kb)Source: MCP Registry. Synced Nov 20, 2026, 16:18 UTC.
LadderKit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LadderKit MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.
Can the LadderKit MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the LadderKit MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the LadderKit MCP server have?
- 2 tools: 2 read. list_entries and get_entry.
Does the LadderKit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LadderKit MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the LadderKit MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.