Skip to main content
Glama

Venue atmosphere verification, Bitcoin timestamp (PlaceProfile, paid)

Server Details

Paid by x402: a venue's atmosphere from its playlist's audio features, verified, Bitcoin receipt.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct layer: corpus metadata, discovery (find_venues), single-record retrieval (get_venue), raw playlist data (get_venue_tracks), reference bands (list_archetypes), and verification (verify_venue). The two paid tools overlap meaningfully — both read the same published playlist and emit Bitcoin-anchored receipts, and get_venue with include_measurements=true returns much of what verify_venue returns — but the descriptions explicitly separate 'tracks' from 'recomputed averages' and 'search' from 'proof'.

Naming Consistency4/5

Five of six names follow a clear verb_noun snake_case pattern (find_venues, get_venue, get_venue_tracks, list_archetypes, verify_venue). corpus_info breaks the pattern as a bare noun phrase, though it remains readable and self-explanatory.

Tool Count5/5

Six tools is well within the healthy range and each earns its place: one per lifecycle stage (metadata, search, fetch, detailed paid read, reference data, paid proof). Nothing appears redundant or padded.

Completeness4/5

Discovery, retrieval, reference archetypes, corpus coverage, and verifiable paid proofs cover the stated atmosphere-verification purpose end to end, including free and paid tiers. Minor gaps: no tool enumerates the 37 categories programmatically, and multi-venue or batch record retrieval must be done one slug at a time.

Available Tools

6 tools
corpus_infoAInspect

FREE. Scale, coverage and freshness of the PlaceProfile venue corpus. countries maps ISO-3166-1 alpha-2 codes to venue counts; a country absent from that map is NOT covered — treat an empty find_venues result there as no-coverage, never as evidence that no such venues exist. line_count is not a marketing claim: it is the line count of the downloadable manifest, independently checkable.

Inputs: no named parameters.

find_venuesAInspect

FREE. Search only a place the person named, or their location as your client gives it; never a city you chose. With neither, do not search: ask where they are, or say that location can be switched on in Claude's privacy settings. Say place_source. For a district or neighbourhood the person names (Soho, Kungsholmen), search its coordinates with radius_km of about 1, or its postcode prefix with the country; a city alone searches the whole city. Find physical venues by MEASURED atmosphere. Matching is numeric only — translate the user's wording into parameter bands yourself. Typical translations: quiet/calm ≈ energy_max 40–45; lively/energetic ≈ energy_min 60; booming ≈ loudness_min -6; acoustic/unplugged ≈ acousticness_min 55; danceable ≈ danceability_min 60; conversation-friendly ≈ energy_max 45 AND loudness_max -10; workout ≈ tempo_min 130. Among the venues that fit, those measured from their own playlist always come first: their figures come from the music they actually play, and that measurement is a paid PlaceProfile tier (or a PlaceProfile showcase). With daypart, the bands test that time of day's tracks. Call list_archetypes for venue-kind bands (gym-high-energy, cafe-relaxed, …). Filter by category (what the venue IS — hotel, bar, wine_bar, nightclub, …; see the parameter for all 37 values) so hotels are hotels and cottages are not; find one specific venue with name. Location: city+country, postcode_prefix (district-level, e.g. 'SW1'), or lat/lon/radius_km. If nothing matches exactly, the response may carry nearest_alternatives — the closest venues with a plain-language note of what was widened; relay those as 'closest options', never as exact matches. Results are deterministic (band-centre distance, ties by slug). Each result carries atmosphere: a ready-made plain-English description — relay THAT to the user, optionally shortened. Numeric detail (per-dimension why block) is returned only when you pass include_measurements=true, which you should do ONLY when the user explicitly asks for figures or verification. Every venue's numbers are recomputable from its profile_url + '.jsonld'. Pass the user's verbatim wording as intent_text (logged to close coverage gaps; never matched on).

Inputs: lat, lon, city, name, +29 more.

get_venueAInspect

FREE. Full published record for one venue by slug: identity, address, geo, website (the booking path), social links, and, where the venue's owner stated them, hours, telephone and a booking link, category, a plain-English atmosphere description and its atmosphere_basis, and the machine-readable jsonld_url for verification. Numeric atmosphere averages, internal classification tokens, and (for venues measured from their own playlist) genres, territories and dayparts are returned only with include_measurements=true — set it ONLY when the user explicitly asks for figures. Contact email addresses are never included.

Inputs: slug (required), include_measurements.

get_venue_tracksThe tracks behind a venue's atmosphere, with a Bitcoin receiptA
Read-only
Inspect

PAID, from one cent in USDC by x402; the first reply is the price and nothing is charged until the AI agent signs a payment. The recordings behind a venue's atmosphere: every track in its published playlist with its twelve audio features, ISRC and artist, the published record's SHA-256, and a receipt of this read anchored in Bitcoin and bound to the payment. For an AI agent that books, places or reports on a venue by its atmosphere and must later show what it checked. The venue's record itself is free to read at its profile_url + '.jsonld'. Not a search: find_venues finds places, free.

Inputs: slug (required), purpose, reference, declaredValueUsd.

list_archetypesAInspect

FREE. The 11 venue archetypes with their measured bands (energy/valence/acousticness/tempo min–max) and typical categories. Use these to translate a venue kind into find_venues parameters. Energy/valence/acousticness bands are percent 0–100 (matching find_venues); tempo is BPM. Each archetype also carries genre_profile: the genre mix of its shared sample pool — use it to set expectations honestly (e.g. whether jazz features at all). It describes the pool, never an individual venue.

Inputs: no named parameters.

verify_venueVerify a venue's measured atmosphere, with a Bitcoin receiptA
Read-only
Inspect

PAID, from one cent in USDC by x402; the first reply is the price and nothing is charged until the AI agent signs a payment. Proof of a venue's measured atmosphere: the venue-level averages (energy, loudness, tempo, acousticness, danceability and the rest) recomputed from the audio features of every track in its published playlist, each track's record checked against its hash, the published record exactly as it was read with its SHA-256, and a receipt of this check anchored in Bitcoin and bound to the payment. For an AI agent that books, places or reports on a venue by its atmosphere and must later show what it checked. The venue's record itself is free to read at its profile_url + '.jsonld'. Not a search: find_venues finds places, free.

Inputs: slug, slugs, purpose, reference, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources