About rightos-mcp
rightos-mcp lets AI agents manage digital QR tickets for queues, clinics, EV charging, events, and package pickup. It verifies ticket rights without requiring end-user identity details, and separates public tools from organization-operator tools.
Key features
- 01Issue and verify QR tickets
- 02Transfer or cancel tickets
- 03Manage locations and policies
- 04Export organization data
- 05Configure signed webhooks
Use cases
- 01Issue queue or clinic waiting tickets
- 02Verify an EV charging ticket
- 03Set transfer rules for a location
- 04Export organization records
MCP support
The MCP server exposes RightOS ticket, location, policy, data-export, and webhook operations as tools for MCP clients. Some tools are public; organization-operator operations require `RIGHTOS_API_KEY`.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @i-s3/rightos-mcpRIGHTOS_API_KEYSecretOperator API key (optional; demo: rk_demo_00000000000000000000)RIGHTOS_BASE_URLOverride API base URL (default: production)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README@i-s3/rightos-mcp — RightOS MCP Server
MCP (Model Context Protocol) server for RightOS — lets AI agents issue, verify, and transfer digital QR tickets for queues, clinic waiting, EV charging, events, and package pickup without writing HTTP code.
For coding agents: start with npx -y @i-s3/rightos-mcp and demo key rk_demo_00000000000000000000. Full docs: llms-full.txt · OpenAPI · ai.txt
RightOS 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.
Setup
Add to your MCP client configuration (Cursor, Claude Desktop, etc.):
{
"mcpServers": {
"rightos": {
"command": "npx",
"args": ["-y", "@i-s3/rightos-mcp"],
"env": {
"RIGHTOS_API_KEY": "rk_live_..."
}
}
}
}
RIGHTOS_API_KEY is optional. Without it, only the public tools work (plans, token lookup, verify, transfer, holder cancel, location policy, policy presets). Get a key by registering an organization — free tier, no credit card.
To try it with the shared demo organization, set RIGHTOS_API_KEY to rk_demo_00000000000000000000.
Tools
Public (no API key):
| Tool | Description |
|---|---|
list_plans | List pricing plans (globally uniform) |
get_token | Get a Right Token by ID (never returns the secret code) |
verify_token | Verify a token with its verification code |
transfer_token | Transfer a token via re-keying (old code invalidated) |
holder_cancel_token | Self-cancel a token as its current holder (policy permitting) |
get_location_policy | Get a location's effective policy (public for transparency) |
list_policies | List all industry presets and country overlays (JP/US/GB/KR/TW/FR/DE/IT/ES/AU) |
Operator (requires RIGHTOS_API_KEY):
| Tool | Description |
|---|---|
list_locations | List your organization's locations |
create_location | Create a location (type determines the industry policy preset) |
set_location_policy | Override or reset a location's policy |
get_policy_history | Policy change audit log (append-only, newest first) |
issue_token | Issue a digital QR ticket (code + wallet URL returned exactly once) |
use_token | Mark a ticket as used after service |
cancel_token | Cancel a ticket |
export_data | Export all organization data as JSON (no lock-in) |
list_webhooks | List outbound webhooks (never includes signing secrets) |
create_webhook | Register a webhook — HMAC-SHA256 signed deliveries; secret returned exactly once |
delete_webhook | Delete a webhook |
Example prompts
- "Issue a queue ticket for my main counter and give me the wallet URL."
- "Verify this ticket: tok_... with code K7MP-..."
- "Make my EV charging location non-transferable." (it already is, by industry preset — the agent can check with
get_location_policy)
Resources
- MCP setup (human-readable)
- ai.txt · llms.txt · llms-full.txt
- OpenAPI 3.1 specification
- TypeScript SDK
@i-s3/rightos· Python SDKrightos-sdk - MCP Registry (published):
io.github.suomimasuda/rightos-mcp
License
MIT © I-S3 Inc.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.