Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.lishuhang/site-mcp

REMOTE · MCP.LISHUHANG.COM · SCANNED SEP 29

航通社官网(lishuhang.me,书航博客 + 每日 AIGC 早报)只读检索:文章与早报列表、关键词搜索、单篇全文 markdown。Streamable HTTP,免鉴权,无状态。

66 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 588 tokens (~98/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the io.github.lishuhang/site-mcp server?

io.github.lishuhang/site-mcp is a hosted endpoint at https://mcp.lishuhang.com/mcp, 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.lishuhang.com

# add to Claude Code
claude mcp add --transport http lishuhang-site-mcp 'https://mcp.lishuhang.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "lishuhang-site-mcp": {
      "url": "https://mcp.lishuhang.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lishuhang-site-mcp": {
      "type": "http",
      "url": "https://mcp.lishuhang.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.lishuhang-site-mcp]
url = "https://mcp.lishuhang.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lishuhang-site-mcp": {
      "type": "remote",
      "url": "https://mcp.lishuhang.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lishuhang-site-mcp --url 'https://mcp.lishuhang.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  lishuhang-site-mcp:
    url: "https://mcp.lishuhang.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lishuhang-site-mcp": {
      "Transport": "http",
      "Url": "https://mcp.lishuhang.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add lishuhang-site-mcp -t streamable-http -u 'https://mcp.lishuhang.com/mcp'
// mcp.json
{
  "mcpServers": {
    "lishuhang-site-mcp": {
      "type": "http",
      "url": "https://mcp.lishuhang.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 29 Sept 26 66

    First indexed and scored.

Diagnostics

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 29 Sept 2026 · Probed https://mcp.lishuhang.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lishuhang.com CN=WE1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 e1eb17b1e4579a53135cfe3a62ffbc2f
SANs: lishuhang.com, mcp.lishuhang.com, *.mcp.lishuhang.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.lishuhang.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
lishuhang.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=0; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.lishuhang.com/mcp Verified 200
http (plaintext) http://mcp.lishuhang.com/mcp HTTPS enforced 301 https://mcp.lishuhang.com/mcp
MCP tools · 6 exposed · ~533 tokens

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 →

Tool Tokens
get_article ~83

取航通社单篇文章全文 markdown(含 front matter、正文与发布日期标注)。

NameTypeReqDescription
slugstring–或直接给 _posts 文件名(如 2026-09-18-ai-duan-pian-da-sai-xian.md)
urlstring–文章页 URL(list_articles/search_articles 结果中的 url)

No output schema declared.

No examples provided.

get_daily_issue ~67

取「每日 AIGC 早报」单期全文 markdown(同日重发不覆盖,以每日首次同步版本为准)。

NameTypeReqDescription
datestringyes日期,支持 2026-09-28 / 2026.9.28 等写法

No output schema declared.

No examples provided.

list_articles ~132

分页浏览航通社全站文章(按发布时间倒序)。支持按分类、标签、年份、关键词过滤。不返回正文。

NameTypeReqDescription
categorystring–按分类过滤,如 AI、科技、传媒
pagenumber–页码,默认 1
page_sizenumber–每页条数,默认 20,最大 100
qstring–标题/摘要包含的关键词(粗过滤)
tagstring–按标签过滤,如 featured
yearstring–按年份过滤,如 2026

No output schema declared.

No examples provided.

list_daily_issues ~124

分页浏览「每日 AIGC 早报」期号(按日期倒序)。支持按年份与日期区间过滤。

NameTypeReqDescription
date_fromstring–起始日期 2026-09-01
date_tostring–截止日期 2026-09-28
pagenumber–页码,默认 1
page_sizenumber–每页条数,默认 20,最大 100
yearstring–按年份过滤,如 2026

No output schema declared.

No examples provided.

search_articles ~76

关键词搜索航通社全站文章(标题加权、标签/分类次之、摘要兜底),返回命中列表与评分。

NameTypeReqDescription
limitnumber–返回条数上限,默认 10,最大 30
querystringyes关键词,可空格分隔多词

No output schema declared.

No examples provided.

site_overview ~51

航通社(lishuhang.me,书航的博客)站点概览:文章与早报总数、最新内容、全部 agent 入口。首次接触本站时调用。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.lishuhang/site-mcp server?

io.github.lishuhang/site-mcp is listed in the public MCP registry as io.github.lishuhang/site-mcp. 航通社官网(lishuhang.me,书航博客 + 每日 AIGC 早报)只读检索:文章与早报列表、关键词搜索、单篇全文 markdown。Streamable HTTP,免鉴权,无状态。 This page covers its hosted endpoint (https://mcp.lishuhang.com/mcp).

Is the io.github.lishuhang/site-mcp server safe to use?

io.github.lishuhang/site-mcp scores 66 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 io.github.lishuhang/site-mcp server expose?

io.github.lishuhang/site-mcp exposes 6 tools: site_overview, list_articles, search_articles, get_article, list_daily_issues, get_daily_issue. Their descriptions and schemas cost roughly 533 tokens of context every time the server is loaded.

Does the io.github.lishuhang/site-mcp server require authentication?

No. We connected to io.github.lishuhang/site-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.lishuhang/site-mcp server still maintained?

io.github.lishuhang/site-mcp is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.