Remote MCP · Endpoint

One Agent a Day MCP server

No. One Agent a Day answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://oneagentaday.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.oneagentaday/agents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
424 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and fetch 40+ free AI agent prompts. A new one is added every day.
Listing
From the official MCP registry (active).
Recent checks of One Agent a Day
CheckedResultHandshake
53 minutes agoHandshake completed424 ms
3 days agoHandshake completed722 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed190 ms
15 days agoHandshake completed215 ms
15 days agoHandshake completed220 ms
17 days agoHandshake completed363 ms
18 days agoHandshake completed195 ms
18 days agoHandshake completed193 ms
20 days agoHandshake completed301 ms
22 days agoHandshake completed197 ms
25 days agoHandshake completed222 ms
27 days agoHandshake completed228 ms
29 days agoHandshake completed256 ms

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

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