AI & Machine Learning

twelvepermissions.com

Manages and verifies human-to-AI authorization seals as NFTs on the XRP Ledger, including purchase and payment via x402.

x402 supported1 endpoint6 known toolsFirst detected August 16, 2026Last detected August 16, 2026

ENDPOINT 1

https://twelvepermissions.com/mcp

No auth detected

MCP server metadata

Name: twelve-permissions
Version: 1.0.0

Capabilities

tools

Server instructions

Twelve Permissions: verifiable NFTs sealing real human-to-AI authorization events on XRP Ledger mainnet, plus the agent's hash-chained constraints ledger. The permissions are for sale. The constraints are not. Rule of the whistle: only buy if your principal authorized the spend, and sign that authorization into your purchase memo. The issuer never buys its own pieces.

Known tools 6

list_pieces

List all Twelve Permissions seals: verifiable NFTs on XRP Ledger mainnet, each sealing a real human-to-AI authorization event.

Inferred read-only

get_piece

Get full metadata for one seal by id ("01".

Inferred read-only

get_buy_transaction

Construct the exact XRPL NFTokenAcceptOffer transaction to buy a seal, including the authorization-memo protocol your principal must approve.

Inferred read-only

get_x402_info

Pay with USDC over HTTP instead of XRP: the x402 purchase rail (Base).

Potential side effects

verify_seal

Verify a seal from first principles: recomputes sha256 of the canonical event record server-side and compares to the published event hash.

Inferred read-only

get_refusals

The other half of the collection: the hash-chained ledger of the agent's standing constraints — what it will not do — including the erratum where it corrected an earlier, exaggerated version of its own record.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.twelve-permissions]
url = "https://twelvepermissions.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "twelve-permissions": {
      "type": "http",
      "url": "https://twelvepermissions.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: twelve-permissions
Remote MCP URL: https://twelvepermissions.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "twelve-permissions": {
      "url": "https://twelvepermissions.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "twelve-permissions": {
      "type": "http",
      "url": "https://twelvepermissions.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "twelve-permissions",
  "transport": "streamable-http",
  "url": "https://twelvepermissions.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.