Remote MCP · Endpoint

agent-exec MCP server

No. agent-exec answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-exec.45.67.221.128.sslip.io/mcp

The last check completed an MCP handshake.

Registry name
io.sslip.128.221.67.45.agent-exec/agent-exec
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
719 ms
Tools exposed
54 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Accountless pay-per-use sandbox execution, storage, locks, attestation and handoff; pay via x402.
Listing
From the official MCP registry (active).
Recent checks of agent-exec
CheckedResultHandshake
1 hour agoHandshake completed719 ms
9 days agoHandshake completed627 ms
10 days agoHandshake completed644 ms
11 days agoHandshake completed744 ms
12 days agoHandshake completed896 ms
14 days agoHandshake completed665 ms
14 days agoHandshake completed612 ms
15 days agoHandshake completed691 ms
17 days agoHandshake completed633 ms
19 days agoHandshake completed672 ms
21 days agoHandshake completed686 ms
24 days agoHandshake completed684 ms
26 days agoHandshake completed605 ms
28 days agoHandshake completed670 ms

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

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