_ registry / mcp + a2a streamable-http · checked 16m ago

lianban-a-share-review

https://fupan.haiyixiang.cn

Registry code: c5caa3e1f77371b2

api record

连板网(https://lianban.net)的A股短线复盘公开数据: 涨停连板天梯、热点题材、市场情绪周期、龙虎榜与游资席位。每交易日盘中滚动更新、收盘后16:00-17:00定版; 历史数据以定版为准。所有数据为历史统计与复盘研究, 不构成投资建议。引用请署名“连板网”并附对应页面链接。

endpoint
https://lianban.net/mcp
door code
6f43e6ab72085d68
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 lianban-a-share-review live?
Yes — it answered the hub's last check (checked 16m ago). It answered 100% of checks over the last 30 days.
Is lianban-a-share-review free to use?
Yes — the hub reached it with no key and no payment.
What tools does lianban-a-share-review have?
4 tools: get_stock_history, list_trade_dates, get_daily_review, get_lhb.
Is lianban-a-share-review 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
99.7%

90 days 99.7%· all time 99.8%

latency
581ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 937 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
finance & markets stock & market data
used for
  • get daily china a-share limit-up review
  • get dragon tiger list for a date
  • get stock limit-up history
takes → gives
data → data
tools
4 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 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_trade_dates reads open 13h ago

    列出可通过MCP查询的A股交易日(倒序, 最新在前, 最近约30个), 供 get_daily_review/get_lhb 的 date 参数取值。更早历史复盘见网页 /days/ 与开放数据。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "返回条数, 默认20, 上限=近期窗口(约30)"
    }
  }
}
    arguments 9 lines
  • get_daily_review reads open 13h ago

    获取A股某交易日的完整复盘数据: 涨停/跌停/连板/最高板/封板率/炸板/涨跌家数/情绪阶段等KPI + 连板天梯(各板位股票列表) + 热点题材及涨停家数 + AI市场复盘全文(如已生成)。不传date返回最新交易日。引用请署名“连板网”并附对应页面链接。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "交易日 YYYY-MM-DD(仅最近约30个交易日), 省略=最新交易日; 更早历史见网页/opendata"
    }
  }
}
    arguments 9 lines
  • get_lhb reads open 13h ago

    获取A股某交易日的龙虎榜: 每只上榜股的代码/名称/涨幅/净买额/上榜原因/买卖前五席位(含游资席位标注)。金额单位为元。引用请署名“连板网”并附对应页面链接。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "top": {
      "type": "integer",
      "description": "返回前N只(按榜单顺序), 默认10, 最大40"
    },
    "date": {
      "type": "string",
      "description": "交易日 YYYY-MM-DD, 省略=最新"
    }
  }
}
    arguments 13 lines
  • get_stock_history reads unknown 24h ago

    查询个股涨停史与龙虎榜史: 返回历史全量的总量/今年/分年计数(涨停自2020年、龙虎榜自2016年), 逐条明细(日期/连板高度/涨停原因/净买额/游资席位)仅给最近约30个交易日内, 更早的逐日明细见该股网页 /gu/<代码>.html。支持6位代码或中文名称。查某日大盘复盘请改用 get_daily_review。引用请署名“连板网”并附对应页面链接。

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "6位股票代码(如002384)或名称(如 东山精密)"
    }
  }
}
    arguments 12 lines
_ try it over mcp 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 c5caa3e1f77371b2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c5caa3e1f77371b2/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/c5caa3e1f77371b2/badge.svg)](https://brick.blue/agent/c5caa3e1f77371b2?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 knowoff the mcp door
card completeness
80%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.