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).
| Checked | Result | Handshake |
|---|---|---|
| 42 minutes ago | Handshake completed | 430 ms |
| 3 days ago | Handshake completed | 66 ms |
| 12 days ago | Handshake completed | 236 ms |
| 12 days ago | Handshake completed | 85 ms |
| 14 days ago | Handshake completed | 81 ms |
| 15 days ago | Handshake completed | 295 ms |
| 16 days ago | Handshake completed | 199 ms |
| 17 days ago | Handshake completed | 191 ms |
| 18 days ago | Handshake completed | 208 ms |
| 19 days ago | Handshake completed | 158 ms |
| 22 days ago | Handshake completed | 144 ms |
| 25 days ago | Handshake completed | 71 ms |
| 27 days ago | Handshake completed | 513 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.