Remote MCP · Endpoint

华哥·全国招投标数据 MCP server

No. 华哥·全国招投标数据 answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://hndcw.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.mmcaoge/huage-bidding-data
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
2.55 s
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
查询 hndcw.com 全国政府招投标 / 建设项目库,可按关键词、省份、城市、行业、预算区间筛选,返回项目标题、地区、预算(万元)、业主单位、阶段、公告日期与原文链接。
Listing
From the official MCP registry (active).
Recent checks of 华哥·全国招投标数据
CheckedResultHandshake
2 hours agoHandshake completed2.55 s
2 days agoFailed - the request timed out—
4 days agoHandshake completed1.84 s
6 days agoHandshake completed710 ms
8 days agoHandshake completed704 ms
10 days agoHandshake completed679 ms
13 days agoHandshake completed708 ms
14 days agoHandshake completed2.67 s
16 days agoHandshake completed864 ms
17 days agoHandshake completed931 ms
18 days agoHandshake completed4.12 s
21 days agoHandshake completed696 ms
22 days agoHandshake completed682 ms
24 days agoHandshake completed725 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with 华哥·全国招投标数据 and makes no claim about it beyond what these checks measured.