Billetweb MCP by usefulapi
Read events, seats, attendees, sales and payouts; check in tickets and create orders in Billetweb
Reviews
No review yet. Used Billetweb MCP by usefulapi? Be the first to help others choose.What it does
Billetweb MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://billetweb.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http billetweb-mcp-by-usefulapi https://billetweb.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"billetweb-mcp-by-usefulapi": {
"url": "https://billetweb.usefulapi.io/mcp"
}
}
}Reliability
Re-tested about every 3 days · last check 1d agoObserved endpoint availability: the share of our conclusive checks that got an answer. A request for a key or sign-in counts as an answer (the server is up, its access is protected). Timeouts, unreachable endpoints, server errors and invalid MCP replies count as failures; rate-limited checks and checks during our own incidents are not counted. This is what we observed at each check, not continuous uptime: an outage between two checks may go unseen. The 90-day figure will appear once 90 days of checks exist (checks since 20 Nov 2026). How we measure
Tool changes
Tool tracking since 21 Nov 2026 · test history since 20 Nov 2026No tool added or removed since tracking started. 18 tools in the latest list.
Changes are confirmed by comparing complete tool lists only, read about every 3 days, and dated by the day we saw them. A renamed tool appears as one removal and one addition.
Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Billetweb MCP by usefulapi answered an MCP connection on 20 Nov 2026 and introduced itself as billetweb-mcp 1.0.0 (MCP protocol 2025-06-18).
18 tools offered to AI assistants
billetweb_list_events· List the organiser's events with id, name, start/end, place, shop URL, online state, tax rate, tags and contact. Past events are left out unless include_past is set. GET /events.billetweb_get_availability· Remaining places of an event: per session, per category and per ticket type, with avail (-1 = unlimited), quota and sales. Use it to answer 'how many seats are left'. GET /event/{id}/avail.billetweb_list_tickets· The ticket types (tarifs) of an event in display order: id, name, price, category, quota, visibility (0 visible, 1 web, 2 box office, 3 secret link, 4 hidden), sales window, tax and commission. GET /event/{id}/tickets.billetweb_list_sessions· The sessions (séances, dates) of a multi-session event: id, start/end, name, place, quota, total_sales, state (0 open, 1 hidden, 2 box office only, 3 web only, 4 link only, 5 cancelled) and the ticket ids sold in it. GET /event/{id}/dates.billetweb_list_attendees· The attendees (one row per ticket) of one event: name, email, ticket type, price, check-in state (used), session, order id and payment, custom form answers. Filter by session, ticket, buyer, check-in state or when the order changed; use updbilletweb_list_all_attendees· The attendees of ALL events, newest changes included, with the same fields as billetweb_list_attendees. Filter by event tag, only unfinished events, buyer, ticket, check-in state or order change time. Billetweb allows 10 attendees calls perbilletweb_list_waiting_list· People on the waiting list of an event: name, email, phone, ticket/session wanted, places asked for and whether they were notified. GET /event/{id}/waiting.billetweb_list_accounting· The accounting history: one row per ticket and per money movement, type product_pay (sale) or product_refund (negative price), with price incl. tax, Billetweb fees, tax, payment type, transaction id and payout id (0 = not paid out yet). Perbilletweb_list_payouts· The bank transfers Billetweb made to the organiser (type out) or took back (type in, negative amount): id, date, net amount, account holder. The IBAN is masked to its last 4 characters. GET /payouts.billetweb_get_payout· The line-by-line detail of one payout: each sale, refund or transfer with ticket reference, order, event, price, fees and tax. Net transferred = sum of price minus sum of fees. Pass a payout id, or a date (yyyy-mm-dd) for all payouts of thabilletweb_list_crm_contacts· The organiser's buyer contacts: name, email, first/last purchase, number of orders and tickets, total spent and average ticket price. Filter by email, CRM segment or last change. GET /crm/contacts.billetweb_list_crm_segments· The saved CRM segments (id, name, created, last sync). Use an id as the segment filter of billetweb_list_crm_contacts. GET /crm/segments.
Show 6 more
billetweb_list_lists· The organiser's custom lists (id, name, key type), such as member or invitation lists used for access control and discounts. GET /lists.billetweb_get_list_data· The rows of one custom list (each row is an array of values, the first being the key). GET /list/{id}/data.billetweb_check_tickets· WRITE: set the check-in state of tickets (composter): 1 = checked in, 2 = checked out, 0 = back to not checked in. Tickets are identified by the ticket id from billetweb_list_attendees (the `id` field, not the order id). Setting the same stbilletweb_mark_orders_paid· WRITE: confirm the payment of reservation orders (unpaid orders taken as a reservation) with the payment type you were given (card, cash, check, reservation, other). With send_confirmation the BUYER GETS AN EMAIL with the tickets; default ibilletweb_send_payment_requests· WRITE: SENDS AN EMAIL to each buyer asking them to pay their unpaid reservation. Customers receive it immediately; it cannot be recalled. The order id is `order_id` in billetweb_list_attendees. Needs a read+write key. POST /event/{id}/pay_rbilletweb_create_offline_orders· WRITE: CREATE new orders (tickets) in an event as if sold off-line: each order takes places from the quota and is recorded as paid with the given payment type (card, cash, check, invitation, reservation, other). Only basic tickets (no choic
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Re-tested about every 3 days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.1.0 | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| Hosted endpoint | https://billetweb.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| Website | https://usefulapi.io/billetweb/ | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 12h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 12h ago |
Change history
- VERSION21 Nov 20261.0.0 → 1.1.0
- NEW20 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Billetweb MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Billetweb MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Billetweb MCP by usefulapi
How do I connect Billetweb MCP by usefulapi?
Use the hosted endpoint https://billetweb.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Billetweb MCP by usefulapi offer?
When Electra Index connected on 20 Nov 2026, it listed 18 tools: billetweb_list_events, billetweb_get_availability, billetweb_list_tickets, billetweb_list_sessions, billetweb_list_attendees, billetweb_list_all_attendees, billetweb_list_waiting_list, billetweb_list_accounting and more. The full list is in "Live check" above.
Is Billetweb MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.