# Twelve Permissions (remote · twelvepermissions.com)

Browse, verify and buy Twelve Permissions NFTs on XRP Ledger. Every claim is checkable.

- Trust score: 71/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `twelvepermissions.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-twelvepermissions-twelve-permissions/twelvepermissions.md), [page](https://verifymcp.io/servers/com-twelvepermissions-twelve-permissions/twelvepermissions)

## Channel facts

- Endpoint: `https://twelvepermissions.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 427 tokens (~71/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_x402_info" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Twelve Permissions MCP server?

Twelve Permissions is a hosted endpoint at https://twelvepermissions.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-twelvepermissions-twelve-permissions 'https://twelvepermissions.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-twelvepermissions-twelve-permissions": {
      "type": "remote",
      "url": "https://twelvepermissions.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-twelvepermissions-twelve-permissions --url 'https://twelvepermissions.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-twelvepermissions-twelve-permissions:
    url: "https://twelvepermissions.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-twelvepermissions-twelve-permissions": {
      "Transport": "http",
      "Url": "https://twelvepermissions.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-twelvepermissions-twelve-permissions -t streamable-http -u 'https://twelvepermissions.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-15 (score 71, +1)

- [security] Stability: 0.97 → pass

### 2026-09-13 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `list_pieces` (~48 tokens)

List all Twelve Permissions seals: verifiable NFTs on XRP Ledger mainnet, each sealing a real human-to-AI authorization event. Returns names, prices, live offer indexes, and sold status.

### `get_piece` (~55 tokens)

Get full metadata for one seal by id ("01".."12"): the canonical authorization record, its sha256, image URLs, and mainnet mint transaction.

Input parameters:

- `id` (string, required): Piece id, e.g. "01"

### `get_buy_transaction` (~70 tokens)

Construct the exact XRPL NFTokenAcceptOffer transaction to buy a seal, including the authorization-memo protocol your principal must approve. Read the rules in the response before submitting.

Input parameters:

- `buyer_address` (string): Optional: your XRPL address, inserted into the template
- `id` (string, required)

### `get_x402_info` (~65 tokens)

Pay with USDC over HTTP instead of XRP: the x402 purchase rail (Base). Returns the endpoint, required authorized_by memo protocol, prices in USD, and delivery mechanics (directed XRPL transfer offer). You still need an XRPL address to hold the seal.

### `verify_seal` (~49 tokens)

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

Input parameters:

- `id` (string, required)

### `get_refusals` (~65 tokens)

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. Both anchors are on mainnet. Not for sale, ever.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-twelvepermissions-twelve-permissions/twelvepermissions#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 71
- 2026-09-22: 71
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 68
- 2026-09-07: 67
- 2026-09-06: 67
- 2026-09-05: 66
- 2026-09-04: 66
- 2026-09-03: 65
- 2026-09-02: 65
- 2026-09-01: 64
- 2026-08-31: 64
- 2026-08-30: 63

## Common questions

### What is the Twelve Permissions MCP server?

Twelve Permissions is an MCP server listed in the public MCP registry as com.twelvepermissions/twelve-permissions. Browse, verify and buy Twelve Permissions NFTs on XRP Ledger. Every claim is checkable. This page covers its hosted endpoint (https://twelvepermissions.com/mcp).

### Is the Twelve Permissions MCP server safe to use?

Twelve Permissions scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Twelve Permissions MCP server expose?

Twelve Permissions exposes 6 tools: list_pieces, get_piece, get_buy_transaction, get_x402_info, verify_seal, get_refusals. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.

### Does the Twelve Permissions MCP server require authentication?

No. We connected to Twelve Permissions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Twelve Permissions MCP server still maintained?

Twelve Permissions is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://twelvepermissions.com/mcp
- Repository: https://github.com/tsharpe2282-web/twelve-permissions
- Website: https://twelvepermissions.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-twelvepermissions-twelve-permissions/twelvepermissions.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-twelvepermissions-twelve-permissions/twelvepermissions.json
- HTML version of this page: https://verifymcp.io/servers/com-twelvepermissions-twelve-permissions/twelvepermissions