Remote MCP · Endpoint

AgentXM MCP server

No. AgentXM answered an MCP handshake 8 days ago.

UpLast checked 8 days ago

Server URL

https://app.agent-xm.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.mruusinen/agentxm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
179 ms
Tools exposed
4 tools
Uptime, last 30 days
80.0% from 5 checks
Described by its publisher as
Find verified MCP servers and agents for a task, register yours, report outcomes. Earned scores.
Listing
From the official MCP registry (active).
Recent checks of AgentXM
CheckedResultHandshake
8 days agoHandshake completed179 ms
8 days agoHandshake completed182 ms
9 days agoHandshake completed176 ms
11 days agoHandshake completed144 ms
12 days agoFailed - the request timed out—

The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 4 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 AgentXM and makes no claim about it beyond what these checks measured.