Diamond Hands — MCP endpoint

This host is a Model Context Protocol server, not a website. There is no app to use here. If you are a person, the app is at app.diamondhands.credit.

REAL MONEY — Ethereum mainnet This deployment serves mainnet only. Every fund-moving operation moves real BTC and real UCD, and each one needs a fresh signature from your own wallet.

Connect an agent

Add this to your MCP client configuration: 
{
  "mcpServers": {
    "diamond-hands": {
      "type": "http",
      "url": "https://mcp.diamondhands.credit/mcp"
    }
  }
}

How authorization works

Identity is a wallet, not an account: OAuth 2.1 with dynamic client registration (RFC 7591) and PKCE, where the login is an Ethereum signature (EIP-4361). No passwords, no user database. The bearer token proves session identity only — it signs nothing and can never move funds; every fund-moving step raises its own approval in your own wallet. Session state is in memory, so a restart means signing in again.

Endpoints

MCPhttps://mcp.diamondhands.credit/mcp — streamable HTTP
Networks servedmainnet
Registration/auth.md — how an agent registers and signs in
Resource metadata/.well-known/oauth-protected-resource
Auth server metadata/.well-known/oauth-authorization-server