Remote MCP · Endpoint

AutoPoster AI MCP server

No. AutoPoster AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent.autoposter.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.autoposter/autoposter
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
517 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Multi-platform social media post creation, scheduling, and publishing.
Listing
From the official MCP registry (active).
Recent checks of AutoPoster AI
CheckedResultHandshake
1 hour agoHandshake completed517 ms
13 hours agoHandshake completed485 ms
2 days agoHandshake completed492 ms
4 days agoHandshake completed489 ms
6 days agoHandshake completed484 ms
9 days agoHandshake completed480 ms
11 days agoHandshake completed525 ms
13 days agoHandshake completed571 ms
15 days agoHandshake completed533 ms
17 days agoHandshake completed538 ms
19 days agoHandshake completed522 ms
21 days agoHandshake completed577 ms
23 days agoHandshake completed535 ms
24 days agoHandshake completed657 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 AutoPoster AI and makes no claim about it beyond what these checks measured.