Remote MCP · Endpoint

AI Inbx Inbox MCP server

No — it is up, but it requires credentials. AI Inbx Inbox answered 53 minutes ago with an authentication challenge rather than a session.

Auth requiredLast checked 53 minutes ago

Server URL

https://mcp.aiinbx.com/inbox

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

Registry name
com.aiinbx/inbox
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 5 checks
Described by its publisher as
Give Claude, Cursor or any agent its own email address: send, read and reply in threads.
Listing
From the official MCP registry (active).
Recent checks of AI Inbx Inbox
CheckedResultHandshake
53 minutes agoCredentials required—
3 days agoCredentials required—
12 days agoCredentials required—
13 days agoCredentials required—
14 days agoCredentials required—

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

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