com.getvahada/vahada
Registry code: 08350ab8b54f98c5
Vahada holds real drink prices from bars in Turkey, read from venue menus. Call list_areas first if you are unsure an area is covered. All prices are standing menu prices in Turkish lira; happy-hour prices are returned separately with their hours and never as the headline figure.
- endpoint
- https://getvahada.com/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 com.getvahada/vahada live?
- Yes — it answered the hub's last check (checked 29m ago). It answered 100% of checks over the last 30 days.
- Is com.getvahada/vahada free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.getvahada/vahada have?
- 6 tools: cheapest_drinks, venues_near, venue_prices, price_index, happy_hours_now, list_areas.
- Is com.getvahada/vahada 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 6 tools
- down → live
- topic
- lifestyle & home food & drink
- used for
- find the cheapest drinks at bars in turkey
- find current happy hours nearby
- get drink prices for a venue
- find priced bars near a location
- get a beer price index by area
- takes → gives
- text, data → data
- tools
- 6 reads
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.
list_areas reads open 14h ago
Which Turkish districts and neighbourhoods Vahada has enough priced venues to answer for, and how many venues each has. Call this first when unsure whether an area is covered.
{ "type": "object", "properties": { "city": { "type": "string", "description": "Filter to one city, e.g. 'Istanbul'." } } }arguments 9 linescheapest_drinks reads unknown never probed
Rank venues by the cheapest standing price for a drink category, optionally within one district or neighbourhood of a Turkish city. Use for questions like 'where is the cheapest beer in Kadıköy' or 'cheap cocktails in Beyoğlu'.
{ "type": "object", "required": [ "drink" ], "properties": { "area": { "type": "string", "description": "District or neighbourhood name, e.g. 'Kadıköy' or 'Beyoğlu'. Omit for all of Turkey." }, "drink": { "enum": [ "beer", "wine", "cocktail" ], "type": "string", "description": "Which drink category to rank by." }, "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "How many venues to return (default 10)." } } }arguments 27 linesvenues_near reads unknown never probed
Priced venues within a radius of a latitude/longitude, nearest first, with their cheapest drink in each category and the distance. Use when the user has shared a location or named a place you can geocode yourself.
{ "type": "object", "required": [ "latitude", "longitude" ], "properties": { "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "How many to return (default 10)." }, "latitude": { "type": "number", "maximum": 90, "minimum": -90 }, "longitude": { "type": "number", "maximum": 180, "minimum": -180 }, "radius_km": { "type": "number", "maximum": 25, "minimum": 0.1, "description": "Search radius in km (default 2)." } } }arguments 31 linesvenue_prices reads unknown never probed
Every standing drink price for one venue, plus any happy hours with the days and times they run. Accepts a venue name or its Vahada slug.
{ "type": "object", "required": [ "venue" ], "properties": { "venue": { "type": "string", "description": "Venue name or slug, e.g. 'Fıçı Pera'." } } }arguments 12 linesprice_index reads unknown never probed
The published Vahada Bira Endeksi: median drink prices for Turkey and for the covered districts, as frozen in a monthly edition. Use for 'what does a beer cost in Turkey'.
{ "type": "object", "properties": {} }arguments 4 lineshappy_hours_now reads unknown never probed
Discounted drinks being served AT THIS MOMENT, with how long each has left. Turkey time. Use for 'is there a happy hour near me right now' or 'cheap drinks in Beyoğlu tonight'. Returns an empty list when nothing is running, which is a real answer rather than an error.
{ "type": "object", "properties": { "area": { "type": "string", "description": "District or neighbourhood, e.g. 'Kadıköy'. Omit for all of Turkey." }, "limit": { "type": "integer", "maximum": 25, "minimum": 1, "description": "How many to return (default 10)." } } }arguments 15 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 id08350ab8b54f98c5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/08350ab8b54f98c5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/08350ab8b54f98c5?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.