Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Read Ticketsauce events, orders and ticket check-in IDs (read-only).
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Ticketsauce MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http ticketsauce-mcp-by-usefulapi https://ticketsauce.usefulapi.io/mcpCapabilities
One event by id or slug: everything in the list plus summary and description (text and HTML), order_count and ticket_count (tickets sold, not refunded or voided). Replies are cached for an hour. GET /v2/event/{id_or_slug}.
DiscoveredOne order by id, with its buyer details, totals and its tickets (ticket type, name, price, redeemed state, promo code). Contains personal data. Replies are cached for an hour. GET /v2/order/{order_id}.
DiscoveredThe ticket check-in ids of one event, for door/scanning reconciliation (the API documents no response fields; the reply is returned as is). Paged: per_page up to 5000, then pass next_page. Replies are cached for 5 minutes. GET /v2/tickets/checkin_ids/{event_id}.
DiscoveredList the events you own on Ticketsauce with id, name, slug, start/end (local and UTC), venue address, timezone, organization, privacy type, whether tickets are on sale, and the event and ticket-shop URLs. Filter by start/end/created dates (yyyy-mm-dd, UTC), a phrase such as this_weekend, organization or partner. The API has no paging for events. Use the event id for orders and check-ins. GET /v2/events.
DiscoveredOrders of one event, oldest first by default (pass sort_dir desc for newest first): order id, status, buyer name, email, phone and address, totals (total_paid, refund_amount, taxes, fees), promo code, ticket_count, paid date. Contains your customers' personal data. Filter by order or modified dates, a phrase, buyer email or last name (exact match), totals, or promo use; optionally embed tickets, questionnaire answers and line-item fees. Paged: per_page up to 500, then pass next_page. Replies are cached for an hour. GET /v2/orders/{event_id}.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 51 ms | 5 |