Remote MCP · Endpoint

Wagent MCP server

Yes, as of 5 hours ago: the server returned an HTTP error.

DownLast checked 5 hours ago

Server URL

https://mcp.wagent.sh/c/%7Bconnection_id%7D/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.deepa-wagent/wagent
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
WhatsApp MCP server with per-chat permissions. Agents see only chats you allow; sends wait for you.
Listing
From the official MCP registry (active).
Recent checks of Wagent
CheckedResultHandshake
5 hours agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—

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

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