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

frontrowtickets

https://mcp.frontrowtickets.com

Registry code: ef3c390ebc079e3f

api record

FrontRowTickets.com ticket inventory (via TicketNetwork). Read-only: search events, check availability and pricing. All data is cached; every response includes as_of. To buy, send the user to the event url — checkout happens on the website.

endpoint
https://mcp.frontrowtickets.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 frontrowtickets live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is frontrowtickets free to use?
Yes — the hub reached it with no key and no payment.
What tools does frontrowtickets have?
4 tools: get_availability, get_deals, get_event, search_events.
Is frontrowtickets 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 100%· all time 100%

latency
308ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1 open 3 never probed 1 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.

  • search_events open 2h ago

    Search FrontRowTickets.com ticket inventory by text, city, date range, or category. Returns matching events with ticket counts and starting prices.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "city": {
          "type": "string",
          "description": "City name, e.g. Chicago"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Free text: team, artist, show, or venue name"
        },
        "date_to": {
          "$ref": "#/properties/date_from",
          "description": "Latest event date (ISO)"
        },
        "category": {
          "enum": [
            "sports",
            "concerts",
            "theater",
            "comedy"
          ],
          "type": "string"
        },
        "date_from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}",
          "description": "Earliest event date (ISO)"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • get_availability unknown 2h ago

    Ticket availability and starting price for one event. Note: the TicketNetwork Catalog API does not expose section-level price bands, so only totals and the starting price are returned.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "event_id"
      ],
      "properties": {
        "event_id": {
          "type": "string",
          "description": "Event ID from search_events"
        },
        "quantity": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Desired ticket quantity (informational)"
        },
        "max_price": {
          "type": "number",
          "description": "Only report the event if its starting price is at or below this USD value",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • get_deals unknown 2h ago

    Cheapest available events under a price cap, optionally filtered by city and date range.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "max_price"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City name, e.g. Chicago"
        },
        "date_to": {
          "$ref": "#/properties/date_from",
          "description": "Latest event date (ISO)"
        },
        "date_from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}",
          "description": "Earliest event date (ISO)"
        },
        "max_price": {
          "type": "number",
          "description": "Maximum starting price in USD",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_event unknown never probed

    Full details for one event: venue, date, ticket count, price range, sections available.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "event_id"
      ],
      "properties": {
        "event_id": {
          "type": "string",
          "description": "Event ID from search_events"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 ef3c390ebc079e3f.

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