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

tianji-wsa-mcp

https://api.wsa.cloud.tencent.com

Registry code: 0d4ef698611e3882

api record

联网搜索MCP(Model Context Protocol,MCP)基于腾讯云产品-封装而成,底层搜索引擎来源于搜狗搜索,以互联网全网公开资源为基础,实现了从收录至召回排序全链路的智能搜索增强。合作伙伴通过检索词请求接口,以JSON形式返回搜索结果对应的排序信息、数据字段,可在业务场景中结合搜索结果的内容,扩充信息内容源,丰富展现效果,提升用户的查询满意度。

from a public catalogue that lists it, not from the operator

endpoint
https://api.wsa.cloud.tencent.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 tianji-wsa-mcp live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is tianji-wsa-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does tianji-wsa-mcp have?
1 tool: SearchPro.
Is tianji-wsa-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
100%

90 days 100%· all time 100%

latency
1,559ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 2 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 1 tools
1 auth-required 1 of 1 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.

  • SearchPro auth-required 11h ago

    联网搜索API,根据查询词返回相关网页内容。

    mcp-tool

    {
      "type": "object",
      "required": [
        "Query"
      ],
      "properties": {
        "Cnt": {
          "enum": [
            10,
            20,
            30,
            40,
            50
          ],
          "type": "integer",
          "description": "返回结果条数,取值 10/20/30/40/50。"
        },
        "Mode": {
          "enum": [
            0,
            1,
            2
          ],
          "type": "integer",
          "description": "返回结果类型,不传默认为0。取值:0,公开网页信源结果;1,优质权威垂直信源结果(如天气、金价、股价等实时垂直权威信息);2,混合结果。"
        },
        "Site": {
          "type": "string",
          "description": "站点过滤,限定在指定站点内搜索。示例:zhihu.com"
        },
        "Query": {
          "type": "string",
          "description": "搜索词/查询词。必填,UTF-8 字节数不超过 1500(约 500 个中英文字符)。示例:今天北京的天气"
        },
        "Industry": {
          "enum": [
            "news",
            "acad",
            "finance",
            "gov"
          ],
          "type": "string",
          "description": "垂直领域搜索。示例:gov/news/acad/finance,分别对应党政机关、权威媒体、学术(英文)、金融。"
        },
        "Freshness": {
          "type": "string",
          "description": "搜索时效范围。示例:d[N]表示搜索最近N天,N取值1-30整数;m[N]表示搜索最近N月,N取值1-12整数;y[N]表示搜索最近N年,N取值1-5整数。例如,2026.6.10分别传参d7/m3/y1进行搜索,则搜索结果的时间范围分别为“2026.6.10-2026.6.4”/“2026.6.10-2026.4.1”/“2026”,以此类推。"
        }
      }
    }
    arguments 50 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 0d4ef698611e3882.

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

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.

_ also on tencent.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.