Skip to content

technology.royalty/royaltea-public

by royalty.technology · remote · no sign-in to list tools · v1.0.0 · published by technology.royalty

Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup.

Changes · 3
CompareRegistry entry

5 tools: 3 change things and 2 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http royaltea-public https://api.royalty.technology/api/public-mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warndraft_revenue_agreement

    The server marks "draft_revenue_agreement" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The description's first verb is "generate": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 3Claude Code: ask
  • calculate_revenue_splitModel 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,…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Calculate Revenue Split
    • readOnlyHint: true
  • draft_revenue_agreementGenerate 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…1 finding

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "draft_revenue_agreement" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The description's first verb is "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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'.

    Annotations the server declares

    • title: Draft Revenue Agreement
    • readOnlyHint: true
  • prepare_studio_setupTurn a plan (studio name, project, collaborators, intended split) into a ONE-CLICK setup link for someone who doesn't have a RoyalTea account yet.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Prepare Studio Setup
    • readOnlyHint: false
    • destructiveHint: false
Only reads 2Claude Code: allow
  • explain_royalteaExplain what RoyalTea is and how it helps creative teams track contributions and split revenue fairly.No findings

    Why it is in this group

    • The name "explain_royaltea" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain Royaltea
    • readOnlyHint: true
  • get_platform_cutsThe 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 U…No findings

    Why it is in this group

    • The name "get_platform_cuts" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Platform Cuts
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http royaltea-public https://api.royalty.technology/api/public-mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__royaltea-public__get_platform_cuts",
      "mcp__royaltea-public__explain_royaltea"
    ],
    "ask": [
      "mcp__royaltea-public__calculate_revenue_split",
      "mcp__royaltea-public__draft_revenue_agreement",
      "mcp__royaltea-public__prepare_studio_setup"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as royaltea-public. Review it before you use it.