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
376 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Schedule and publish to LinkedIn, X, and Threads from your AI. Content calendar, approval-first.
Listing
From the official MCP registry (active).
Recent checks of com.feedsquad/feedsquad
CheckedResultHandshake
1 hour agoHandshake completed376 ms
2 days agoHandshake completed186 ms
4 days agoHandshake completed207 ms
5 days agoHandshake completed536 ms
7 days agoHandshake completed213 ms
8 days agoHandshake completed337 ms
9 days agoHandshake completed385 ms
12 days agoHandshake completed282 ms
13 days agoHandshake completed196 ms
15 days agoHandshake completed197 ms
16 days agoHandshake completed273 ms
17 days agoHandshake completed186 ms
18 days agoHandshake completed194 ms
19 days agoHandshake completed278 ms
20 days agoHandshake completed197 ms
21 days agoHandshake completed190 ms
22 days agoHandshake completed418 ms

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

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.