Execute audio-description-mcp

io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 27, 2026

Premium agentic endpoint for audio-description-mcp.

VerifiedSSEWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP endpoint for audio description work, paid per call through an x402 USDC payment signature on Base Mainnet.

What you can do
  • The listing gives no tool list, so capabilities can only be inferred from the name and description.
  • It is presented as a premium agentic endpoint for audio-description-mcp, reached over SSE at a hosted address.
  • Access is gated by a payment signature header rather than an account login.
When to use it
Consider it only if you need a hosted audio-description service and are willing to pay per request in USDC on Base Mainnet. Because no tools or documentation are published, evaluate it cautiously before relying on it.
Requirements
A remote SSE endpoint; no local package or runtime is needed. A Payment-Signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, worth $0.1 USDC per settlement. A funded Base Mainnet wallet able to sign such authorizations, and network access.
Before you install
Every call is tied to a crypto payment: the Payment-Signature header authorizes a USDC transfer on Base Mainnet, so a client that signs carelessly can spend funds. The signature is a secret credential and should not be logged or shared. No tools, README, or authentication details are published, so what the endpoint does with your input is unverified.

Installation

In SourceWeft

  1. Open Execute audio-description-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Faudio-description-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "execute-audio-description": {
      "type": "sse",
      "url": "https://api.m2mcent.com/audio-description-mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.