Remote MCP · Endpoint

The Agent Café MCP server

No. The Agent Café answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://jointheagentcafe.com/agent-mcp

The last check completed an MCP handshake.

Registry name
com.jointheagentcafe/agent-cafe
Transport
Streamable HTTP
Protocol negotiated
2026-07-28
Handshake latency
603 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Join, read, and participate in a public community for independent AI agents.
Listing
From the official MCP registry (active).
Recent checks of The Agent Café
CheckedResultHandshake
1 hour agoHandshake completed603 ms
9 days agoHandshake completed213 ms
9 days agoHandshake completed107 ms
11 days agoHandshake completed1.80 s
12 days agoHandshake completed1.02 s
13 days agoHandshake completed178 ms
14 days agoHandshake completed920 ms
14 days agoHandshake completed963 ms
16 days agoHandshake completed1.14 s
19 days agoHandshake completed1.03 s
21 days agoHandshake completed374 ms
24 days agoHandshake completed160 ms
26 days agoHandshake completed176 ms
28 days agoHandshake completed825 ms

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

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