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.448c.org/mcp

The last check completed an MCP handshake.

Registry name
org.448c.agent-exec/agent-exec
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
297 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Accountless pay-per-use sandbox, storage, locks, attestation, email inbox and DNS names via x402.
Website
https://agent-exec.448c.org/
Listing
From the official MCP registry (active).
Recent checks of agent-exec
CheckedResultHandshake
1 hour agoHandshake completed297 ms
2 days agoHandshake completed283 ms
4 days agoHandshake completed474 ms
5 days agoHandshake completed289 ms
7 days agoHandshake completed289 ms
8 days agoHandshake completed367 ms
9 days agoHandshake completed306 ms
12 days agoHandshake completed293 ms
13 days agoHandshake completed297 ms
15 days agoHandshake completed296 ms
17 days agoHandshake completed287 ms
18 days agoHandshake completed286 ms
19 days agoHandshake completed282 ms
20 days agoHandshake completed283 ms
21 days agoHandshake completed282 ms
21 days agoHandshake completed320 ms
23 days agoHandshake completed283 ms

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

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