Remote MCP · Endpoint

艾达 ADA MCP server

Yes, as of 44 minutes ago: the TLS certificate could not be verified.

DownLast checked 44 minutes ago

Server URL

https://ai.hengyu.group/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
group.hengyu.ai/ada
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Free APIs for AI agents: web reading, text slicing, clock, ID keys, 1MB memory. No signup or fees.
Listing
From the official MCP registry (active).
Recent checks of 艾达 ADA
CheckedResultHandshake
44 minutes agoFailed - the TLS certificate could not be verified—
3 days agoHandshake completed924 ms
13 days agoHandshake completed839 ms
13 days agoHandshake completed849 ms
15 days agoHandshake completed906 ms
15 days agoHandshake completed802 ms
17 days agoHandshake completed805 ms
18 days agoHandshake completed805 ms
18 days agoHandshake completed1.87 s
20 days agoHandshake completed1.88 s
22 days agoHandshake completed1.84 s
25 days agoHandshake completed943 ms
27 days agoHandshake completed1.11 s
29 days agoHandshake completed860 ms

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

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 艾达 ADA and makes no claim about it beyond what these checks measured.