Rightos Sdk MCP Server

RightOS SDKs

Official SDKs for RightOS — privacy-preserving rights verification infrastructure by I-S3 (Japan).

RightOS turns queues, reservations, EV charging, and package pickup into digital QR tickets ("Right Tokens"). It verifies that a valid right is present — never who the person is. No names, phone numbers, or birthdates are required from end users.

RightOS is not a taxi or ride-hailing service. It does not arrange vehicles, set fares, assign drivers, or broker dispatch.

SDKs

Both SDKs are zero-dependency single files — install via a package manager or just download the file.

MCP server (for AI agents)

mcp/ — @i-s3/rightos-mcp: an MCP server that gives AI agents (Cursor, Claude Desktop, etc.) 12 tools for issuing, verifying, and transferring Right Tokens.

{
  "mcpServers": {
    "rightos": {
      "command": "npx",
      "args": ["-y", "@i-s3/rightos-mcp"],
      "env": { "RIGHTOS_API_KEY": "rk_live_..." }
    }
  }
}

Quick example (TypeScript)

import { RightOS } from "@i-s3/rightos";

const client = new RightOS({ apiKey: "rk_live_..." });
const [location] = await client.listLocations();
const issued = await client.issueToken({ locationId: location.id, title: "Queue ticket" });
// Hand issued.walletUrl (QR page) to your customer
const outcome = await RightOS.verify(issued.token.id, issued.verificationCode);
// outcome.result === "success"

Quick example (Python)

from rightos import RightOS

client = RightOS(api_key="rk_live_...")
location = client.list_locations()[0]
issued = client.issue_token(location_id=location["id"], title="Queue ticket")
outcome = RightOS().verify_token(issued["token"]["id"], issued["verificationCode"])
# outcome["result"] == "success"

Resources

• Developer documentation
• OpenAPI 3.1 specification
• Full documentation for AI agents (llms-full.txt)
• Pricing — globally uniform, free tier available, no credit card required
• Try the live demo without registration: shared demo key rk_demo_00000000000000000000

Privacy & security design

• The verification code is handed to the holder exactly once; the server stores only its SHA-256 hash.
• Transfers use re-keying: a new code is issued and the old one is invalidated immediately.
• QR codes contain only the tokenId and verificationCode — no personal data.
• Paid transfers and auctions are not offered.

License

MIT © I-S3 Inc.