MCP.Market

Twelve Permissions MCP server

online · 100% uptime
by twelvepermissions.com·com.twelvepermissions/twelve-permissions·v1.0.0
No reviews yet

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

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Twelve Permissions yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Twelve Permissions tools (6, 2 write)

write = sends, deletes, buys or posts
  • get_buy_transactionwrite actionFree

    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.

  • get_pieceFree

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

  • get_refusalsFree

    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.

  • get_x402_infowrite actionFree

    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.

  • list_piecesFree

    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.

  • verify_sealFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 556ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 56 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Twelve Permissions compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
43 ms
faster than 93% of 30,031 servers

What its tools let an agent do: 4 read · 2 change

Install Twelve Permissions in Claude Code, Cursor or VS Code

claude mcp add --transport http twelve-permissions https://twelvepermissions.com/mcp
Add to Cursor

What the publisher says

From the Twelve Permissions repository's README, as published. We do not edit it. Read it on GitHub

Twelve Permissions — verification apparatus

Twelve NFTs on XRP Ledger mainnet. Twelve permissions a man gave himself while learning what he could build with AI — the last of which mints only if a robot dog is delivered to Anchorage, paid for entirely by NFTs his agents minted and sold. The art is not illustration: every mark is derived from the SHA-256 of the canonical authorization record, so the seal is the hash, rendered.

This repository exists so you don't have to take any of that on trust. It holds the generator, the canonical records, and the server source. Re-run them yourself.

Collection: Issuer: rHEiuaYLNQ4UdLqeUrnE9AwEHqsDMr9g9R (taxon 12, 5% royalty)

Verify a seal from first principles

No dependencies. Node only.

node generate.js            # regenerates every seal from events.json
git status                  # should report no changes

The second line is the test. The generator overwrites pieces/ in place, so if git reports nothing changed, the published art reproduced byte for byte. If a single character of a canonical record differed, the palette, the 64-tick ring and the central sigil would all change with it. Forging a seal means breaking SHA-256.

To check one piece end to end:

explorer.

  1. Read its canonical record in events.json.
  2. Take the SHA-256 of that record — it is committed in the NFT's on-chain URI.
  3. Re-run the generator and compare the art, byte for byte.
  4. Look up the mint transaction in records/minted.mainnet.json on any XRPL

VERIFY.md has the long version.

What's here

Two artifacts, and only one of them proves anything

Each piece has two images, and the difference matters:

SHA-256 of its record by generate.js. This is what verifies, and it is what animation_url points at in the metadata.

  • pieces/NN.svg — the canonical seal. Derived deterministically from the

field artwork by compose-art.js. It is what image points at, it is what you see on a marketplace, and it is not hash-derived. The field art is decorative.

  • NN.png — the display image. The same seal composited over generated

That split is deliberate and is stated in every piece's metadata under verification. Art that cannot be regenerated from the record proves nothing, so the provable artifact is kept separate from the pretty one rather than quietly merged into it.

PNGs are not committed here because they are large and are display-only. Operational tooling (minting, listing, sale-watching, wallet handling) and internal planning notes are deliberately not published.

The MCP server

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Twelve Permissions: common questions

Is Twelve Permissions MCP server safe?
Mostly: it is graded B (77/100). Read the Twelve Permissions safety report
How do I install Twelve Permissions?
It runs remotely at twelvepermissions.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Twelve Permissions need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Twelve Permissions maintained?
The last commit was 57 days ago (2026-09-08). The latest release is v1.0.0.
Is Twelve Permissions up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Twelve Permissions compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.