Remote MCP · Endpoint
GoAI Moat Social Media Content Strategy MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://social.mcp.goaimoat.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.goaimoat/social-media-strategy
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 56.3% from 16 checks
- Described by its publisher as
- Platform playbooks, rolling content calendars and video hooks for cross-border sellers
- Website
- https://goaimoat.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Handshake completed | 631 ms |
| 14 days ago | Handshake completed | 628 ms |
| 15 days ago | Handshake completed | 627 ms |
| 17 days ago | Handshake completed | 630 ms |
| 18 days ago | Handshake completed | 632 ms |
| 19 days ago | Handshake completed | 775 ms |
| 20 days ago | Handshake completed | 637 ms |
| 20 days ago | Handshake completed | 635 ms |
| 21 days ago | Handshake completed | 642 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 9 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 GoAI Moat Social Media Content Strategy and makes no claim about it beyond what these checks measured.