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

quanlian-qingbao

https://lian.yisuncloud.com

Registry code: a0ba4cf9095e2981

api record

全链传导 MCP：先 intel_availability，再 intel_chain / signal / heal / brief。需 API Key（配置 MCP_HTTP_API_KEY 或请求头 X-Intel-Key / Bearer）。

endpoint
https://lian.yisuncloud.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 quanlian-qingbao live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is quanlian-qingbao free to use?
Not measured yet.
What tools does quanlian-qingbao have?
5 tools: intel_availability, intel_chain, intel_signal, intel_heal, intel_brief.
Is quanlian-qingbao 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
100%

90 days 100%· all time 100%

latency
871ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
5 never probed 0 of 5 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.

  • intel_availability unknown never probed

    [v1.2.0] 先查：available_now、coverage、requires_trigger。建议再调 chain/signal/brief。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名，如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai；与 entity 二选一或并用"
    }
  }
}
    arguments 13 lines
  • intel_chain unknown never probed

    [v1.2.0] 全链：timeline、delta_days、vs_prior（≈get_chain）。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名，如 OpenAI、华为、台积电"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai；与 entity 二选一或并用"
    }
  }
}
    arguments 13 lines
  • intel_signal unknown never probed

    [v1.2.0] 规则缺口（≈list_signals）：落地/商业化/技术缺口。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名，如 OpenAI、华为、台积电"
    },
    "window": {
      "type": "number",
      "description": "近窗天数 7–90"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai；与 entity 二选一或并用"
    }
  }
}
    arguments 17 lines
  • intel_heal unknown never probed

    [v1.2.0] 缺口愈合：healed / persistent / new。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "实体名，如 OpenAI、华为、台积电"
    },
    "window": {
      "type": "number",
      "description": "近窗天数 7–90"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai；与 entity 二选一或并用"
    }
  }
}
    arguments 17 lines
  • intel_brief unknown never probed

    [v1.2.0] 企业短板组合叙事（模板，非大模型）。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "heal": {
      "type": "string",
      "description": "传 0 可跳过愈合快照写入"
    },
    "entity": {
      "type": "string",
      "description": "实体名，如 OpenAI、华为、台积电"
    },
    "window": {
      "type": "number",
      "description": "近窗天数 7–90"
    },
    "entity_id": {
      "type": "string",
      "description": "如 ent_openai；与 entity 二选一或并用"
    }
  }
}
    arguments 21 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 a0ba4cf9095e2981.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a0ba4cf9095e2981/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/a0ba4cf9095e2981/badge.svg)](https://brick.blue/agent/a0ba4cf9095e2981?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
90%

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.