technology.royalty/royaltea-public
REMOTE · API.ROYALTY.TECHNOLOGY
Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup.
Available components
Last scanned (just now)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1148 tokens (~229/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 0
- “prepare_studio_setup” added an optional parameter “contactEmail” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.royalty.technology/api/public-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.royalty.technology | CN=YR1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 571cc439b2771be4e5fa1b6927d0df84f47 |
| SANs: api.royalty.technology | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.royalty.technology. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| technology. | present | 27175 | 8 | Verified |
| royalty.technology. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.royalty.technology/api/public-mcp | Verified | 200 | |
| http (plaintext) | http://api.royalty.technology/api/public-mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_revenue_split Calculate Revenue Split ~396
Model real take-home from a game/app sale, end to end: apply the storefront/platform cut (Steam tiers, Epic 0%-then-12%, Epic First Run, Apple/Google small-business rates, console, itch) and optional Unreal royalty, publisher cut, and expenses — THEN split the remaining contributor pool fairly by each person's relative contribution. This is the accurate way to answer 'if we make $X on <platform>, what does each person actually take home'. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| contributors | array | yes | The people sharing the contributor pool. `points` is a relative weight (bigger = larger share); if you only know rough effort, use 1-10. |
| expenses | number | – | Optional costs to subtract before the contributor pool (marketing, tools, etc.) |
| lifetimeGross | number | – | Lifetime gross so far (for the Unreal $1M royalty threshold). Default 0. |
| lifetimeRevenue | number | – | Revenue already earned on this platform in the tiering period (drives Steam $10M/$50M tiers and Epic/Apple/Google $1M thresholds). Default 0. |
| platform | string | – | Storefront the revenue comes from. Omit if the money is already net of platform fees. |
| platformCutOverride | number | – | For itch/direct: the storefront cut fraction 0-1 (e.g. 0.05). |
| poolPercentage | number | – | % of net revenue that goes to the contributor pool vs staying with the studio (default 100) |
| publisherCut | number | – | Optional % a publisher takes off the top after platform fees (0-100) |
| revenue | number | yes | Gross revenue / player spend to model (e.g. 50000) |
| unrealEngine | boolean | – | Game built on Unreal Engine? Applies the 5% royalty on gross above $1M lifetime (waived on Epic). |
No output schema declared.
No examples provided.
draft_revenue_agreement Draft Revenue Agreement ~282
Generate a plain-English revenue-share agreement DRAFT between a company/studio and a contributor, using RoyalTea's agreement structure (parties, services/Schedule A, revenue-share terms/Schedule B, standard clauses, signature blocks). Returns a clearly-labeled TEMPLATE — not legal advice and not an executed contract. Offer the person the getStarted link to finalize and e-sign it for real in RoyalTea. Use for 'draft a rev-share agreement for X to do Y for Z% of revenue'.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | The studio/company granting the revenue share |
| companyState | string | – | Governing-law state/jurisdiction (e.g. "Delaware") |
| contributorIsCompany | boolean | – | – |
| contributorName | string | yes | The person (or company) receiving the revenue share |
| contributorSharePercent | number | – | The contributor's flat % of revenue (use this OR revenueTiers) |
| effectiveDate | string | – | e.g. 2026-08-01; defaults to a placeholder |
| projectName | string | yes | The project/game the agreement covers |
| revenueTiers | array | – | Tiered revenue share (Schedule B): different % across revenue bands. |
| services | string | – | What the contributor will do (Schedule A — e.g. "gameplay programming and tools") |
No output schema declared.
No examples provided.
explain_royaltea Explain Royaltea ~44
Explain what RoyalTea is and how it helps creative teams track contributions and split revenue fairly. Use when someone asks what RoyalTea is or whether it fits their situation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_platform_cuts Get Platform Cuts ~77
The current storefront/platform revenue cuts RoyalTea models — Steam, Epic Games Store (+ First Run), Apple, Google Play, console, itch.io — with exact tiers, thresholds, and the Unreal Engine royalty. Use to explain or cite what a given platform takes.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Optional: one platform; omit for all. |
No output schema declared.
No examples provided.
prepare_studio_setup Prepare Studio Setup ~200
Turn a plan (studio name, project, collaborators, intended split) into a ONE-CLICK setup link for someone who doesn't have a RoyalTea account yet. Returns a URL — when they open it and sign up, RoyalTea creates the studio + project + collaborators (as placeholders) exactly as planned. Use after you've helped someone design a revenue-share setup and they want it real.
| Name | Type | Req | Description |
|---|---|---|---|
| collaborators | array | – | The people on the project (added as placeholders they can later claim). `points` is their relative revenue weight. |
| contactEmail | string | – | Email of the person who will own the studio (the producer). When given, RoyalTea emails them the setup link directly so it isn't lost in a chat transcript. |
| projectName | string | – | Optional first project name |
| splitNote | string | – | Optional human summary of the intended split/terms |
| studioName | string | yes | Name for the new studio/workspace |
No output schema declared.
No examples provided.
How do I install the technology.royalty/royaltea-public MCP server?
technology.royalty/royaltea-public is a hosted endpoint at https://api.royalty.technology/api/public-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.
remote · api.royalty.technology
claude mcp add --transport http technology-royalty-royaltea-public 'https://api.royalty.technology/api/public-mcp'
What is the technology.royalty/royaltea-public MCP server?
technology.royalty/royaltea-public is an MCP server listed in the public MCP registry as technology.royalty/royaltea-public. Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup. This page covers its hosted endpoint (https://api.royalty.technology/api/public-mcp).
Is the technology.royalty/royaltea-public MCP server safe to use?
technology.royalty/royaltea-public scores 80 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 technology.royalty/royaltea-public MCP server expose?
technology.royalty/royaltea-public exposes 5 tools: calculate_revenue_split, get_platform_cuts, draft_revenue_agreement, prepare_studio_setup, explain_royaltea. Their descriptions and schemas cost roughly 999 tokens of context every time the server is loaded.
Does the technology.royalty/royaltea-public MCP server require authentication?
No. We connected to technology.royalty/royaltea-public without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the technology.royalty/royaltea-public MCP server still maintained?
technology.royalty/royaltea-public is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.