Remote MCP · Endpoint

The Deploy Log MCP server

No. The Deploy Log answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://deployedbyai.com/log/mcp

The last check completed an MCP handshake.

Registry name
com.deployedbyai/the-deploy-log
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI deployments that shipped and are available now, each sourced to the publisher's own page.
Listing
From the official MCP registry (active).
Recent checks of The Deploy Log
CheckedResultHandshake
1 hour agoHandshake completed324 ms
2 days agoHandshake completed42 ms
5 days agoHandshake completed191 ms
7 days agoHandshake completed250 ms
9 days agoHandshake completed164 ms
11 days agoHandshake completed191 ms
13 days agoHandshake completed67 ms
15 days agoHandshake completed86 ms
17 days agoHandshake completed173 ms
18 days agoHandshake completed247 ms
20 days agoHandshake completed177 ms
21 days agoHandshake completed254 ms
23 days agoHandshake completed132 ms
25 days agoHandshake completed150 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 The Deploy Log and makes no claim about it beyond what these checks measured.