_ registry / mcp http-sse · checked 1h ago

tixel

https://mcp-v1.tixel.com

Registry code: cfde71edae6c1a8c

api record

Ticket resale marketplace: search concerts, festivals and sports events, view listings and seats, and list your own tickets for sale.

endpoint
https://mcp-v1.tixel.com/mcp
protocol
http-sse ·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 tixel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tixel free to use?
Yes — the hub reached it with no key and no payment.
What tools does tixel have?
7 tools: search_events, check_listing_status, get_listing_details, get_selling_options, start_email_listing, list_event_listings, list_supported_cities.
Is tixel 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
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
873ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 322 checks · signed record
  • down → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search concert and festival tickets
  • view ticket listings for an event
  • sell tickets from an email
takes → gives
text → data
tools
6 reads1 changes data
_ 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 7 tools
1 open 6 never probed 1 of 7 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.

  • list_supported_cities reads open 23h ago

    Return the list of cities supported on the Tixel marketplace, each with a numeric city_id. Use this information to filter the events returned by other tools by the city where the event is held — pass a city_id from this list as the city_id parameter of search_events. Optionally narrow the list with query (case-insensitive match on the city name) and/or country_code (ISO country code).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "description": "Case-insensitive substring match on the city name (e.g. \"york\")."
        },
        "country_code": {
          "type": "string",
          "description": "ISO 3166-1 alpha-2 country code to restrict cities to (e.g. \"US\", \"GB\")."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • search_events reads unknown 20h ago

    Find concerts, festivals, sports games, and shows available on the Tixel marketplace. Use for both specific queries ("Olivia Dean London", "Coldplay 2026") and broader exploration ("pop concerts in London this month"). Returns upcoming events; pass an event's tixelSlug to list_event_listings to fetch tickets. To restrict results to a specific city, pass the optional city_id parameter — call list_supported_cities to get the list of supported cities and their city_id values.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results to return. Defaults to 10."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Free-text search across event title, artist names, and venue."
        },
        "city_id": {
          "type": "integer",
          "description": "Restrict results to a single supported city, identified by its city_id. Get valid city_id values from the list_supported_cities tool."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • check_listing_status reads unknown 23h ago

    Poll an email-listing session started with start_email_listing. Long-polls (up to ~25s) while Tixel scans the forwarded email, then returns the parse status, any detected tickets, and a continueUrl — the link the user opens to finish the listing on tixel.com. If isPending is true the email hasn't been read yet; wait a moment and call again with the same sessionToken. A status of "parsed", "ai_accepted", "links_sent" or "listed" means the tickets were recognised and continueUrl is ready; "parsing_error" or "ignored" means it couldn't be used.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "session_token"
      ],
      "properties": {
        "session_token": {
          "type": "string",
          "minLength": 1,
          "description": "The sessionToken returned by start_email_listing."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • get_listing_details reads unknown 23h ago

    Fetch full per-seat info, seller details, restrictions, and the event seat-map image for one Tixel listing. Use after list_event_listings when the user wants to dig into a specific option.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tixel_slug",
        "listing_id"
      ],
      "properties": {
        "listing_id": {
          "type": "string",
          "minLength": 1,
          "description": "Listing id from list_event_listings results."
        },
        "tixel_slug": {
          "type": "string",
          "minLength": 1,
          "description": "Tixel event slug — the same one passed to list_event_listings."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_selling_options reads unknown never probed

    Help a user who already owns tickets list (sell/resell) them on Tixel. Returns the best way to list for the ticketing company the tickets were bought from (e.g. Ticketmaster, Ticketek, DICE, Eventbrite) and a direct tixel.com link to that listing page, plus generic fallbacks (forwarding the confirmation email, uploading a PDF). If the user hasn't said where they bought their tickets, call without ticketing_company to get the full list of supported companies, then ask them. Prefer the recommended option; offer fallbacks if the user can't use it (e.g. no account access). Do not use for buying tickets — use search_events instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO 3166-1 alpha-2 country code of the user (e.g. \"AU\", \"GB\", \"US\"). Orders the company list by local popularity."
        },
        "ticketing_company": {
          "type": "string",
          "description": "Company the tickets were purchased from, as the user describes it (e.g. \"Ticketmaster\", \"dice.fm\", \"Sydney Opera House\"). Also accepts special events like \"Burning Man\"."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • start_email_listing changes data unknown never probed

    Begin listing (selling) a user's tickets on Tixel straight from their inbox. Returns a one-off Tixel scanner address (scanAlias). The host should then use its email connector to forward the user's original ticket confirmation email — including any PDF or ticket attachments — to that address, sent from the email account the tickets were bought with so Tixel can verify ownership. After forwarding, call check_listing_status with the returned sessionToken to track parsing and get the link to finish the listing. Use this when the user has a confirmation email or e-tickets and wants to sell them; use get_selling_options instead if they ask how selling works or bought from a ticketing company with a direct Tixel integration (e.g. Ticketmaster, Eventbrite).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • list_event_listings reads unknown 20h ago

    Show available ticket listings for a specific event on Tixel — prices (incl. buyer fee), seat sections, quantity per listing, and the deep link to complete the purchase on tixel.com. Each listing represents a contiguous batch of seats sold together by one seller. Call search_events first to get the tixel_slug.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tixel_slug"
      ],
      "properties": {
        "sort": {
          "enum": [
            "cheapest",
            "best_value",
            "best_seats"
          ],
          "type": "string",
          "description": "How to order results. Defaults to cheapest."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max listings to return. Defaults to 20."
        },
        "quantity": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Filter to listings with at least this many tickets sold together."
        },
        "tixel_slug": {
          "type": "string",
          "minLength": 1,
          "description": "Tixel event slug from search_events (e.g. \"/au/sports-tickets/2026/04/30/collingwood-magpies-melbourne-cr\")."
        }
      },
      "additionalProperties": false
    }
    arguments 36 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 cfde71edae6c1a8c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cfde71edae6c1a8c/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/cfde71edae6c1a8c/badge.svg)](https://brick.blue/agent/cfde71edae6c1a8c?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
100%

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.