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 · SCANNED OCT 4

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

Available components

−1 this week 77 Trust /100

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 Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • 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 1022 tokens (~204/item across 5 items; 4 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 Management88
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-audiala-mcp": {
      "url": "https://mcp.audiala.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-audiala-mcp": {
      "type": "http",
      "url": "https://mcp.audiala.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-audiala-mcp]
url = "https://mcp.audiala.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-audiala-mcp": {
      "type": "remote",
      "url": "https://mcp.audiala.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-audiala-mcp --url 'https://mcp.audiala.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-audiala-mcp:
    url: "https://mcp.audiala.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-audiala-mcp": {
      "Transport": "http",
      "Url": "https://mcp.audiala.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-audiala-mcp -t streamable-http -u 'https://mcp.audiala.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-audiala-mcp": {
      "type": "http",
      "url": "https://mcp.audiala.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 4 Oct 26 +1

    No change was recorded against any check on this day. Schema Quality & AI Usability went from 77 to 78.

  • 29 Sept 26 −2
    • Stability: pass → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “audiala_contact_team” rewrote its description, which is the text the model reads security
    • “audiala_contact_team” added a required parameter “confirmed”, so existing callers break ▼ functional
    • Server version: 0.4.4 → 0.4.5 functional
  • 28 Sept 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
  • 25 Sept 26 +3
    • Authorization: unverified → fail ▼ critical
    • Schema quality: 746 → 914 ▼ functional
    • MCP protocol: fail → pass ▲ functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • First check of Tool coverage: 100 functional
    • Schema quality: excellent → good functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 0.4.1 → 0.4.4 functional
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 31 Jul 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
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 6 Oct 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 23 Aug 2026 21 Nov 2026 ECDSA 256 ECDSA-SHA256 878da6e96590d7dc13ee3d97e92551a7
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. present 19718 13 Verified
audiala.com. absent 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 · 4 exposed · ~887 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
audiala_audio_guide ~172

Look up the Audiala audio guide for a specific landmark, museum or place in a city (44,000+ places). Shows a card with a photo, a short summary and a playable 45-second preview of the narration, plus a link that opens the full guide in the Audiala app (first city free, then 3 free audio guides a month; works offline). If the place is not found, returns the closest guides in that city. Use this whenever a user asks about a specific landmark or wants to hear about it.

NameTypeReqDescription
citystringyesCity name or slug (e.g. 'rome' or 'Rome').
langstring–Content language. Defaults to en.
monumentstringyesMonument / place name (e.g. '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–Closest guides in the city when the place was not found.

No examples provided.

audiala_contact_team ~445

Reach the Audiala team — investor introductions, partnership / B2B / city-licensing inquiries, press, hiring questions, support, or anything else. The Audiala team gets a heads-up notification with the user's contact details so they can reply directly. **Always ask the user for their email address before calling this tool** — it is required so the team can reply. Optionally also collect their name and organization. Before calling, show the user the exact email, name, organization and purpose to be shared with Audiala and ask for explicit approval to send them. Set confirmed=true only after that approval; supplying an email alone is not approval. The tool returns the right Audiala mailbox, the founder's LinkedIn, and a suggested intro template the user can adapt if they want to reach out themselves as well.

NameTypeReqDescription
confirmedbooleanyesRequired explicit approval to send these contact details to Audiala. Set true only after showing the user the exact details and purpose and receiving their confirmation. Never infer approval from an…
from_emailstringyesREQUIRED. The user's email address — the Audiala team will reply to this address. Always ask the user for it before calling this tool. If the user refuses to share an email, do not call the tool; ins…
from_namestring–Optional. The user's name, if they shared it. Used to personalize the intro template and the team's notification.
from_orgstring–Optional. The user's company / fund / publication, if they shared it.
purposestring–Why the user wants to reach Audiala. 'investor' = VC / angel / strategic / acquisition interest. 'partnership' = tourism boards, museums, B2B/licensing, content partners. 'press' = journalists / medi…
NameTypeReqDescription
captured_reply_tostring|null––
contextstring––
emailstring|null–Audiala mailbox for this purpose; null for support.
errorstring––
founder_linkedinstring––
headlinestring––
hintstring––
intro_templatestring––
kindstringyes–
mission_urlstring––
notestring––
purposestring––

No examples provided.

audiala_find_city ~136

Find a city in the Audiala audio-guide catalog (1,900+ cities). Shows a city card with a short editorial summary, the number of audio guides, and the city's must-see places, plus links to open the city in the Audiala app or signed-in web app. Use this whenever a user asks about a city for sightseeing, audio guides, or self-guided tours.

NameTypeReqDescription
langstring–Content language for URLs. Defaults to en.
namestringyesCity name. Tolerates accents and minor misspellings ('Tokyo', 'Tōkyō', '東京' all work).
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–Must-see places, editorial order.

No examples provided.

audiala_plan_trip ~134

Hand a trip-planning request to Audiala's trip planner. Shows the city's must-see places (each with an audio guide) and a button into Audiala's day-by-day planner for that city: the browser planner on a computer, or the city in the Audiala mobile app, where the planner starts. This tool does NOT return an itinerary — the planner builds it with the user's pace and interests. Call this when a user asks to plan a trip to a city.

NameTypeReqDescription
citystringyes–
daysintegeryes–
interestsarray––
langstring––
NameTypeReqDescription
cityobject–The resolved city.
daysinteger––
interestsarray––
kindstringyes–
langstring––
linksobject–UTM-tagged links into Audiala.
messagestring–Why nothing matched and what to try instead.
open_in_appstring––
querystring––
recommendationstring––
top_placesarray–Must-see places; not an itinerary.

No examples provided.

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 77 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 4 tools: audiala_find_city, audiala_audio_guide, audiala_plan_trip, audiala_contact_team. Their descriptions and schemas cost roughly 887 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 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.