arclight
Registry code: cfa48fb71c592c11
Arclight aggregates real, upcoming events across 50 metros from live sources (Luma, Ticketmaster, SeatGeek, Skiddle, confs.tech and more) and links back to each one. Start with arclight_list_cities if unsure a city is covered, then arclight_search_events. Every listing is real — never invent an event, a time or a price; if a search returns nothing, say so.
- endpoint
- https://arclight.events/api/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 arclight live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is arclight free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does arclight have?
- 4 tools: arclight_get_event, arclight_city_picks, arclight_search_events, arclight_list_cities.
- Is arclight 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.
90 days 98.9%· all time 98.9%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search upcoming events in a city
- get curated event picks
- get event details
- list covered cities
- takes → gives
- text → data
- tools
- 4 reads
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.
arclight_list_cities reads open 9h ago
List every metro Arclight covers, with the slug to pass to the other tools, plus the available topic filters. Call this first when unsure whether a city is covered. Read-only, no arguments required.
{ "type": "object", "properties": { "response_format": { "enum": [ "markdown", "json" ], "type": "string", "default": "markdown", "description": "Output format. 'markdown' to read back to a person, 'json' to compute over." } }, "additionalProperties": false }arguments 15 linesarclight_get_event reads unknown 17h ago
Fetch the full detail of one event by its Arclight slug (or its arclight.events URL): title, start time in the venue's own timezone, price, tags, description and the source link. Read-only.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Event slug, or the full arclight.events/event/<slug> URL." }, "response_format": { "enum": [ "markdown", "json" ], "type": "string", "default": "markdown", "description": "Output format. 'markdown' to read back to a person, 'json' to compute over." } }, "additionalProperties": false }arguments 22 linesarclight_city_picks reads unknown 9h ago
A small curated set of events worth going to in a city over the next few days, chosen for variety rather than raw recency. Use when someone asks what is worth doing rather than for an exhaustive list. Read-only.
{ "type": "object", "required": [ "city" ], "properties": { "city": { "type": "string", "description": "City slug or name." }, "limit": { "type": "integer", "default": 3, "maximum": 10, "minimum": 1, "description": "How many picks to return. Capped at 10 on purpose — this is a curated shortlist chosen for variety, not a search. Use arclight_search_events when an exhaustive list is wanted." }, "response_format": { "enum": [ "markdown", "json" ], "type": "string", "default": "markdown", "description": "Output format. 'markdown' to read back to a person, 'json' to compute over." } }, "additionalProperties": false }arguments 29 linesarclight_search_events reads unknown 9h ago
Search real, upcoming events in a city, optionally narrowed to a topic and timeframe. Every event is aggregated from a live source (Luma, Ticketmaster, SeatGeek, Skiddle, confs.tech and others) and links back to it — Arclight never invents listings and holds no tickets. Read-only. Returns paginated results with has_more/next_offset.
{ "type": "object", "required": [ "city" ], "properties": { "city": { "type": "string", "description": "City slug or name, e.g. \"san-francisco\". See arclight_list_cities." }, "limit": { "type": "integer", "default": 20, "maximum": 50, "minimum": 1, "description": "How many events to return in one call. Pair with offset to page." }, "topic": { "enum": [ "ai", "tech", "software", "meetups", "hackathons", "conferences", "networking", "music", "arts", "nightlife" ], "type": "string", "description": "Optional topic filter." }, "offset": { "type": "integer", "default": 0, "maximum": 500, "minimum": 0, "description": "How many events to skip, for paging. Pass the next_offset from the previous response rather than computing it; when has_more is false there is nothing left to fetch. Offset applies within the chosen timeframe, so changing timeframe invalidates an offset from an earlier call." }, "timeframe": { "enum": [ "today", "tomorrow", "this_week", "this_month", "upcoming" ], "type": "string", "default": "this_week", "description": "How far ahead to look, measured from now. Past events are never returned." }, "response_format": { "enum": [ "markdown", "json" ], "type": "string", "default": "markdown", "description": "Output format. 'markdown' to read back to a person, 'json' to compute over." } }, "additionalProperties": false }arguments 64 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 idcfa48fb71c592c11.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/cfa48fb71c592c11/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/cfa48fb71c592c11?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.