UPFRONT
tickets-upfront-upfront declares 9 capabilities across 9 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
find_events | read |
declared |
get_seating_map | read |
declared |
compare_prices | read |
declared |
find_ticket_groups | read |
declared |
best_seats | read |
declared |
section_info | read |
declared |
report_fact | write |
assumed |
venue_info | read |
declared |
artist_tours | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-28 | 19 | tools/list on https://api.upfront.tickets/mcp, published in the official MCP registry as tickets.upfront/upfront 1.0.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.