Consulate - AI Dispute Resolution (Crypto + Traditional + General)

com.consulatehqPublished by consulatehq.comOfficial publisherv2.0.0Updated Oct 24, 2026

Unified dispute resolution: crypto, payments, SLA violations. 95% AI automation.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for AI-assisted dispute resolution covering crypto, payments and SLA violations, with most cases handled automatically.

What you can do
Submit and work through disputes involving crypto, payments or SLA violations through a single unified service. The provider states that about 95% of cases are handled by AI automation. Access is authenticated with a Consulate API key sent as a bearer token. No individual tools are documented in the supplied listing, so the exact operations available to an assistant are not described.
When to use it
Consider it when you want an assistant to help file or follow up on disputes about crypto transactions, payments or service-level agreement breaches, and you already hold a Consulate account and API key.
Requirements
A remote endpoint reached over streamable HTTP at the provider's API host. A Consulate API key is required, sent in the Authorization header as a bearer token; keys begin with a live or test prefix. Network access is needed.
Before you install
The server requires an API key in the Authorization header, so treat it as a secret and prefer a test key while evaluating. Disputes concern payments and crypto, so submissions may involve financial or transaction data and may trigger real case handling; confirm what is sent to the provider before use.

Installation

In SourceWeft

  1. Open Consulate - AI Dispute Resolution (Crypto + Traditional + General) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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/com.consulatehq%2Fconsulate/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": {
    "consulate-ai-dispute-resolution-crypto-t": {
      "type": "http",
      "url": "https://api.consulatehq.com/"
    }
  }
}

Tools

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

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.