Remote MCP · Endpoint

华哥·鸣儿招投标问答 MCP server

Yes, as of 1 hour ago: the request timed out.

DownLast checked 1 hour ago

Server URL

https://hndcw.com/mcp-minger

The last check failed: the request timed out.

Registry name
io.github.mmcaoge/huage-minger-qa
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
71.4% from 14 checks
Described by its publisher as
「鸣儿」招投标智能助手:回答投标流程、资质要求、找项目、政策匹配等提问,并可联动项目库返回匹配标讯。
Listing
From the official MCP registry (active).
Recent checks of 华哥·鸣儿招投标问答
CheckedResultHandshake
1 hour agoFailed - the request timed out—
9 days agoFailed - the request timed out—
10 days agoHandshake completed1.47 s
11 days agoHandshake completed1.40 s
12 days agoHandshake completed1.12 s
14 days agoHandshake completed1.01 s
14 days agoFailed - the request timed out—
15 days agoHandshake completed1.04 s
17 days agoHandshake completed878 ms
19 days agoHandshake completed3.38 s
21 days agoHandshake completed664 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed1.00 s
28 days agoHandshake completed231 ms

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

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.