Skip to content

Pandy Tickets MCP server

cloud.pandy/ticketspandy.cloudstreamable-httpv1.0.0Scanned

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

4 tools: 1 can delete or cancel things, 1 change things and 2 only read.

Tools: 1 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Pandy Tickets MCP server can do

The Pandy Tickets MCP server is published by pandy.cloud, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: draft-event) and create or change data (1 tool: get-checkout-link). 2 tools only read.

3 tools bring in text other people can write (search-events, get-event and get-checkout-link).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • draft-eventPrepare a person's own event on Pandy Tickets from what they told you (name, date, place, ticket categories with price and quantity).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
    • idempotentHint: false
Changes things 1Claude Code: ask
Only reads 2Show 2 read-only tools
  • get-eventOne 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.instruc…Reads text others writeNo findings

    Why it is in this group

    • The name "get-event" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • search-eventsSearch upcoming published events on Pandy Tickets in Guatemala, soonest first, 20 per page.Reads text others writeNo findings

    Why it is in this group

    • The name "search-events" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:32 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tickets.pandy.cloud/mcp: tools/list returned 4 tools to an anonymous client, including draft-event (destructive), get-checkout-link (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • RFC 9728 protected resource metadata: https://tickets.pandy.cloud/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://tickets.pandy.cloud to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get-checkout-link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get-checkout-link" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://tickets.pandy.cloud/.well-known/oauth-protected-resource/mcp -> none; Authorization servers: https://tickets.pandy.cloud -> none; Dynamic client registration: yes -> not …View diff
    • RFC 9728 protected resource metadata: https://tickets.pandy.cloud/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://tickets.pandy.cloud to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tickets__search-events",
      "mcp__tickets__get-event"
    ],
    "ask": [
      "mcp__tickets__get-checkout-link"
    ],
    "deny": [
      "mcp__tickets__draft-event"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tickets. Review it before you use it.

Capability tags behind 3 rules
  • mcp__tickets__search-events untrusted-input
  • mcp__tickets__get-event untrusted-input
  • mcp__tickets__get-checkout-link untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/cloud.pandy/tickets/verify?hash=645da9588dce9db9a77af6aabd9d75bdeeaee4bb14f46742ca94e1466de19e23" | jq -e '.changed == false'

Pinned hash 645da9588dce, from Nov 12, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/cloud.pandy/tickets/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for cloud.pandy/tickets
[![Anlyon Radar](https://radar.anlyon.com/badge/cloud.pandy/tickets.svg)](https://radar.anlyon.com/servers/cloud.pandy/tickets)

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

Pandy Tickets MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Pandy Tickets MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Pandy Tickets MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: draft-event.

Can the Pandy Tickets MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Pandy Tickets MCP server have?

4 tools: 1 destructive, 1 write, 2 read. draft-event, get-checkout-link, search-events and get-event.

Does the Pandy Tickets MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Pandy Tickets MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Pandy Tickets MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.