Remote MCP · Endpoint

Feeds MCP server

No. Feeds answered an MCP handshake 42 minutes ago.

Up · key neededLast checked 42 minutes ago

Server URL

https://feeds.worker.mymarketing.click/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
click.mymarketing/feeds
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Peças, referências, agenda e publicação nas redes
Listing
From the official MCP registry (active).
Recent checks of Feeds
CheckedResultHandshake
42 minutes agoHandshake completed160 ms
3 days agoHandshake completed333 ms
12 days agoHandshake completed388 ms
12 days agoHandshake completed76 ms
14 days agoHandshake completed75 ms
15 days agoHandshake completed924 ms
16 days agoHandshake completed791 ms
17 days agoHandshake completed460 ms
18 days agoHandshake completed337 ms
19 days agoHandshake completed116 ms
22 days agoHandshake completed462 ms
25 days agoHandshake completed325 ms
27 days agoHandshake completed367 ms

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

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