Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Audiala

REMOTE · MCP.AUDIALA.COM

Audio guides for 44,000+ places in 1,900+ cities, with narrated previews in ChatGPT and Claude.

Available components

0 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Recent critical change

Authorization (25 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security91
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 704 tokens (~176/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 30 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Nov 26 0
    • “get_trip_planner_link” added an optional parameter “q” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 12 Nov 26 +1
    • Stability: pass → fail ▼ security
    • Tool “audiala_audio_guide” was removed ▼ security
    • Tool “audiala_contact_team” was removed ▼ security
    • Tool “audiala_find_city” was removed ▼ security
    • Tool “audiala_plan_trip” was removed ▼ security
    • Authorization: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 71% → 100% ▲ functional
    • Schema quality: 204 → 167 ▲ functional
    • Server version: 0.4.8 → 0.4.10 functional
    • New tool “get_audio_guide_preview” functional
    • New tool “get_city_overview” functional
    • New tool “get_trip_planner_link” functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Server version: 0.4.7 → 0.4.8 functional
  • 29 Oct 26 +2
    • Stability: fail → pass ▲ security
  • 10 Oct 26 0
    • Transport: fail → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.audiala.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=audiala.com CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 ecf7ef0ba70eeea913a2eb8b18ae5c80
SANs: audiala.com, mcp.audiala.com, *.mcp.audiala.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.audiala.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
audiala.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.audiala.com/mcp Verified 200
http (plaintext) http://mcp.audiala.com/mcp HTTPS enforced 301 https://mcp.audiala.com/mcp
MCP tools · 3 exposed · ~586 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_audio_guide_preview ~225

Looks up one landmark, museum or other place in Audiala's audio-guide catalog and returns a place card: a photo, a short summary, a 45-second preview of the narrated audio guide that the user can play in the card, and a link that opens the full guide in the Audiala app. Use this when the user asks for Audiala's audio guide to a specific named place, or asks to hear it. Both the city and the place name are required. Only the 45-second preview plays in the chat; the full narration is in the Audiala app. If the place has no guide, the result lists up to 6 places in that city that do (kind "place_candidates"). Read-only.

NameTypeReqDescription
citystringyesCity the place is in, as a name or catalog slug, for example 'Rome' or 'rome'.
langstring–Language of the guide and its preview. Defaults to en.
monumentstringyesName of the landmark, museum or place, for example 'Colosseum'.
NameTypeReqDescription
cityobject–The resolved city.
kindstringyes–
langstring––
linksobject–UTM-tagged links into Audiala.
listen_in_appstring––
messagestring–Why nothing matched and what to try instead.
notestring––
placeobject––
querystring––
suggestionsarray–Other places in the city that have a guide, when the place was not found.

No examples provided.

get_city_overview ~187

Looks up one city in Audiala's audio-guide catalog and returns a city card: a short summary, the number of audio guides, up to 8 places that have a guide, and links to the city on audiala.com and in the Audiala app. Use this when the user asks what Audiala covers in a named city, or which places there have an audio guide. Do not use it for hotels, restaurants, transport, tickets or opening hours: the catalog has none of these. The catalog covers 1,900+ cities; a city that is not in it returns kind "not_found". Read-only.

NameTypeReqDescription
langstring–Language of the summary and links. Defaults to en.
namestringyesCity name. Accents and minor misspellings are tolerated, for example 'Tokyo', 'Tōkyō' or '東京'.
NameTypeReqDescription
cityobject–The resolved city.
kindstringyes–
langstring––
linksobject–UTM-tagged links into Audiala.
matchesarray–Other cities matching the query.
messagestring–Why nothing matched and what to try instead.
querystring––
top_placesarray–Places in the city that have an audio guide, in the order of the audiala.com city page.

No examples provided.

get_trip_planner_link ~174

Returns a link that opens Audiala's trip planner for one city, in a browser or in the Audiala mobile app, together with up to 8 places in that city that have an audio guide. Use this when the user asks to plan a trip to that city with Audiala, or to continue planning in Audiala. This tool does not build an itinerary and returns no day-by-day plan: the planner does that after the user opens the link. Read-only.

NameTypeReqDescription
citystringyesCity name, for example 'Prague'.
langstring–Language of the card and links. Defaults to en.
qstring–Optional walk or trip brief to pre-fill in the planner, for example '3 hours around Trastevere, baroque churches and a café stop'.
NameTypeReqDescription
cityobject–The resolved city.
kindstringyes–
langstring––
linksobject–UTM-tagged links into Audiala.
messagestring–Why nothing matched and what to try instead.
open_in_appstring–Opens the city in the Audiala mobile app, where the trip planner starts.
querystring––
recommendationstring–What each link opens.
top_placesarray–Places in the city that have an audio guide; not an itinerary.

No examples provided.

Install

How do I install the Audiala MCP server?

Audiala is a hosted endpoint at https://mcp.audiala.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.audiala.com

# add to Claude Code
claude mcp add --transport http com-audiala-mcp 'https://mcp.audiala.com/mcp'
Common questions

What is the Audiala MCP server?

Audiala is an MCP server listed in the public MCP registry as com.audiala/mcp. Audio guides for 44,000+ places in 1,900+ cities, with narrated previews in ChatGPT and Claude. This page covers its hosted endpoint (https://mcp.audiala.com/mcp).

Is the Audiala MCP server safe to use?

Audiala scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Audiala MCP server expose?

Audiala exposes 3 tools: get_city_overview, get_audio_guide_preview, get_trip_planner_link. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.

Does the Audiala MCP server require authentication?

No. We connected to Audiala without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Audiala MCP server still maintained?

Audiala is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Audiala MCP server?

VerifyMCP ran 14 checks on Audiala, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.