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

外部接口服务

https://mcp.traveldaily.cn

Registry code: 61b616f6c17430c1

api record
endpoint
https://mcp.traveldaily.cn/mcp/public_traveldaily
protocol
streamable-http ·2024-11-05
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 外部接口服务 live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is 外部接口服务 free to use?
Yes — the hub reached it with no key and no payment.
What tools does 外部接口服务 have?
6 tools: news_detail, report_detail, news_list, news_search, report_search, report_list.
Is 外部接口服务 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
2,624ms

last good check

priced tools
0

of 6 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 6 tools
4 open 2 never probed 4 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.

  • news_list open 11h ago

    获取新闻列表,支持按分类、头条、推荐筛选。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "description": "页码,默认1"
        },
        "category": {
          "type": "number",
          "description": "分类ID筛选"
        },
        "pageSize": {
          "type": "number",
          "description": "每页条数,默认10"
        },
        "isHeadline": {
          "type": "boolean",
          "description": "是否只看头条"
        },
        "isRecommend": {
          "type": "boolean",
          "description": "是否只看推荐"
        }
      }
    }
    arguments 25 lines
  • news_search open 11h ago

    通过 Elasticsearch 全文搜索新闻标题、摘要、内容,支持分类筛选、分页与高亮。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "description": "页码,默认1"
        },
        "keyword": {
          "type": "string",
          "description": "搜索关键词"
        },
        "category": {
          "type": "number",
          "description": "分类ID筛选,可选"
        },
        "pageSize": {
          "type": "number",
          "description": "每页条数,默认10"
        }
      }
    }
    arguments 21 lines
  • report_search open 11h ago

    通过 Elasticsearch 按关键词搜索报告名称和简介,支持分类筛选、分页与高亮。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "description": "页码,默认1"
        },
        "keyword": {
          "type": "string",
          "description": "搜索关键词"
        },
        "category": {
          "type": "number",
          "description": "分类ID筛选,可选"
        },
        "pageSize": {
          "type": "number",
          "description": "每页条数,默认10"
        }
      }
    }
    arguments 21 lines
  • report_list open 38h ago

    获取报告列表,支持按分类、类型、是否付费筛选。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "description": "页码,默认1"
        },
        "type": {
          "type": "number",
          "description": "报告类型"
        },
        "isPaid": {
          "type": "number",
          "description": "是否付费:1付费,0免费"
        },
        "category": {
          "type": "number",
          "description": "分类ID筛选"
        },
        "pageSize": {
          "type": "number",
          "description": "每页条数,默认10"
        }
      }
    }
    arguments 25 lines
  • news_detail unknown never probed

    根据新闻ID获取新闻详情内容。

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "number",
          "description": "新闻ID"
        }
      }
    }
    arguments 12 lines
  • report_detail unknown never probed

    根据报告ID获取报告详情内容。

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "number",
          "description": "报告ID"
        }
      }
    }
    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 61b616f6c17430c1.

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