Remote MCP · Endpoint

TicketsMinistry events MCP server

No. TicketsMinistry events answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.ticketsministry.com/mcp

The last check completed an MCP handshake.

Registry name
com.ticketsministry.ai/events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
271 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search live events in Sri Lanka: dates, venues, ticket tiers, prices and help articles.
Listing
From the official MCP registry (active).
Recent checks of TicketsMinistry events
CheckedResultHandshake
1 hour agoHandshake completed271 ms
6 hours agoHandshake completed268 ms
2 days agoHandshake completed249 ms
4 days agoHandshake completed324 ms
7 days agoHandshake completed354 ms
9 days agoHandshake completed314 ms
11 days agoHandshake completed244 ms
13 days agoHandshake completed358 ms
15 days agoHandshake completed451 ms
17 days agoHandshake completed310 ms
19 days agoHandshake completed255 ms
21 days agoHandshake completed351 ms
23 days agoHandshake completed423 ms
24 days agoHandshake completed295 ms
25 days agoHandshake completed295 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 TicketsMinistry events and makes no claim about it beyond what these checks measured.