Tickets is answering right now. Last checked 4 min ago. It exposes 13 tools.
Agenda and ticketing for Toots Jazz Club, Brussels: browse concerts, check seats, reserve tickets.
Uptime history
25 days of history · worst day 99%
25 days agonow
100.0%
Uptime 24h
91 of 91 checks
13
Tools
read from the server
205 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 September 2026. No other catalogue keeps this.
21 Sep
a tool appeared
pay_with_shared_payment_token
Nothing serious here today
Today is the operative word: we check Tickets every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add tickets --transport http https://toots.brussels/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"tickets": {
"url": "https://toots.brussels/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.tickets]
url = "https://toots.brussels/mcp".cursor/mcp.json
{
"mcpServers": {
"tickets": {
"url": "https://toots.brussels/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"tickets": {
"url": "https://toots.brussels/mcp"
}
}
}Available tools 13
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
redeem
redeem_gift_card
Applies a Toots gift card code (given to you by the buyer) to a held booking, after set_contact. Uses as much of the card's balance as the order needs. Fully covered orders complete immediately (status paid); otherwise the response carries the payment_url for the balance.
redeem_pass
Applies a Toots Pass code (given to you by the buyer; format XXX-XXXXXX-XXX) to a held booking, after set_contact. Covers as many tickets as the pass has concerts left. If the order is fully covered the booking completes immediately (status paid); otherwise the response carries the payment_url for the balance. The code is a venue credential, not a payment instrument.
availability
get_availability
Live ticket availability for a concert, per session: the stock_id, category_id and price_id values that hold_tickets needs, with prices in euro cents and the maximum quantity per line.
booking
get_booking_status
Current status of a booking: awaiting_contact, awaiting_payment (with payment_url and amount left), paid or expired. A paid booking carries ticket_url — the one link to share with the buyer, which adapts to their device (wallet on a phone, PDF and choices elsewhere) — plus the explicit ticket_pdf_url and, when configured, apple_wallet_url / google_wallet_url.
contact
set_contact
Attaches the buyer to a held booking and returns the payment_url. Give that URL to the human buyer: payment (card or Bancontact) happens in their browser, never through this API. The tickets will be emailed to the address given here.
event
get_event
Full details of one concert: bio, line-up, other dates of the same run, prices and availability.
events
list_events
All upcoming concerts with date, line-up, genres and a price/availability summary. Amounts are euro cents.
hold
hold_tickets
Reserves tickets and returns a booking_uuid. The hold expires after 15 minutes if the order is not paid, releasing the seats. Only call this once the buyer has chosen; do not hold speculatively.
pay
pay_with_shared_payment_token
Pays the remaining balance of a booking (after set_contact, and after any pass or gift card) with a Shared Payment Token from the buyer's Link agent wallet. Request the token for exactly amount_to_pay_cents in EUR, scoped to the Stripe network profile profile_61VNUTvZyhaQmxLgqA6VNUTv7A9CUusxmQZ0xC5doSoy; the buyer approves that spend in Link. Charges the buyer, so only call it once they confirmed the purchase. On success the booking is paid and carries ticket_url; if the response says otherwise (payment_status, next_step) or errors, give the payment_url to the human buyer instead — the booking stays open until its hold expires.
recover
recover_tickets
For a buyer who lost their tickets: sends the ticket links of their past paid orders to their email address. The links go to the inbox only — the response never contains them — so the inbox is the proof of ownership. Tell the buyer to check their email (and spam folder).
release
release_booking
Gives an unpaid hold's seats back immediately, instead of letting them sit reserved until the 15-minute expiry. Call this when the buyer changes their mind. Paid bookings cannot be released.
venue
get_venue_info
Address, contact details and the venue's FAQ (house rules, practical questions). Use this to answer buyer questions about the club instead of guessing.
wait
wait_for_payment
Like get_booking_status, but holds the request open (up to 25 seconds) and returns as soon as the booking is paid. Call it after handing the buyer the payment_url instead of polling in a loop; repeat while status is still awaiting_payment and the hold has time left.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://toots.brussels/mcp | streamable-http | answering | 179 ms | 4 min ago |
Alternatives to Tickets
same job, measured the same waybrawsr
by brawsr
Browser sessions, checkpoints, rewind, fork, lineage, and lifecycle tools for brawsr.
Zendesk MCP
by markusvankempen
Zendesk MCP: 14 tools for AI agents — create, search, assign, comment, and close support tickets.
Safari DevTools MCP
by hayodev
MCP server for Safari DevTools — browser debugging and automation for AI coding agents
HVTracker MCP
by yugantm
Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.
Freshdesk
by wyre-ai
MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.
Freshdesk
by wyre-technology
MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.
Vigile MCP
by vigile-ai
Query trust scores for MCP servers and agent skills. Check if a tool is safe.
Browserbase
by mcparmory
Create and control browser sessions for web automation, testing, and AI agent tasks
Tickets — questions
Answers built from our own checks of this server.
What can Tickets do?
It exposes 13 tools, read directly from the server on our last check. Among them: get_availability, get_booking_status, get_event, get_venue_info, hold_tickets, list_events and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Tickets working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 205 ms. The bar chart above shows every period we have measured.
How do I connect Tickets?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tickets need an API key?
No. Tickets completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tickets?
It answers our handshake in 205 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.