NeedATicket.co.uk
Registry code: 52a0feacb16e9154
Read-only live ticket prices from NeedATicket.co.uk. Call search_ticket_prices; link people to the event page URL in each result, which has the current price and where to buy.
- endpoint
- https://needaticket.co.uk/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 NeedATicket.co.uk live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is NeedATicket.co.uk free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does NeedATicket.co.uk have?
- 1 tool: search_ticket_prices.
- Is NeedATicket.co.uk 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.
90 days 100%· all time 100%
last good check
of 1 tools
- unknown → live
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.
through this hub
successful
what callers paid
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_ticket_prices open 2h ago
Live "from" prices for upcoming concerts, sport, theatre and festivals, checked hourly from StubHub listings by NeedATicket.co.uk. Prices are per ticket in GBP before the seller's fees. Use it for questions like "cheapest Oasis tickets", "what's on in Manchester next weekend" or "how much are Metallica Sphere tickets". Every result links to the event's page on NeedATicket.co.uk, which shows the current price, other dates and where to buy. An event page's price can be refreshed live on demand; priceCheckedAt says when it was last read.
{ "type": "object", "properties": { "to": { "type": "string", "description": "Last event date to include, YYYY-MM-DD." }, "from": { "type": "string", "description": "First event date to include, YYYY-MM-DD (the event's local date)." }, "sort": { "enum": [ "price", "drop", "soon", "low" ], "type": "string", "description": "price = cheapest first; soon = soonest first; drop = biggest 7-day price fall; low = furthest below its usual price." }, "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Results to return (default 10)." }, "query": { "type": "string", "maxLength": 60, "minLength": 2, "description": "Artist, team, show or venue name. Part of a word is fine." }, "anywhere": { "type": "boolean", "description": "Include events in every country, not only this site's home country. Default true when a query is given; a city with no events at home is also looked for abroad." }, "max_price": { "type": "number", "description": "Highest \"from\" price per ticket, in GBP.", "exclusiveMinimum": 0 }, "event_city": { "type": "string", "description": "Only events held in this town or city, as named in the question, e.g. \"london\", \"las-vegas\". Not the user's own location." } }, "additionalProperties": false }arguments 49 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id52a0feacb16e9154.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/52a0feacb16e9154/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/52a0feacb16e9154?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.