Execute audio-watermarking-detector-mcp

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

Premium agentic endpoint for audio-watermarking-detector-mcp.

VerifiedSSEWeb executableFinanceMedia & Design

Overview

AI-generated overview

A remote MCP endpoint for an audio watermarking detector, paid per call through an x402 USDC settlement signature.

What you can do
Connects an assistant to a hosted audio-watermarking-detector service over SSE so it can submit audio for watermark detection and read the results. Access is metered: each call is settled on-chain through an x402 V2 payment authorization. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth considering when you need to check whether audio files carry a watermark and are willing to pay a small per-call fee in USDC on Base Mainnet rather than run a detector locally.
Requirements
A remote SSE endpoint at the provider's host; no local runtime or package. A crypto wallet able to sign EIP-3009 TransferWithAuthorization authorizations on Base Mainnet, with USDC available, supplied as the Payment-Signature header. Network access to the endpoint.
Before you install
Every call costs $0.1 USDC settled on Base Mainnet, so usage spends real money. The Payment-Signature header carries a signed payment authorization; treat it as a secret and do not share or log it. Audio you submit is sent to a third-party service. The manifest lists no tools, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open Execute audio-watermarking-detector-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-watermarking-detector-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-watermarking-detector": {
      "type": "sse",
      "url": "https://api.m2mcent.com/audio-watermarking-detector-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.