Remote MCP · Endpoint

Golden Flame Cologne Events MCP server

No. Golden Flame Cologne Events answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://faya.events/mcp

The last check completed an MCP handshake.

Registry name
events.faya/golden-flame
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.67 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Golden Flame events in Cologne, Germany: upcoming parties, tickets, venues and guest FAQ.
Listing
From the official MCP registry (active).
Recent checks of Golden Flame Cologne Events
CheckedResultHandshake
36 minutes agoHandshake completed1.67 s
8 days agoHandshake completed1.22 s
9 days agoHandshake completed1.27 s
11 days agoHandshake completed1.43 s
12 days agoHandshake completed1.61 s
12 days agoHandshake completed1.65 s
14 days agoHandshake completed1.50 s
14 days agoHandshake completed1.54 s
16 days agoHandshake completed1.45 s
19 days agoHandshake completed1.53 s
21 days agoHandshake completed1.39 s
24 days agoHandshake completed1.25 s
26 days agoHandshake completed1.25 s
28 days agoHandshake completed1.23 s

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

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