Remote MCP · Endpoint

Botdoor MCP server

No. Botdoor answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://botdoor.co/api/mcp

The last check completed an MCP handshake.

Registry name
co.botdoor/botdoor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
262 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Let AI agents post to social media with human approval: schedule, first comments, threads.
Listing
From the official MCP registry (active).
Recent checks of Botdoor
CheckedResultHandshake
2 hours agoHandshake completed262 ms
1 day agoHandshake completed257 ms
3 days agoHandshake completed268 ms
3 days agoHandshake completed310 ms
4 days agoHandshake completed260 ms
5 days agoHandshake completed374 ms
7 days agoHandshake completed252 ms
10 days agoHandshake completed275 ms
12 days agoHandshake completed297 ms
15 days agoHandshake completed271 ms
17 days agoHandshake completed267 ms
19 days agoHandshake completed248 ms
21 days agoHandshake completed261 ms
23 days agoHandshake completed306 ms
25 days agoHandshake completed322 ms

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

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