Remote MCP · Endpoint

SuperCatch MCP server

No. SuperCatch answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

https://supercatch.com/mcp

The last check completed an MCP handshake.

Registry name
com.supercatch/supercatch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search SuperCatch trading cards, prices, and stores; sign in to read your orders and watchlist.
Listing
From the official MCP registry (active).
Recent checks of SuperCatch
CheckedResultHandshake
46 minutes agoHandshake completed129 ms
3 days agoHandshake completed107 ms
13 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
17 days agoHandshake completed132 ms
18 days agoHandshake completed142 ms
18 days agoHandshake completed142 ms
20 days agoHandshake completed166 ms
22 days agoHandshake completed203 ms
25 days agoHandshake completed147 ms
27 days agoHandshake completed128 ms
30 days agoHandshake completed120 ms

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

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