_ registry / mcp streamable-http · checked 2h ago

lishuhang-site-mcp

https://mcp.lishuhang.com

Registry code: 3c209a80ef89bd97

api record

航通社(书航博客 lishuhang.me + 每日 AIGC 早报)只读检索服务。先 site_overview 概览,list/search 找文章,get_article / get_daily_issue 取全文。

endpoint
https://mcp.lishuhang.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lishuhang-site-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is lishuhang-site-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does lishuhang-site-mcp have?
6 tools: site_overview, get_article, get_daily_issue, list_articles, search_articles, list_daily_issues.
Is lishuhang-site-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.7%

90 days 97.9%· all time 97.9%

latency
239ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 338 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search blog articles
  • read a daily aigc briefing
  • list articles by tag or year
  • get site overview
takes → gives
text → text, data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_articles reads open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "标题/摘要包含的关键词(粗过滤)"
        },
        "tag": {
          "type": "string",
          "description": "按标签过滤,如 featured"
        },
        "page": {
          "type": "number",
          "description": "页码,默认 1"
        },
        "year": {
          "type": "string",
          "description": "按年份过滤,如 2026"
        },
        "category": {
          "type": "string",
          "description": "按分类过滤,如 AI、科技、传媒"
        },
        "page_size": {
          "type": "number",
          "description": "每页条数,默认 20,最大 100"
        }
      }
    }
    arguments 29 lines
  • search_articles reads open 2d ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "返回条数上限,默认 10,最大 30"
        },
        "query": {
          "type": "string",
          "description": "关键词,可空格分隔多词"
        }
      }
    }
    arguments 16 lines
  • list_daily_issues reads open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "description": "页码,默认 1"
        },
        "year": {
          "type": "string",
          "description": "按年份过滤,如 2026"
        },
        "date_to": {
          "type": "string",
          "description": "截止日期 2026-09-28"
        },
        "date_from": {
          "type": "string",
          "description": "起始日期 2026-09-01"
        },
        "page_size": {
          "type": "number",
          "description": "每页条数,默认 20,最大 100"
        }
      }
    }
    arguments 25 lines
  • site_overview reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_article reads unknown 2h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "url": {
          "type": "string",
          "description": "文章页 URL(list_articles/search_articles 结果中的 url)"
        },
        "slug": {
          "type": "string",
          "description": "或直接给 _posts 文件名(如 2026-09-18-ai-duan-pian-da-sai-xian.md)"
        }
      }
    }
    arguments 13 lines
  • get_daily_issue reads unknown 2d ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "日期,支持 2026-09-28 / 2026.9.28 等写法"
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3c209a80ef89bd97.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3c209a80ef89bd97/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3c209a80ef89bd97/badge.svg)](https://brick.blue/agent/3c209a80ef89bd97?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
765ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.