Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pandy Tickets

REMOTE · TICKETS.PANDY.CLOUD

Find events in Guatemala, get checkout links and draft new events. Public, no key.

+2 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 23 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1173 tokens (~293/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 0
    • Tool “draft-event” rewrote its description, which is the text the model reads security
    • Schema quality: 256 → 293 ▼ functional
    • “draft-event” added an optional parameter “price_phases” cosmetic
    • “draft-event” added an optional parameter “questions” cosmetic
    • “draft-event” added an optional parameter “transfer_instructions” cosmetic
  • 17 Oct 26 0
    • Tool “draft-event” rewrote its description, which is the text the model reads security
    • Schema quality: 201 → 256 ▼ functional
    • Schema quality: good → excellent functional
    • “draft-event” added an optional parameter “accent_color” cosmetic
    • “draft-event” added an optional parameter “theme” cosmetic
    • “draft-event” added an optional parameter “theme_tone” cosmetic
    • “draft-event” added an optional parameter “title_font” cosmetic
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 72

    First indexed and scored.

Diagnostics

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 23 Oct 2026 · Probed https://tickets.pandy.cloud/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pandy.cloud CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 1e24395535be7a2c0e7d3ec366f5df81
SANs: pandy.cloud, *.pandy.cloud
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 tickets.pandy.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cloud. present 7041 13 Verified
pandy.cloud. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tickets.pandy.cloud/mcp Verified 200
http (plaintext) http://tickets.pandy.cloud/mcp HTTPS enforced 301 https://tickets.pandy.cloud/mcp
MCP tools · 4 exposed · ~978 tokens

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 →

Tool Tokens
draft-event ~639

Prepare a person's own event on Pandy Tickets from what they told you (name, date, place, ticket categories with price and quantity). Nothing is published and no account is created: it returns a one-time claim_url, valid 48 hours. The person opens it, signs in with Google, and lands on a screen where they review the event and publish it with one click. Use it when someone wants to organize an event and sell tickets or take registrations. Leave ticket_types empty for a free event. Also fill in, when the person said them: questions to ask each attendee, early-bird price_phases, and transfer_instructions (bank details) so the person only reviews and publishes. Relay the Spanish instructions and the link.

NameTypeReqDescription
accent_colorstring–Brand colour as #RRGGBB, if the person gave one.
capacityinteger–Most people the event takes in total, if there is a limit.
descriptionstring–What the event is about, up to 5000 characters.
end_atstringyesEnd, Guatemala local time, YYYY-MM-DDTHH:MM, after start_at.
price_phasesarray–Early-bird style price phases, in order, up to 10. The first phase that has not ended applies. Needs paid ticket_types; a free event has no prices to phase.
questionsarray–Questions every attendee answers when registering or buying, up to 15. Works for free and paid events.
start_atstringyesStart, Guatemala local time, YYYY-MM-DDTHH:MM. Must be in the future.
templatestring–Kind of event. Default conference.
themestring–Look of the event page, checkout, emails and tickets. pandy: El estilo de Pandy Tickets. Sirve para cualquier evento. gala: Para recitales, galas, bodas y cenas benéficas. deportivo: Para carreras, t…
theme_tonestring–Light or dark version of a look that has both (gala). auto follows the event image: light image, light page. Default: the organizer's last choice, else auto.
ticket_typesarray–Paid ticket categories. Empty or omitted for a free event.
titlestringyesEvent name, up to 160 characters.
title_fontstring–Title font. Omit to use the look's own font.
transfer_instructionsstring–Bank, account number and holder for paying by bank transfer, 10 to 2000 characters. The person sees it prefilled when publishing.
venuestringyesPlace or city, up to 240 characters.

No output schema declared.

No examples provided.

get-checkout-link ~117

The link a person opens to buy tickets or register, with Spanish instructions to relay. For paid events (card or bank transfer), checkout opens with the ticket type and quantity already chosen. For free registration, it is the event page. Nothing is reserved or charged: the person completes it themselves.

NameTypeReqDescription
quantityinteger–For paid events: how many tickets, default 1.
slugstringyesThe event slug.
ticket_type_idinteger–For paid events: the ticket type id from get-event.

No output schema declared.

No examples provided.

get-event ~69

One published event: description, ticket types with prices and whether each is sold out, what the registration form asks, and how people get in (entry.url and Spanish entry.instructions to relay).

NameTypeReqDescription
slugstringyesThe event slug, from search-events or the event URL (/e/{slug}).

No output schema declared.

No examples provided.

search-events ~153

Search upcoming published events on Pandy Tickets in Guatemala, soonest first, 20 per page. Each result has its public URL, dates, venue, how people get in (free, transfer or card) and the lowest price.

NameTypeReqDescription
entrystring–Only events that take people this way.
fromstring–Starts on or after this date, YYYY-MM-DD, Guatemala time.
pageinteger–Page number, starting at 1.
qstring–Text in the title, venue or description, e.g. "congreso", "Antigua", "5K".
tostring–Starts on or before this date, YYYY-MM-DD, Guatemala time.

No output schema declared.

No examples provided.

Install

How do I install the Pandy Tickets MCP server?

Pandy Tickets is a hosted endpoint at https://tickets.pandy.cloud/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 · tickets.pandy.cloud

# add to Claude Code
claude mcp add --transport http cloud-pandy-tickets 'https://tickets.pandy.cloud/mcp'
Common questions

What is the Pandy Tickets MCP server?

Pandy Tickets is an MCP server listed in the public MCP registry as cloud.pandy/tickets. Find events in Guatemala, get checkout links and draft new events. Public, no key. This page covers its hosted endpoint (https://tickets.pandy.cloud/mcp).

Is the Pandy Tickets MCP server safe to use?

Pandy Tickets scores 76 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 Pandy Tickets MCP server expose?

Pandy Tickets exposes 4 tools: search-events, get-event, get-checkout-link, draft-event. Their descriptions and schemas cost roughly 978 tokens of context every time the server is loaded.

Does the Pandy Tickets MCP server require authentication?

No. We connected to Pandy Tickets without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pandy Tickets MCP server still maintained?

Pandy Tickets is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.