Remote MCP · Endpoint
com.feedsquad/feedsquad MCP server
No. com.feedsquad/feedsquad answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://feedsquad.com/api/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- com.feedsquad/feedsquad
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 361 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Schedule and publish to LinkedIn, X, and Threads from your AI. Content calendar, approval-first.
- Website
- https://feedsquad.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 361 ms |
| 18 hours ago | Handshake completed | 380 ms |
| 2 days ago | Handshake completed | 346 ms |
| 3 days ago | Handshake completed | 463 ms |
| 4 days ago | Handshake completed | 355 ms |
| 5 days ago | Handshake completed | 396 ms |
| 6 days ago | Handshake completed | 369 ms |
| 7 days ago | Handshake completed | 316 ms |
| 10 days ago | Handshake completed | 424 ms |
| 13 days ago | Handshake completed | 656 ms |
| 15 days ago | Handshake completed | 520 ms |
| 17 days ago | Handshake completed | 216 ms |
| 19 days ago | Handshake completed | 216 ms |
| 21 days ago | Handshake completed | 376 ms |
| 23 days ago | Handshake completed | 186 ms |
| 25 days ago | Handshake completed | 207 ms |
| 27 days ago | Handshake completed | 536 ms |
| 28 days ago | Handshake completed | 213 ms |
| 29 days ago | Handshake completed | 337 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 com.feedsquad/feedsquad and makes no claim about it beyond what these checks measured.