Golden Flame Cologne Events
REMOTE · FAYA.EVENTS
Golden Flame events in Cologne, Germany: upcoming parties, tickets, venues and guest FAQ.
Available components
Last scanned (6 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 362 tokens (~72/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://faya.events/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=faya.events | CN=YE2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60f65717d0bd1bbbb8a3d00a09f021a59e0 |
| SANs: faya.events | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of faya.events. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| events. | present | 12487 | 8 | Verified |
| faya.events. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | object-src 'none'; base-uri 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://faya.events/mcp | Verified | 200 | |
| http (plaintext) | http://faya.events/mcp | HTTPS enforced | 301 | https://faya.events/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask ~105
Ask any question about Golden Flame events in Cologne: dates, tickets, box office, age limit, dress code, costumes, music, getting there, getting home at night, coming alone or with a group – or about going out in Köln. Answers come only from official, published Golden Flame information, each with a source link. Stelle jede Frage zu Golden-Flame-Events oder zum Ausgehen in Köln; Antworten nur aus offiziellen Angaben, mit Quelle.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
No output schema declared.
No examples provided.
get_event ~34
Details of one Golden Flame event by id (from list_events). Details zu einem Event.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
get_tickets ~38
Official ticket link and sales status for a Golden Flame event. Offizieller Ticket-Link und Verkaufsstatus.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
list_events ~63
Upcoming public Golden Flame events in Cologne (Köln) with date, time, venue, age limit, dress code, price and ticket link. Anstehende Golden-Flame-Events in Köln mit Datum, Ort, Alter, Dresscode, Preis und Ticket-Link.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~69
Search Golden Flame events, event series and guides about going out in Cologne, e.g. "Halloween party Köln ab 18", "Maskenball Köln", "Party am Rhein", "Party Hauptbahnhof Köln". Suche in Events, Reihen und Köln-Guides.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Golden Flame Cologne Events MCP server?
Golden Flame Cologne Events is a hosted endpoint at https://faya.events/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · faya.events
claude mcp add --transport http events-faya-golden-flame 'https://faya.events/mcp'
What is the Golden Flame Cologne Events MCP server?
Golden Flame Cologne Events is an MCP server listed in the public MCP registry as events.faya/golden-flame. Golden Flame events in Cologne, Germany: upcoming parties, tickets, venues and guest FAQ. This page covers its hosted endpoint (https://faya.events/mcp).
Is the Golden Flame Cologne Events MCP server safe to use?
Golden Flame Cologne Events scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Golden Flame Cologne Events MCP server expose?
Golden Flame Cologne Events exposes 5 tools: ask, list_events, get_event, get_tickets, search. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.
Does the Golden Flame Cologne Events MCP server require authentication?
No. We connected to Golden Flame Cologne Events without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Golden Flame Cologne Events MCP server still maintained?
Golden Flame Cologne Events is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.