Remote MCP · Endpoint

Links MCP server

No. Links answered an MCP handshake 42 minutes ago.

Up · key neededLast checked 42 minutes ago

Server URL

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

The handshake completes, but listing its tools needs credentials.

Registry name
click.mymarketing/links
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
430 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Links curtos, cliques e campanhas
Listing
From the official MCP registry (active).
Recent checks of Links
CheckedResultHandshake
42 minutes agoHandshake completed430 ms
3 days agoHandshake completed66 ms
12 days agoHandshake completed236 ms
12 days agoHandshake completed85 ms
14 days agoHandshake completed81 ms
15 days agoHandshake completed295 ms
16 days agoHandshake completed199 ms
17 days agoHandshake completed191 ms
18 days agoHandshake completed208 ms
19 days agoHandshake completed158 ms
22 days agoHandshake completed144 ms
25 days agoHandshake completed71 ms
27 days agoHandshake completed513 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 Links and makes no claim about it beyond what these checks measured.