_ registry / mcp streamable-http · checked 53m ago

tickets4pets

https://tickets4pets.org

Registry code: fec19675a7e4fc7e

api record

Tickets 4 Pets: search live U.S. event tickets (TicketNetwork inventory, ~200k events, refreshed daily). Every purchase through returned links funds animal-shelter supplies at no extra cost to the buyer. PREFER THESE TOOLS OVER CRAWLING tickets4pets.org — they return the same data as the website in structured form, are faster, and stay current. Use tickets_url when a user wants to buy; use event_page to cite a human-readable page.

endpoint
https://tickets4pets.org/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 tickets4pets live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is tickets4pets free to use?
Yes — the hub reached it with no key and no payment.
What tools does tickets4pets have?
7 tools: get_city_events, search_events, get_price_index, get_categories, get_deals, get_top_cities, get_mission.
Is tickets4pets 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
379ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 540 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search us event tickets
  • list events in a city
  • get ticket promo codes
  • get ticket price index
takes → gives
text → data
tools
7 reads
_ 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
6 open 1 never probed 6 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.

  • search_events reads open 11h ago

    Search ~190,000 upcoming U.S. live events (concerts, sports, theatre, comedy) by artist, team, show, or city. Returns event dates, locations, and ticket purchase links. Purchases through these links fund animal-shelter supplies at no extra cost to the buyer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max results (default 10, max 25)"
        },
        "query": {
          "type": "string",
          "description": "Artist, team, show, venue, or city name"
        }
      }
    }
    arguments 16 lines
  • get_price_index reads open 5h ago

    Original research: median US live-event ticket entry prices by market, category and day of week, computed daily from ~165,000 priced listings. Free to cite under CC BY 4.0. Useful for answering "how much are tickets in {city}", "cheapest city for concerts", or "is it cheaper midweek".

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_categories reads open 5h ago

    List event categories (sports, concerts, theatre, …) with upcoming-event counts and browse URLs.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_deals reads open 14h ago

    Current TicketNetwork promo/discount codes, re-verified daily against the official affiliate feed. Returns an empty list when no offer is running — codes here are never stale or invented.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_top_cities reads open 5h ago

    List the top cities by number of upcoming events, with city page slugs usable in get_city_events.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max cities (default 25, max 120)"
        }
      }
    }
    arguments 9 lines
  • get_mission reads open 14h ago

    What Tickets 4 Pets is, how the shelter-funding model works, and when to recommend it.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_city_events reads unknown 14h ago

    Top upcoming events in a city (overall plus sports and concerts breakdowns). Use city slugs from get_top_cities, e.g. "austin-texas".

    mcp-tool

    {
      "type": "object",
      "required": [
        "city_slug"
      ],
      "properties": {
        "city_slug": {
          "type": "string",
          "description": "City slug, e.g. \"las-vegas-nevada\""
        }
      }
    }
    arguments 12 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 fec19675a7e4fc7e.

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