Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Tickets is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Agenda and ticketing for Toots Jazz Club, Brussels: browse concerts, check seats, reserve tickets.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tickets-mcp https://toots.brussels/mcp
# 2 — ask your agent for something these tools do
# list_events, get_event, get_availability and 10 more
Tickets costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tickets-mcp https://toots.brussels/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
All upcoming concerts with date, line-up, genres and a price/availability summary. Amounts are euro cents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
Full details of one concert: bio, line-up, other dates of the same run, prices and availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event_id from list_events. |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event_id from list_events. |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
Address, contact details and the venue's FAQ (house rules, practical questions). Use this to answer buyer questions about the club instead of guessing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event_id from list_events. |
| items | array | yes | — |
| idempotency_key | string | no | Optional deduplication key of your choosing. Retrying a timed-out hold with the same key returns the original booking instead of reserving twice. |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| firstname | string | yes | — |
| lastname | string | yes | — |
| string | yes | The buyer's email; the tickets are sent there. | |
| terms_accepted | boolean | yes | Must be true, and only after the buyer explicitly accepted the terms of sale. |
| zip | string | no | — |
| country | string | no | Two-letter ISO code, e.g. BE. |
| promo_code | string | no | — |
| newsletter_opt_in | boolean | no | Only true if the buyer explicitly asked to subscribe. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| code | string | yes | The Toots Pass code, exactly as the buyer gave it. |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| code | string | yes | The gift card code, exactly as the buyer gave it. |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| shared_payment_token | string | yes | The spt_… token granted by the buyer's Link wallet. |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| timeout_seconds | integer | no | — |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| booking_uuid | string | yes | — |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The email address the buyer ordered with. | |
| locale | string | no | Language for titles, labels and the returned URLs. Defaults to fr. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tickets or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_events | no tags | |
| get_event | no tags | |
| get_availability | no tags | |
| get_venue_info | no tags | |
| hold_tickets | state-write | state-write: declares readOnlyHint: false |
| set_contact | state-write | state-write: declares readOnlyHint: false |
| redeem_pass | state-write | state-write: declares readOnlyHint: false |
| redeem_gift_card | state-write | state-write: declares readOnlyHint: false |
| pay_with_shared_payment_token | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| release_booking | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| wait_for_payment | no tags | |
| get_booking_status | no tags | |
| recover_tickets | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tickets can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.