TicketSpice MCP by usefulapi
REMOTE · TICKETSPICE.USEFULAPI.IO
Read TicketSpice forms, orders, tickets, customers, coupons; create or delete coupons.
Available components
Last scanned (10 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “build_an_attendee_list_with_check_in_status” functional
- New prompt “check_ticket_sales_and_revenue_for_an_event” functional
- New prompt “create_or_remove_a_discount_coupon” functional
- New prompt “find_everything_one_buyer_purchased” functional
- New prompt “review_the_coupons_of_an_event” functional
- New prompt “see_how_much_limited_inventory_is_left” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.7.0 → 1.9.0 functional
- Server version: 1.6.0 → 1.7.0 functional
- Server version: 1.5.2 → 1.6.0 functional
- 30 Oct 26 0
- Server version: 1.5.1 → 1.5.2 functional
- Server version: 1.5.0 → 1.5.1 functional
- 29 Oct 26 +1
- Server version: 1.4.0 → 1.5.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- 28 Oct 26 0
- Server version: 1.1.0 → 1.3.0 functional
- 27 Oct 26 +1
- Server version: 1.0.0 → 1.1.0 functional
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://ticketspice.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ticketspice.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ticketspice.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/ticketspice/ |
| http (plaintext) | http://ticketspice.usefulapi.io/mcp | Inconclusive | 302 | http://ticketspice.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ticketspice_create_coupon Create coupon ~243
WRITE: create a discount coupon in the live TicketSpice account (it can be redeemed by ticket buyers right away). One discount (fixed amount or percent) and one or more codes; optionally limited to one form, to a number of uses, and to an expiry date. Not idempotent: calling it twice creates two coupons. POST /coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| available | integer | – | How many times the coupon can be used; -1 = unlimited (default). |
| codes | array | yes | One or more redeemable codes. |
| currency | string | – | Currency code, default USD. |
| discount_type | string | yes | fixed (a currency amount) or percent. |
| discount_value | number | yes | Discount amount: currency units for a fixed discount, percent (1-100) for a percent discount. |
| expires | string | – | When the coupon expires; omit for no expiry. |
| form_id | integer | – | Restrict the coupon to this form; omit for all forms. |
| name | string | yes | Internal coupon name. |
| per_ticket | boolean | – | Apply the discount to each ticket instead of once per order (default false). |
No output schema declared.
No examples provided.
ticketspice_delete_coupon Delete coupon ~108
WRITE: permanently delete a coupon from the live TicketSpice account; its codes stop working immediately and this cannot be undone. Show the coupon (ticketspice_get_coupon) and get the user's approval first, then call with confirm: true. GET /coupons/{id}, then DELETE /coupons/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true: the user approved permanently deleting this coupon. |
| coupon_id | integer | yes | TicketSpice coupon id to delete. |
No output schema declared.
No examples provided.
ticketspice_get_coupon Get coupon ~55
One coupon by id with its discounts, codes, availability and redeemed counts. GET /coupons/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| coupon_id | integer | yes | TicketSpice coupon id (from ticketspice_list_coupons). |
No output schema declared.
No examples provided.
ticketspice_get_customer Get customer ~64
One customer record by id: email, billing details and total of the customer's transactions. GET /search/customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | TicketSpice customer id (from ticketspice_list_customers, or an order's customerId). |
No output schema declared.
No examples provided.
ticketspice_get_form Get event ~56
One form by id: name, status, accounting reference, time zone and its field layout. GET /forms/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | integer | yes | TicketSpice form id (from ticketspice_list_forms). |
No output schema declared.
No examples provided.
ticketspice_get_form_inventory Get form inventory ~53
Inventory items of a form (limited-quantity items): path, name, sold and remaining quantity. GET /forms/{id}/inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | integer | yes | TicketSpice form id. |
No output schema declared.
No examples provided.
ticketspice_get_order Get order ~104
One order by id with the buyer's billing details, event, totals and status. Set include_tickets to embed the order's tickets and include_transactions its payments (charges and refunds). GET /search/orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_tickets | boolean | – | Also return the order's tickets. |
| include_transactions | boolean | – | Also return the order's transactions. |
| order_id | integer | yes | TicketSpice order id (from ticketspice_list_orders). |
No output schema declared.
No examples provided.
ticketspice_get_ticket Get ticket ~72
One ticket by id: buyer, event, level, amount, fee, total, status, scan count, last scan time and the buyer's form answers. GET /search/tickets/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | TicketSpice ticket id (from ticketspice_list_tickets). |
No output schema declared.
No examples provided.
ticketspice_get_transaction Get transaction ~59
One transaction by id: amounts, type, payment method, masked card, gateway message and status. GET /search/transactions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | integer | yes | TicketSpice transaction id (from ticketspice_list_transactions). |
No output schema declared.
No examples provided.
ticketspice_list_coupons List coupons ~165
List TicketSpice coupons: account-wide ones, or only those of one form when form_id is given. Shows discounts, codes, availability, redeemed count and expiry. GET /coupons/global or /coupons/forms/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Only global coupons with this code (ignored with form_id). |
| form_id | integer | – | Only coupons of this form; omit for the account-wide (global) coupons. |
| limit | integer | – | Results per page, 1-50 (default 25). |
| sort | string | – | Sort by id: asc or desc (the vendor default applies when omitted). |
| starting_after | integer | – | Cursor: pass the previous reply's next_starting_after to get the next page. |
No output schema declared.
No examples provided.
ticketspice_list_customers List customers ~193
List customer records (buyers): id, email, billing name and address, total spent, created and updated dates. Filter by email or dates. New customers can take up to 5 minutes to appear. GET /search/customers.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only records created after this time. |
| created_before | string | – | Only records created before this time. |
| string | – | Only the customer with this email address. | |
| limit | integer | – | Results per page, 1-50 (default 25). |
| sort | string | – | Sort by id: asc or desc (the vendor default applies when omitted). |
| starting_after | integer | – | Cursor: pass the previous reply's next_starting_after to get the next page. |
| updated_after | string | – | Only records updated after this time. |
| updated_before | string | – | Only records updated before this time. |
No output schema declared.
No examples provided.
ticketspice_list_forms List events ~182
List the account's TicketSpice forms (ticketed events / order pages): id, name, status (open, closed, scheduled or archived), created and updated dates. Use the form ids to filter orders, tickets and transactions. GET /forms.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only records created after this time. |
| created_before | string | – | Only records created before this time. |
| limit | integer | – | Results per page, 1-50 (default 25). |
| sort | string | – | Sort by id: asc or desc (the vendor default applies when omitted). |
| starting_after | integer | – | Cursor: pass the previous reply's next_starting_after to get the next page. |
| updated_after | string | – | Only records updated after this time. |
| updated_before | string | – | Only records updated before this time. |
No output schema declared.
No examples provided.
ticketspice_list_orders List orders ~267
List orders (one per checkout): order number, buyer billing name and address, form, total, currency and status, newest or oldest first. Filter by event (form), status, buyer email, customer id, order number or dates. GET /search/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only records created after this time. |
| created_before | string | – | Only records created before this time. |
| customer_id | integer | – | Only orders of this customer (buyer) id. |
| string | – | Only orders placed with this email address. | |
| form_id | integer | – | Only orders of this form. |
| limit | integer | – | Results per page, 1-50 (default 25). |
| order_number | string | – | Only the order with this order number. |
| sort | string | – | Sort by id: asc or desc (the vendor default applies when omitted). |
| starting_after | integer | – | Cursor: pass the previous reply's next_starting_after to get the next page. |
| status | string | – | Order status string as the vendor returns it (for example "completed" or "active"). |
| updated_after | string | – | Only records updated after this time. |
| updated_before | string | – | Only records updated before this time. |
No output schema declared.
No examples provided.
ticketspice_list_tickets List tickets ~324
List sold tickets (one record per ticket): id, buyer billing name, event, ticket level, amount, fee, total, status, scan count and last scan time, event date. Filter by event (form), status, order, buyer email, customer id or dates. Use it for attendee lists and check-in status. GET /search/tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only records created after this time. |
| created_before | string | – | Only records created before this time. |
| customer_id | integer | – | Only tickets of this customer id. |
| string | – | Only tickets of orders placed with this email address. | |
| form_id | integer | – | Only tickets of this event (form) id. |
| limit | integer | – | Results per page, 1-50 (default 25). |
| order_display_id | string | – | Only tickets of the order with this customer-facing order display id. |
| order_id | integer | – | Only tickets of this order id. |
| order_number | string | – | Only tickets of this order number. |
| sort | string | – | Sort by id: asc or desc (the vendor default applies when omitted). |
| starting_after | integer | – | Cursor: pass the previous reply's next_starting_after to get the next page. |
| status | string | – | Ticket status string as the vendor returns it (for example "completed" or "active"). |
| updated_after | string | – | Only records updated after this time. |
| updated_before | string | – | Only records updated before this time. |
No output schema declared.
No examples provided.
ticketspice_list_transactions List transactions ~316
List payment transactions (money movements): amount, currency, type (charge, refund, voucher), payment method, masked card, status, form and buyer email. Filter by type, method, form, order, donor or dates. GET /search/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only records created after this time. |
| created_before | string | – | Only records created before this time. |
| customer_id | integer | – | Only transactions of this customer (buyer) id. |
| string | – | Only transactions of orders placed with this email. | |
| form_id | integer | – | Only transactions of this form. |
| limit | integer | – | Results per page, 1-50 (default 25). |
| order_id | integer | – | Only transactions of this order id. |
| order_number | string | – | Only transactions of this order number. |
| payment_method | string | – | Payment method. |
| reference | string | – | Only the transaction with this payment reference (txReference). |
| sort | string | – | Sort by id: asc or desc (the vendor default applies when omitted). |
| starting_after | integer | – | Cursor: pass the previous reply's next_starting_after to get the next page. |
| status | string | – | Transaction status string as the vendor returns it (for example "completed" or "active"). |
| type | string | – | Transaction type. |
| updated_after | string | – | Only records updated after this time. |
| updated_before | string | – | Only records updated before this time. |
No output schema declared.
No examples provided.
How do I install the TicketSpice MCP by usefulapi server?
TicketSpice MCP by usefulapi is a hosted endpoint at https://ticketspice.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ticketspice.usefulapi.io
claude mcp add --transport http io-usefulapi-ticketspice 'https://ticketspice.usefulapi.io/mcp'
What is the TicketSpice MCP by usefulapi server?
TicketSpice MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ticketspice. Read TicketSpice forms, orders, tickets, customers, coupons; create or delete coupons. This page covers its hosted endpoint (https://ticketspice.usefulapi.io/mcp).
Is the TicketSpice MCP by usefulapi server safe to use?
TicketSpice MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TicketSpice MCP by usefulapi server expose?
TicketSpice MCP by usefulapi exposes 15 tools: ticketspice_list_forms, ticketspice_get_form, ticketspice_get_form_inventory, ticketspice_list_orders, ticketspice_get_order, and 10 more. Their descriptions and schemas cost roughly 2,261 tokens of context every time the server is loaded.
Does the TicketSpice MCP by usefulapi server require authentication?
Its publisher declares no required credentials for TicketSpice MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the TicketSpice MCP by usefulapi server still maintained?
TicketSpice MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TicketSpice MCP by usefulapi server?
VerifyMCP ran 4 checks on TicketSpice MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about TicketSpice MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.