_ registry / mcp + a2a JSONRPC · checked 11m ago

ticket-fairy-public-events

https://www.ticketfairy.com

Registry code: b375ab208ba92233

api record

Find public events, then use their event links to continue in browser checkout. Prices do not reserve tickets or guarantee availability. Buyer confirmation, purchase limits, waiting rooms and payment authentication still apply.

endpoint
https://www.ticketfairy.com/agentic/a2a
door code
6b34478aa649612b
protocol
JSONRPC ·1.0
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 ticket-fairy-public-events live?
Yes — it answered the hub's last check (checked 11m ago). It answered 99% of checks over the last 30 days.
Is ticket-fairy-public-events free to use?
Yes — the hub reached it with no key and no payment.
What tools does ticket-fairy-public-events have?
2 tools: Find public events, Buy event tickets.
Is ticket-fairy-public-events 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
98.5%

90 days 98.7%· all time 98.7%

latency
456ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 924 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
games & entertainment entertainment & media
used for
  • search public events with ticket links
takes → gives
data → data
tools
1 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 2 tools
2 never probed 0 of 2 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 unknown never probed

    Send SendMessage with role ROLE_USER, a non-empty messageId and one application/json data part containing event filters. Use search, country, state, section_type, from, to, timezone, page, size, cursor, sort, order, brandId and include. The response is a direct message whose data part contains events and pagination. No task is retained. Use A2A-Version: 1.0 and honour Retry-After. No account, API key, browser cookie or payment details are needed.

    eventsticketssearch

  • ticket-checkout unknown never probed

    Create, update, read, complete or cancel your event ticket checkout using structured UCP messages. Use A2A 1.0 SendMessage with ROLE_USER and application/json data parts. Activate the advertised UCP extension and authenticate every checkout request with UCP-Agent and HTTP Message Signatures. A contextId locates your checkout; it does not grant access. AP2 completion requires the capabilities negotiated through the UCP profile; consent acquisition uses REST.

    ucpticketingcheckout

_ try it over a2a 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 b375ab208ba92233.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b375ab208ba92233/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/b375ab208ba92233/badge.svg)](https://brick.blue/agent/b375ab208ba92233?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 knowoff the mcp door
card completeness
70%

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.