Remote MCP · Endpoint

Eventbrite MCP server

No. Eventbrite answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/eventbrite/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/eventbrite
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
933 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Eventbrite MCP.
Listing
From the official MCP registry (active).
Recent checks of Eventbrite
CheckedResultHandshake
42 minutes agoHandshake completed933 ms
8 days agoHandshake completed655 ms
9 days agoHandshake completed87 ms
11 days agoHandshake completed119 ms
12 days agoHandshake completed150 ms
13 days agoHandshake completed130 ms
14 days agoHandshake completed194 ms
15 days agoHandshake completed131 ms
16 days agoHandshake completed331 ms
19 days agoHandshake completed60 ms
22 days agoHandshake completed70 ms
24 days agoHandshake completed68 ms
26 days agoHandshake completed91 ms
28 days agoHandshake completed67 ms

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