Execute crypto-dispute-mediator-mcp

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

Premium agentic endpoint for crypto-dispute-mediator-mcp.

VerifiedSSEWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for a crypto dispute mediator, reachable over SSE and paid per call with a signed USDC transfer on Base Mainnet.

What you can do
Connects an assistant to a hosted crypto dispute mediation service over SSE at a fixed remote endpoint. The registry lists no individual tools, so the exact operations are not documented here. Access is metered: each request is settled through an x402 V2 payment on Base Mainnet in USDC, authorized by a signed transfer header.
When to use it
Consider it only if you need a hosted crypto dispute mediation service and are prepared to pay per request in USDC on Base Mainnet. Without a published tool list or README, evaluate it cautiously before relying on it.
Requirements
A remote SSE endpoint at the provider's host; 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, covering $0.4 USDC per request. A wallet able to produce that signature and hold USDC on Base.
Before you install
Requests cost real money: $0.4 USDC per settlement on Base Mainnet, signed with your wallet. The Payment-Signature header is a wallet authorization and must be treated as a secret. The service is a third party that receives your dispute content, and no tool list, README or authentication scheme is published, so scope and data handling are unverified.

Installation

In SourceWeft

  1. Open Execute crypto-dispute-mediator-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%2Fcrypto-dispute-mediator-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-crypto-dispute-mediator": {
      "type": "sse",
      "url": "https://api.m2mcent.com/crypto-dispute-mediator-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.