Remote MCP · Endpoint

PicSee Short Link MCP server

No. PicSee Short Link answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.picsee.io/mcp

The last check completed an MCP handshake.

Registry name
io.picsee/short-link
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
72 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Official PicSee MCP server for short links, link management, click analytics, and optional OAuth.
Listing
From the official MCP registry (active).
Recent checks of PicSee Short Link
CheckedResultHandshake
1 hour agoHandshake completed72 ms
9 days agoHandshake completed82 ms
10 days agoHandshake completed58 ms
11 days agoHandshake completed59 ms
12 days agoHandshake completed66 ms
14 days agoHandshake completed98 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed108 ms
19 days agoHandshake completed110 ms
21 days agoHandshake completed408 ms
24 days agoHandshake completed213 ms
26 days agoHandshake completed105 ms
28 days agoHandshake completed80 ms

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

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