Remote MCP · Endpoint

TicketSea MCP server

No. TicketSea answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ticketsea.com/mcp

The last check completed an MCP handshake.

Registry name
com.ticketsea/ticketsea
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
7 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Find live events, ticket price trends and each seller's tickets. Some links are affiliate links.
Listing
From the official MCP registry (active).
Recent checks of TicketSea
CheckedResultHandshake
1 hour agoHandshake completed52 ms
1 day agoFailed - the response was not JSON-RPC—
2 days agoHandshake completed54 ms
3 days agoHandshake completed42 ms
4 days agoHandshake completed85 ms
5 days agoHandshake completed57 ms
6 days agoHandshake completed863 ms
8 days agoHandshake completed81 ms
11 days agoHandshake completed1.52 s
13 days agoHandshake completed49 ms
16 days agoHandshake completed49 ms
18 days agoHandshake completed1.06 s
20 days agoHandshake completed34 ms
22 days agoHandshake completed52 ms
24 days agoHandshake completed63 ms

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

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