MCP.Market

Audio Delivery Network MCP server

online · 100% uptime
by audiodelivery.net·net.audiodelivery/mcp·v0.3.3
No reviews yet

AI-manageable audio CDN: upload, transcode, normalize, stream & deliver audio, plus grounded docs.

A89/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

0 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Audio Delivery Network yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Audio Delivery Network tools (6)

write = sends, deletes, buys or posts
  • adn_aboutFree

    Report the MCP server version, the bundled OpenAPI version, the docs source (bundled snapshot vs live), and the canonical API base URL. Use this to confirm how fresh the grounded documentation is.

  • adn_get_guideFree

    Get a concise, canonical guide for a core AudioDN concept. Topics: authentication, upload, processing, playback, webhooks, variant-types, security, compatibility.

  • adn_get_operationFree

    Get the full OpenAPI definition for a single operation by operationId (method, path, parameters, request body, responses). Use adn_list_operations to find operationIds.

  • adn_list_operationsFree

    List every AudioDN REST API operation from the bundled OpenAPI spec (operationId, method, path, summary). Use this to discover the exact, canonical endpoints instead of guessing.

  • adn_list_variant_typesFree

    List the AudioDN variant types (transcode, preview, levels, waveform_video, waveform_image, original, cover) with descriptions and whether each can be created via the REST API. Use this to distinguish variant types from org delivery "index" values (see adn_list_variants).

  • adn_search_docsFree

    Search the bundled AudioDN documentation (llms-full.txt, OpenAPI operation summaries, and guides) for a keyword or phrase. Returns ranked snippets. Use this before writing integration code to ground answers in canonical docs.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan23 source files scanned25/25
  • Live reliabilityremote reachable in 1000ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Audio Delivery Network compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
89/100
higher than 80% of 1,299 Productivity servers
Tools
6
the typical Productivity server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Productivity server answers 100%
Response time
166 ms
faster than 72% of 655 Productivity servers
Downloads a week
35
more than 22% of 427 Productivity servers with a package

What its tools let an agent do: 6 read

Install Audio Delivery Network in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.audiodelivery.net/mcp
Add to Cursor

What the publisher says

From the Audio Delivery Network repository's README, as published. We do not edit it. Read it on GitHub

@audiodn/mcp

Model Context Protocol server for AudioDN.

Exposes the AudioDN REST API as MCP tools so AI agents (Cursor, Claude Desktop, Claude Code, VS Code, Codex, etc.) can configure audio hosting on a user's behalf, plus offline, read-only knowledge tools grounded in the canonical AudioDN OpenAPI spec and documentation so agents look up the correct endpoints instead of guessing.

Install in Cursor

One-click install (hosted endpoint, zero setup — knowledge/doc tools work immediately):

To enable the live API tools, set ADNAPIKEY (an adn_... key from the dashboard) in your environment before launching Cursor; the hosted endpoint picks it up from the Authorization header. Prefer a local stdio server? Use this button instead:

Both correspond to the mcp.json shipped with this plugin. See Cursor's MCP docs for manual setup.

Install

npm install -g @audiodn/mcp
# or run on demand
npx @audiodn/mcp

Configure

Set a server-side AudioDN API key (mint one in the dashboard at under Settings → API Keys).

export ADN_API_KEY="adn_..."
# Optional overrides:
# export ADN_API_BASE_URL="https://api.audiodelivery.net"  # default
# export ADN_MCP_ALLOW_DELETE=1     # enable destructive delete tools (off by default)
# export ADN_MCP_LIVE_DOCS=1        # refresh bundled docs from the public site at startup
# export ADN_MCP_TIMEOUT_MS=30000   # per-request timeout

Environment variables

Safety model

prompt for approval; the client is the human-in-the-loop layer.

  • Reads and knowledge tools are annotated read-only and always available.
  • Create/update tools run with the API key but are annotated so MCP clients can

hidden and refuse to run unless the server is started with ADNMCPALLOW_DELETE=1. Set it once to opt in.

  • The two delete tools (adndeletecreator, adndeletecollection) are

Hosted (remote) endpoint

Besides the local npx stdio server above, AudioDN runs the same tool set as a hosted Streamable HTTP endpoint on Cloudflare Workers, so clients that support remote MCP servers can connect without installing anything.

/ serves a human landing page in a browser (and JSON for tooling), and /health returns machine-readable server info.

  • URL: https://mcp.audiodelivery.net/mcp — the MCP endpoint. The root

Knowledge/doc tools work with no key. To enable the live API tools, send your AudioDN API key on every request as either header:

  • Auth — bring your own key: the endpoint is public and stores no secrets.
Authorization: Bearer adn_...
# or
X-ADN-API-Key: adn_...
  • Deletes are never exposed on the hosted endpoint, regardless of key.

Example client configuration (clients that support a remote/HTTP MCP URL):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Audio Delivery Network: common questions

Is Audio Delivery Network MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the Audio Delivery Network safety report
How do I install Audio Delivery Network?
It runs remotely at mcp.audiodelivery.net. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Audio Delivery Network need an API key?
Yes. The registry entry asks for ADN_API_KEY, Authorization.
Is Audio Delivery Network maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.3.3.
Is Audio Delivery Network up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Audio Delivery Network?
Servers from other publishers that do the same job: SvGrid MCP server, Context7 MCP server and Svelte MCP server.
How does Audio Delivery Network compare with other Productivity MCP servers?
safety score 89/100 (higher than 80% of 1,299 Productivity servers); tools 6 (the typical Productivity server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Audio Delivery Network

Same job from other publishers: the closest match first, then the best rated.

  • SvGrid
    Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.
    A
  • Context7
    Up-to-date docs for AI agents
    A
  • Svelte MCP
    The official Svelte MCP server providing docs and autofixing tools for Svelte development
    A
  • Coolify
    46 optimized tools for managing Coolify infrastructure, diagnostics, and docs search
    B
  • Agent-Native Content
    Open-source Obsidian for MDX - edit local docs with agent assistance
    A