MCP servers › io.usefulapi › ticketspice
MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27
io.usefulapi/ticketspice
TicketSpice MCP by usefulapi — the publisher's title
by usefulapi.io · domain (the registry's namespace rule)repository owner on GitHub: m190 (personal account)Source ↗Website ↗
Read TicketSpice forms, orders, tickets, customers, coupons; create or delete coupons. — the publisher's description
Summary
io.usefulapi/ticketspice is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain usefulapi.io. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 1 prompt.
Record checks
4 of 4 record checks met · 4 do not apply · 1 not checked
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not checked: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 15
- Last tested
- 2026-10-27
Tool list size
6,609 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (15 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-27 (ticketspice.usefulapi.io), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.1.0).
Observed fact
This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (ticketspice_create_coupon, ticketspice_delete_coupon). That is our reading of the names; we did not call them. Source: our connection, 2026-10-27.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-27
- Mode
- read-only (no tool calls)
- Latest version
- 1.1.0, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)
- First listed version
- 2026-10-25 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-10-25 to 2026-10-27; 2 in the 90 days before the 2026-10-27 snapshot.(versions still listed in the registry only)
Most recent 2 versions
1.1.0· 2026-10-271.0.0· 2026-10-25
- Registry data
- snapshot 2026-10-27
- Package and repository
- checked 2026-10-27
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.0.0 (published 2026-10-25) → 1.1.0 (published 2026-10-27), between the registry lists of 2026-10-26 and 2026-10-27.
The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.
Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27; release notes from the GitHub Releases API, checked 2026-10-27.
What it is
What does this server offer?
Observed inventoryNone of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.
- ticketspice_list_forms
“List the account's TicketSpice forms (ticketed events / order pages): id, name, status (open, closed, scheduled or archived), created and updated dates.”
Publisher declares: read-only yes · destructive no · open-world yes
7 inputs
created_afterstring“Only records created after this time.”created_beforestring“Only records created before this time.”updated_afterstring“Only records updated after this time.”updated_beforestring“Only records updated before this time.”limitinteger“Results per page, 1-50 (default 25).”starting_afterinteger“Cursor: pass the previous reply's next_starting_after to get the next page.”sortstring“Sort by id: asc or desc (the vendor default applies when omitted).”
- ticketspice_get_form
“One form by id: name, status, accounting reference, time zone and its field layout.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
form_idintegerrequired“TicketSpice form id (from ticketspice_list_forms).”
- ticketspice_get_form_inventory
“Inventory items of a form (limited-quantity items): path, name, sold and remaining quantity.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
form_idintegerrequired“TicketSpice form id.”
- ticketspice_list_orders
“List orders (one per checkout): order number, buyer billing name and address, form, total, currency and status, newest or oldest first.”
Publisher declares: read-only yes · destructive no · open-world yes
12 inputs
form_idinteger“Only orders of this form.”statusstring“Order status string as the vendor returns it (for example "completed" or "active").”emailstring“Only orders placed with this email address.”customer_idinteger“Only orders of this customer (buyer) id.”order_numberstring“Only the order with this order number.”created_afterstring“Only records created after this time.”created_beforestring“Only records created before this time.”updated_afterstring“Only records updated after this time.”updated_beforestring“Only records updated before this time.”limitinteger“Results per page, 1-50 (default 25).”starting_afterinteger“Cursor: pass the previous reply's next_starting_after to get the next page.”sortstring“Sort by id: asc or desc (the vendor default applies when omitted).”
- ticketspice_get_order
“One order by id with the buyer's billing details, event, totals and status.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
order_idintegerrequired“TicketSpice order id (from ticketspice_list_orders).”include_ticketsboolean“Also return the order's tickets.”include_transactionsboolean“Also return the order's transactions.”
- ticketspice_list_transactions
“List payment transactions (money movements): amount, currency, type (charge, refund, voucher), payment method, masked card, status, form and buyer email.”
Publisher declares: read-only yes · destructive no · open-world yes
16 inputs
form_idinteger“Only transactions of this form.”typestring“Transaction type.”payment_methodstring“Payment method.”statusstring“Transaction status string as the vendor returns it (for example "completed" or "active").”order_idinteger“Only transactions of this order id.”customer_idinteger“Only transactions of this customer (buyer) id.”emailstring“Only transactions of orders placed with this email.”order_numberstring“Only transactions of this order number.”referencestring“Only the transaction with this payment reference (txReference).”created_afterstring“Only records created after this time.”created_beforestring“Only records created before this time.”updated_afterstring“Only records updated after this time.”updated_beforestring“Only records updated before this time.”limitinteger“Results per page, 1-50 (default 25).”starting_afterinteger“Cursor: pass the previous reply's next_starting_after to get the next page.”sortstring“Sort by id: asc or desc (the vendor default applies when omitted).”
- ticketspice_get_transaction
“One transaction by id: amounts, type, payment method, masked card, gateway message and status.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
transaction_idintegerrequired“TicketSpice transaction id (from ticketspice_list_transactions).”
- ticketspice_list_tickets
“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.”
Publisher declares: read-only yes · destructive no · open-world yes
14 inputs
form_idinteger“Only tickets of this event (form) id.”statusstring“Ticket status string as the vendor returns it (for example "completed" or "active").”order_idinteger“Only tickets of this order id.”order_display_idstring“Only tickets of the order with this customer-facing order display id.”customer_idinteger“Only tickets of this customer id.”emailstring“Only tickets of orders placed with this email address.”order_numberstring“Only tickets of this order number.”created_afterstring“Only records created after this time.”created_beforestring“Only records created before this time.”updated_afterstring“Only records updated after this time.”updated_beforestring“Only records updated before this time.”limitinteger“Results per page, 1-50 (default 25).”starting_afterinteger“Cursor: pass the previous reply's next_starting_after to get the next page.”sortstring“Sort by id: asc or desc (the vendor default applies when omitted).”
- ticketspice_get_ticket
“One ticket by id: buyer, event, level, amount, fee, total, status, scan count, last scan time and the buyer's form answers.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
ticket_idintegerrequired“TicketSpice ticket id (from ticketspice_list_tickets).”
- ticketspice_list_customers
“List customer records (buyers): id, email, billing name and address, total spent, created and updated dates.”
Publisher declares: read-only yes · destructive no · open-world yes
8 inputs
emailstring“Only the customer with this email address.”created_afterstring“Only records created after this time.”created_beforestring“Only records created before this time.”updated_afterstring“Only records updated after this time.”updated_beforestring“Only records updated before this time.”limitinteger“Results per page, 1-50 (default 25).”starting_afterinteger“Cursor: pass the previous reply's next_starting_after to get the next page.”sortstring“Sort by id: asc or desc (the vendor default applies when omitted).”
- ticketspice_get_customer
“One customer record by id: email, billing details and total of the customer's transactions.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
customer_idintegerrequired“TicketSpice customer id (from ticketspice_list_customers, or an order's customerId).”
- ticketspice_list_coupons
“List TicketSpice coupons: account-wide ones, or only those of one form when form_id is given.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
form_idinteger“Only coupons of this form; omit for the account-wide (global) coupons.”codestring“Only global coupons with this code (ignored with form_id).”limitinteger“Results per page, 1-50 (default 25).”starting_afterinteger“Cursor: pass the previous reply's next_starting_after to get the next page.”sortstring“Sort by id: asc or desc (the vendor default applies when omitted).”
Show 3 more tools
- ticketspice_get_coupon
“One coupon by id with its discounts, codes, availability and redeemed counts.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
coupon_idintegerrequired“TicketSpice coupon id (from ticketspice_list_coupons).”
- ticketspice_create_coupon
“WRITE: create a discount coupon in the live TicketSpice account (it can be redeemed by ticket buyers right away).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
9 inputs, 4 required
namestringrequired“Internal coupon name.”codesarrayrequired“One or more redeemable codes.”discount_valuenumberrequired“Discount amount: currency units for a fixed discount, percent (1-100) for a percent discount.”discount_typestringrequired“fixed (a currency amount) or percent.”currencystring“Currency code, default USD.”availableinteger“How many times the coupon can be used; -1 = unlimited (default).”form_idinteger“Restrict the coupon to this form; omit for all forms.”per_ticketboolean“Apply the discount to each ticket instead of once per order (default false).”expiresstring“When the coupon expires; omit for no expiry.”
- ticketspice_delete_coupon
“WRITE: permanently delete a coupon from the live TicketSpice account; its codes stop working immediately and this cannot be undone.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
2 inputs, 2 required
coupon_idintegerrequired“TicketSpice coupon id to delete.”confirmbooleanrequired“Must be true: the user approved permanently deleting this coupon.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 82
- Tools with a description
- 100% of 15
- Typical description length
- 195 characters
The tool set
Counted from the listing
- Tools
- 15
- Size of the list
- about 4,394 tokens for an agent to load (characters ÷ 4)
- Naming
- 15 of 15 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-27 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://ticketspice.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ticketspice": {
"url": "https://ticketspice.usefulapi.io/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"ticketspice": {
"type": "http",
"url": "https://ticketspice.usefulapi.io/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"ticketspice","type":"http","url":"https://ticketspice.usefulapi.io/mcp"}'Claude Code
claude mcp add --transport http ticketspice https://ticketspice.usefulapi.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"ticketspice": {
"type": "streamableHttp",
"url": "https://ticketspice.usefulapi.io/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"ticketspice": {
"httpUrl": "https://ticketspice.usefulapi.io/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.ticketspice] url = "https://ticketspice.usefulapi.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"ticketspice": {
"url": "https://ticketspice.usefulapi.io/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://ticketspice.usefulapi.io/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint ticketspice.usefulapi.io/mcp | Session opened | matches | our test · 2026-10-27 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-27 |
| Repository github.com/m190/usefulapi-mcp | Opens publicly | matches | api.github.com · 2026-10-27 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.usefulapi · 462 servers
- GitHub owner
- a personal account (m190)
- Repository
- github.com/m190/usefulapi-mcp
- Stars
- 0
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
Source: the registry entry and api.github.com · 2026-10-27.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Tool list changes
Our reads compared · no tool calledHosted endpoint ticketspice.usefulapi.io/mcp
No change in the tool list across 2 reads (2026-10-26 to 2026-10-27; versions 1.0.0 to 1.1.0).
Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-27 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating4 of 4 record checks met · 4 do not apply · 1 not checked
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.usefulapi/ticketspice
Answered from the data aboveWho publishes io.usefulapi/ticketspice?
The registry ties the namespace io.usefulapi to the domain usefulapi.io; only its owner can publish under it. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. These are facts from the registry and GitHub, not a rating.
Is io.usefulapi/ticketspice safe to install?
We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.usefulapi/ticketspice need an API key or sign-in?
It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.usefulapi/ticketspice been security tested?
Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
Where is the source code of io.usefulapi/ticketspice?
In github.com/m190/usefulapi-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not run · an error was returned
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised13 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 296 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 15 tools, 0 resources, 1 prompt.
- 1,488 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.usefulapi/ticketspice: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.usefulapi/ticketspice
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.usefulapi/ticketspice)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology