Execute cross-company-agent-dispute-court-mcp

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

Premium agentic endpoint for cross-company-agent-dispute-court-mcp.

VerifiedSSEWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for a cross-company agent dispute court, paid per call with a USDC signature on Base.

What you can do
The registry describes this as a premium agentic endpoint for a cross-company agent dispute court. No tools are listed in the manifest, so the specific operations it exposes are not documented in the supplied material. It is reached over SSE at a remote host rather than run locally.
When to use it
Consider it only if you specifically need a hosted dispute-resolution service for disputes between agents of different companies, and you are willing to pay per request in USDC. Without a tool list, it is hard to judge whether it fits a given workflow.
Requirements
A remote SSE endpoint; no local package or runtime is declared. Authentication is not declared, but a Payment-Signature header is required: a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, quoted at $1 USDC. Network access and a funded Base wallet able to sign such an authorization are implied.
Before you install
Each call appears to cost $1 USDC settled on Base Mainnet, so real money is spent and the Payment-Signature header carries a wallet authorization that must be treated as a secret. The endpoint is third-party and hosted remotely; the manifest lists no tools, so what data it receives or changes is unclear. Verify the service before sending anything sensitive.

Installation

In SourceWeft

  1. Open Execute cross-company-agent-dispute-court-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%2Fcross-company-agent-dispute-court-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-cross-company-agent-dispute-cour": {
      "type": "sse",
      "url": "https://api.m2mcent.com/cross-company-agent-dispute-court-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.