Remote MCP · Endpoint

Every MCP MCP server

No. Every MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://everymcp.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.everymcp/every-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
169 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search the public universe of MCP servers. This data comes from the Official MCP Registry.
Website
https://everymcp.ai/
Listing
From the official MCP registry (active).
Recent checks of Every MCP
CheckedResultHandshake
1 hour agoHandshake completed169 ms
2 days agoHandshake completed226 ms
5 days agoHandshake completed129 ms
7 days agoHandshake completed258 ms
9 days agoHandshake completed159 ms
11 days agoHandshake completed101 ms
13 days agoHandshake completed170 ms
15 days agoHandshake completed159 ms
18 days agoHandshake completed119 ms
19 days agoHandshake completed150 ms
20 days agoHandshake completed154 ms
22 days agoHandshake completed460 ms
23 days agoHandshake completed233 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Every MCP and makes no claim about it beyond what these checks measured.