Remote MCP · Endpoint

SPOE MCP server

No. SPOE answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://spoe.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.spoe/spoe
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
634 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check a name on 29 platforms and the domains; build and follow apps you own on SPOE.
Website
https://spoe.ai/docs/api#mcp
Listing
From the official MCP registry (active).
Recent checks of SPOE
CheckedResultHandshake
20 minutes agoHandshake completed634 ms
9 days agoHandshake completed665 ms
9 days agoHandshake completed621 ms
11 days agoHandshake completed638 ms
12 days agoHandshake completed621 ms
13 days agoHandshake completed646 ms
14 days agoHandshake completed818 ms
15 days agoHandshake completed665 ms
16 days agoHandshake completed625 ms
19 days agoHandshake completed627 ms
21 days agoHandshake completed665 ms
24 days agoHandshake completed629 ms
26 days agoHandshake completed628 ms
28 days agoHandshake completed619 ms

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

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