Remote MCP · Endpoint

Universal Agents MCP server

No. Universal Agents answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://universalagents.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.universalagents/universal-agents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ask Universal Agents what we sell (Interplay), pricing, and FAQs; draft an intro email.
Listing
From the official MCP registry (active).
Recent checks of Universal Agents
CheckedResultHandshake
2 hours agoHandshake completed90 ms
2 days agoHandshake completed123 ms
4 days agoHandshake completed109 ms
6 days agoHandshake completed708 ms
8 days agoHandshake completed109 ms
10 days agoHandshake completed897 ms
12 days agoHandshake completed133 ms
13 days agoHandshake completed804 ms
14 days agoHandshake completed121 ms
16 days agoHandshake completed107 ms
18 days agoHandshake completed765 ms
20 days agoHandshake completed526 ms
21 days agoHandshake completed776 ms
23 days agoHandshake completed897 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 Universal Agents and makes no claim about it beyond what these checks measured.