What this skill provides

The Unblind MCP server exposes two tools that mirror our public REST API:

• unblind_transaction – translates raw transaction data into clear natural language, with risk warnings.
• unblind_message – explains EIP-712 / typed message signatures and highlights dangerous approvals.

MCP server endpoint

When you integrate Unblind via MCP, you typically point your client to:

Public skill specification

We publish a machine-readable skill specification that describes the MCP server, tools, parameters, and example payloads. Agent platforms can fetch and parse this document to integrate Unblind automatically.

Example MCP client config

A typical MCP-aware client (for example an LLM platform or agent framework) can be configured like this:

{
  "mcpServers": {
    "unblind-mcp-server": {
      "type": "http",
      "url": "https://api.unblind.app/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

Get access & support

If you are building wallets, agents, or security tooling and want to integrate Unblind via MCP, we can help with keys, rate limits, and best practices.