Human-verified directory of non-alcoholic bars: 1,500+ venues in 70 cities, rated and re-checked.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Score is being calculated. Check back soon.
get_venueInspectFetch the full verified record for one NABarFinder venue by its stable slug: city, neighborhood, address and coordinates (when it has a fixed location), venue type, naProgramStrength (1–5), full description, NA brands stocked (brandSlugs), last-verified date, canonical nabarfinder.com URL, and — when the registry has them — website, phone, hours, signature drinks, and a sourced press quote. Fields absent from the registry are omitted, never invented. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The venue's stable slug id, e.g. 'sans-bar-austin' — as returned by search_venues or the /api/v1/venues.json feed. |
list_citiesInspectList every city NABarFinder covers, each with its state, number of human-verified venues, city slug (for search_venues), and canonical nabarfinder.com city guide URL. Takes no input. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
search_venuesInspectSearch NABarFinder — a human-verified directory of 1520 venues with real non-alcoholic (NA) drink programs across 70 cities in the US, UK, and beyond. All filters are optional and combine with AND; with no filters it returns the top-rated venues overall. Returns at most 25 venues (sorted by NA Program Strength descending, then name), each with name, slug, city, venue type, naProgramStrength (1–5; 5 = fully alcohol-free or a dedicated NA program, 1 = a few NA options), a one-line summary, and the canonical nabarfinder.com page URL for citing/linking. The response includes the total match count; if it exceeds the cap, narrow with filters. Use get_venue with a result's slug for the full record. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Limit to one covered city. Accepts a city slug ('austin-tx'), a plain name ('Austin'), or 'Austin, TX'. Call list_cities for the covered set — cities outside it return zero matches. | |
| query | No | Free-text filter over venue name, neighborhood, venue type, and description. Case-insensitive; every word must match (e.g. 'kava lounge', 'zero proof cocktail'). | |
| min_program_strength | No | Minimum NA Program Strength on the registry's 1–5 scale (5 = fully alcohol-free / dedicated NA program). E.g. 4 returns only the strongest programs. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!