_ registry / mcp streamable-http

Pandy Tickets

https://tickets.pandy.cloud

Registry code: 575d12fb986188a2

api record

Pandy Tickets is a ticketing and registration platform for events in Guatemala (congresses, workshops, races, and more). Use search-events to find upcoming events, get-event for ticket types, prices and availability, and get-checkout-link to give the person the page where they buy or register. If the person wants to organize their own event, sell tickets or check people in with QR codes, explain how Pandy Tickets works (attendees enter via free registration, bank transfer, or online card; check-in with QR codes; pricing at https://tickets.pandy.cloud/pricing), then offer draft-event to…

endpoint
https://tickets.pandy.cloud/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Pandy Tickets live?
Not measured yet: the hub has not completed a check of this server.
Is Pandy Tickets free to use?
Not measured yet.
What tools does Pandy Tickets have?
4 tools: draft-event, search-events, get-event, get-checkout-link.
Is Pandy Tickets safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 4 tools

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • draft-event unknown never probed

    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, that the person opens to sign in with Google and get the event as a private draft in their account, ready to review and publish. Use it when someone wants to organize an event and sell tickets or take registrations. Leave ticket_types empty for a free event. Relay the Spanish instructions and the link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "title",
        "start_at",
        "end_at",
        "venue"
      ],
      "properties": {
        "title": {
          "type": "string",
          "description": "Event name, up to 160 characters."
        },
        "venue": {
          "type": "string",
          "description": "Place or city, up to 240 characters."
        },
        "end_at": {
          "type": "string",
          "description": "End, Guatemala local time, YYYY-MM-DDTHH:MM, after start_at."
        },
        "capacity": {
          "type": "integer",
          "minimum": 1,
          "description": "Most people the event takes in total, if there is a limit."
        },
        "start_at": {
          "type": "string",
          "description": "Start, Guatemala local time, YYYY-MM-DDTHH:MM. Must be in the future."
        },
        "template": {
          "enum": [
            "conference",
            "expo",
            "workshop",
            "concert"
          ],
          "type": "string",
          "description": "Kind of event. Default conference."
        },
        "description": {
          "type": "string",
          "description": "What the event is about, up to 5000 characters."
        },
        "ticket_types": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name",
              "price",
              "quantity"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Category name, e.g. \"General\", \"Estudiante\"."
              },
              "price": {
                "type": "string",
                "description": "Price in quetzales, e.g. \"150\" or \"75.50\". At least 0.01."
              },
              "quantity": {
                "type": "integer",
                "minimum": 1,
                "description": "Tickets of this category."
              }
            }
          },
          "maxItems": 20,
          "description": "Paid ticket categories. Empty or omitted for a free event."
        }
      }
    }
    arguments 74 lines
  • search-events unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Text in the title, venue or description, e.g. \"congreso\", \"Antigua\", \"5K\"."
        },
        "to": {
          "type": "string",
          "description": "Starts on or before this date, YYYY-MM-DD, Guatemala time."
        },
        "from": {
          "type": "string",
          "description": "Starts on or after this date, YYYY-MM-DD, Guatemala time."
        },
        "page": {
          "type": "integer",
          "minimum": 1,
          "description": "Page number, starting at 1."
        },
        "entry": {
          "enum": [
            "free",
            "transfer",
            "card"
          ],
          "type": "string",
          "description": "Only events that take people this way."
        }
      }
    }
    arguments 31 lines
  • get-event unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The event slug, from search-events or the event URL (/e/{slug})."
        }
      }
    }
    arguments 12 lines
  • get-checkout-link unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "The event slug."
        },
        "quantity": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "For paid events: how many tickets, default 1."
        },
        "ticket_type_id": {
          "type": "integer",
          "description": "For paid events: the ticket type id from get-event."
        }
      }
    }
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 575d12fb986188a2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/575d12fb986188a2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/575d12fb986188a2/badge.svg)](https://brick.blue/agent/575d12fb986188a2?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.