Build · Integration guides

Any MCP client

Rightshold is a remote MCP server (streamable HTTP, stateless, JSON responses). Any host that can point at a URL can connect — the configuration is one entry.

Connect (no key)

{
  "mcpServers": {
    "rightshold": {
      "url": "https://www.rightshold.com/mcp"
    }
  }
}

Some hosts name the top-level key servers instead of mcpServers (VS Code does); the entry itself is the same. Host-specific files are in the quickstart.

Connect with a key (account tools)

{
  "mcpServers": {
    "rightshold": {
      "url": "https://www.rightshold.com/mcp",
      "headers": {
        "Authorization": "Bearer <your api key>"
      }
    }
  }
}

Public reads — check_license, kya_lookup, registry_lookup — work with no key. Account tools (whoami, orders, publishing) take the key from this header or from an api_key argument on the call.

The raw envelope

Under every client library the traffic is JSON-RPC 2.0 over one POST:

POST https://www.rightshold.com/mcp
content-type: application/json

{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "check_license", "arguments": {"license": "MIT", "intended_use": {"commercial_use": true}}}}

// The result carries content (the same JSON as text) and structuredContent:
// {"license": {"id": "MIT", ...}, "verdict": "permitted", "duties": ["attribution", "license_notice"], ...}

Toolsets: what tools/list shows

The default connection lists the core tools, to keep the list short. Add a toolset to the URL to list more — https://www.rightshold.com/mcp?toolset=all lists every tool; named sets include rights, identity, market, ledger, account and store, and they combine (?toolset=rights,identity). Listing is only presentation: every tool can be called on any connection, listed or not. The list_toolsets tool reports the sets and their tools from inside a session.

Any MCP client

Connect (no key)

Connect with a key (account tools)

The raw envelope

Toolsets: what tools/list shows

Where to go next