# Pandy Tickets (remote · tickets.pandy.cloud)

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

- Trust score: 76/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `tickets.pandy.cloud`: 76/100 (this document), [markdown](https://verifymcp.io/servers/cloud-pandy-tickets/tickets.md), [page](https://verifymcp.io/servers/cloud-pandy-tickets/tickets)

## Channel facts

- Endpoint: `https://tickets.pandy.cloud/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http cloud-pandy-tickets 'https://tickets.pandy.cloud/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cloud-pandy-tickets": {
      "url": "https://tickets.pandy.cloud/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloud-pandy-tickets": {
      "type": "http",
      "url": "https://tickets.pandy.cloud/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cloud-pandy-tickets]
url = "https://tickets.pandy.cloud/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-pandy-tickets": {
      "type": "remote",
      "url": "https://tickets.pandy.cloud/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloud-pandy-tickets --url 'https://tickets.pandy.cloud/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cloud-pandy-tickets:
    url: "https://tickets.pandy.cloud/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cloud-pandy-tickets": {
      "Transport": "http",
      "Url": "https://tickets.pandy.cloud/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloud-pandy-tickets -t streamable-http -u 'https://tickets.pandy.cloud/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cloud-pandy-tickets": {
      "type": "http",
      "url": "https://tickets.pandy.cloud/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 76, +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.

### 2026-10-20 (score 75, +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.

### 2026-10-18 (score 74, 0)

- [security] Tool “draft-event” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 256 → 293
- [cosmetic] “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”

### 2026-10-17 (score 74, 0)

- [security] Tool “draft-event” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 201 → 256
- [functional] Schema quality: good → excellent
- [cosmetic] “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”

### 2026-10-16 (score 74, +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.

### 2026-10-14 (score 73, +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.

### 2026-10-13 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 72)

First indexed and scored.

## MCP tools (4)

### `search-events` (~153 tokens)

Search Events

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.

Input parameters:

- `entry` (string): Only events that take people this way.
- `from` (string): Starts on or after this date, YYYY-MM-DD, Guatemala time.
- `page` (integer): Page number, starting at 1.
- `q` (string): Text in the title, venue or description, e.g. "congreso", "Antigua", "5K".
- `to` (string): Starts on or before this date, YYYY-MM-DD, Guatemala time.

### `get-event` (~69 tokens)

Get Event

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).

Input parameters:

- `slug` (string, required): The event slug, from search-events or the event URL (/e/{slug}).

### `get-checkout-link` (~117 tokens)

Get Checkout Link

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.

Input parameters:

- `quantity` (integer): For paid events: how many tickets, default 1.
- `slug` (string, required): The event slug.
- `ticket_type_id` (integer): For paid events: the ticket type id from get-event.

### `draft-event` (~639 tokens)

Draft Event

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.

Input parameters:

- `accent_color` (string): Brand colour as #RRGGBB, if the person gave one.
- `capacity` (integer): Most people the event takes in total, if there is a limit.
- `description` (string): What the event is about, up to 5000 characters.
- `end_at` (string, required): End, Guatemala local time, YYYY-MM-DDTHH:MM, after start_at.
- `price_phases` (array): 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.
- `questions` (array): Questions every attendee answers when registering or buying, up to 15. Works for free and paid events.
- `start_at` (string, required): Start, Guatemala local time, YYYY-MM-DDTHH:MM. Must be in the future.
- `template` (string): Kind of event. Default conference.
- `theme` (string): 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_tone` (string): 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_types` (array): Paid ticket categories. Empty or omitted for a free event.
- `title` (string, required): Event name, up to 160 characters.
- `title_font` (string): Title font. Omit to use the look's own font.
- `transfer_instructions` (string): Bank, account number and holder for paying by bank transfer, 10 to 2000 characters. The person sees it prefilled when publishing.
- `venue` (string, required): Place or city, up to 240 characters.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cloud-pandy-tickets/tickets#diagnostics

## Score history

- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72

## 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.

## Links

- Remote endpoint: https://tickets.pandy.cloud/mcp
- Website: https://tickets.pandy.cloud/developers
- Changelog RSS feed: https://verifymcp.io/servers/cloud-pandy-tickets/tickets.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloud-pandy-tickets/tickets.json
- HTML version of this page: https://verifymcp.io/servers/cloud-pandy-tickets/tickets