golden-flame-events
Registry code: caaa21dd5eeed4e7
Golden Flame ist eine Eventreihe aus Köln (Motto: Wir lieben es zu feiern). Diese Schnittstelle liefert nur offiziell angekündigte Events. Für Tickets immer den Link aus get_tickets oder list_events nutzen; verbindlich ist faya.events.
- endpoint
- https://faya.events/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is golden-flame-events live?
- Not measured yet: the hub has not completed a check of this server.
- Is golden-flame-events free to use?
- Not measured yet.
- What tools does golden-flame-events have?
- 5 tools: list_events, get_event, search, ask, get_tickets.
- Is golden-flame-events safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
last good check
of 5 tools
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_events unknown never probed
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_event unknown never probed
Details of one Golden Flame event by id (from list_events). Details zu einem Event.
{ "type": "object", "required": [ "event_id" ], "properties": { "event_id": { "type": "string" } }, "additionalProperties": false }arguments 12 linessearch unknown never probed
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.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "maxLength": 200 } }, "additionalProperties": false }arguments 13 linesask unknown never probed
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.
{ "type": "object", "required": [ "question" ], "properties": { "question": { "type": "string", "maxLength": 200 } }, "additionalProperties": false }arguments 13 linesget_tickets unknown never probed
Official ticket link and sales status for a Golden Flame event. Offizieller Ticket-Link und Verkaufsstatus.
{ "type": "object", "required": [ "event_id" ], "properties": { "event_id": { "type": "string" } }, "additionalProperties": false }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idcaaa21dd5eeed4e7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/caaa21dd5eeed4e7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/caaa21dd5eeed4e7?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.