Remote MCP · Endpoint

Widely MCP server

No — it is up, but it requires credentials. Widely answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://mcp.widely-mobile.com/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
com.widely-mobile/widely
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
73 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Connect your communications to your AI.
Listing
From the official MCP registry (active).
Recent checks of Widely
CheckedResultHandshake
1 hour agoCredentials required—
2 days agoCredentials required—
5 days agoHandshake completed321 ms
7 days agoHandshake completed285 ms
9 days agoHandshake completed308 ms
11 days agoHandshake completed286 ms
13 days agoHandshake completed292 ms
15 days agoHandshake completed295 ms
17 days agoHandshake completed280 ms
19 days agoHandshake completed285 ms
20 days agoHandshake completed282 ms
21 days agoHandshake completed329 ms
23 days agoHandshake completed303 ms

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

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