royaltea-public

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

Sollte ich dies verwenden

Qualität und Sicherheit

B
Qualität der Beschreibung
92%
Vollständigkeit des Schemas
84%
Qualität der Benennung
88%
Risiko der Vergiftung
80%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Befunde (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'prepare_studio_setup' description contains placeholder textin prepare_studio_setup
  • INFOTool description contains placeholder or incomplete textin prepare_studio_setup

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,452Tokens (Tool-Definitionen)
~2.4 KBTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (1.13% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "royaltea-public": {
      "url": "https://api.royalty.technology/api/public-mcp"
    }
  }
}

Remote-Endpunkte

https://api.royalty.technology/api/public-mcpstreamable-http

Was es kann

Tool-Inventar

Tools (5)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢calculate_revenue_split(revenue, platform, lifetimeRevenue, unrealEngine, lifetimeGross, ...)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "revenue": {
      "type": "number",
      "description": "Gross revenue / player spend to model (e.g. 50000)"
    },
    "platform": {
      "type": "string",
      "enum": [
        "steam",
        "epic",
        "epic_first_run",
        "apple",
        "google_play",
        "console",
        "itch",
        "direct"
      ],
      "description": "Storefront the revenue comes from. Omit if the money is already net of platform fees."
    },
    "lifetimeRevenue": {
      "type": "number",
      "description": "Revenue already earned on this platform in the tiering period (drives Steam $10M/$50M tiers and Epic/Apple/Google $1M thresholds). Default 0."
    },
    "unrealEngine": {
      "type": "boolean",
      "description": "Game built on Unreal Engine? Applies the 5% royalty on gross above $1M lifetime (waived on Epic)."
    },
    "lifetimeGross": {
      "type": "number",
      "description": "Lifetime gross so far (for the Unreal $1M royalty threshold). Default 0."
    },
    "publisherCut": {
      "type": "number",
      "description": "Optional % a publisher takes off the top after platform fees (0-100)"
    },
    "expenses": {
      "type": "number",
      "description": "Optional costs to subtract before the contributor pool (marketing, tools, etc.)"
    },
    "poolPercentage": {
      "type": "number",
      "description": "% of net revenue that goes to the contributor pool vs staying with the studio (default 100)"
    },
    "platformCutOverride": {
      "type": "number",
      "description": "For itch/direct: the storefront cut fraction 0-1 (e.g. 0.05)."
    },
    "contributors": {
      "type": "array",
      "description": "The people sharing the contributor pool. `points` is a relative weight (bigger = larger share); if you only know rough effort, use 1-10.",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "points": {
            "type": "number",
            "description": "Relative contribution weight"
          },
          "role": {
            "type": "string",
            "description": "Optional role (e.g. Programmer, Artist)"
          }
        },
        "required": [
          "name"
        ]
      }
    }
  },
  "required": [
    "revenue",
    "contributors"
  ]
}
🟢get_platform_cuts(platform)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "platform": {
      "type": "string",
      "enum": [
        "steam",
        "epic",
        "epic_first_run",
        "apple",
        "google_play",
        "console",
        "itch",
        "direct"
      ],
      "description": "Optional: one platform; omit for all."
    }
  }
}
🟢draft_revenue_agreement(companyName, contributorName, projectName, services, contributorSharePercent, ...)

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'.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "companyName": {
      "type": "string",
      "description": "The studio/company granting the revenue share"
    },
    "contributorName": {
      "type": "string",
      "description": "The person (or company) receiving the revenue share"
    },
    "projectName": {
      "type": "string",
      "description": "The project/game the agreement covers"
    },
    "services": {
      "type": "string",
      "description": "What the contributor will do (Schedule A — e.g. \"gameplay programming and tools\")"
    },
    "contributorSharePercent": {
      "type": "number",
      "description": "The contributor's flat % of revenue (use this OR revenueTiers)"
    },
    "revenueTiers": {
      "type": "array",
      "description": "Tiered revenue share (Schedule B): different % across revenue bands.",
      "items": {
        "type": "object",
        "properties": {
          "from": {
            "type": "number"
          },
          "to": {
            "type": "number",
            "description": "null/omit for \"and above\""
          },
          "contributorSharePercent": {
            "type": "number"
          }
        },
        "required": [
          "from",
          "contributorSharePercent"
        ]
      }
    },
    "contributorIsCompany": {
      "type": "boolean"
    },
    "companyState": {
      "type": "string",
      "description": "Governing-law state/jurisdiction (e.g. \"Delaware\")"
    },
    "effectiveDate": {
      "type": "string",
      "description": "e.g. 2026-08-01; defaults to a placeholder"
    }
  },
  "required": [
    "companyName",
    "contributorName",
    "projectName"
  ]
}
⚪prepare_studio_setup(studioName, projectName, collaborators, splitNote, contactEmail)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "studioName": {
      "type": "string",
      "description": "Name for the new studio/workspace"
    },
    "projectName": {
      "type": "string",
      "description": "Optional first project name"
    },
    "collaborators": {
      "type": "array",
      "description": "The people on the project (added as placeholders they can later claim). `points` is their relative revenue weight.",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "role": {
            "type": "string"
          },
          "points": {
            "type": "number"
          }
        },
        "required": [
          "name"
        ]
      }
    },
    "splitNote": {
      "type": "string",
      "description": "Optional human summary of the intended split/terms"
    },
    "contactEmail": {
      "type": "string",
      "description": "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."
    }
  },
  "required": [
    "studioName"
  ]
}
🟢explain_royaltea

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {}
}

Empfohlene Prompts

retrieve_data
Get details about [item] from royaltea-public
Erwartete Tools: get_platform_cuts
fetch_info
Fetch [information type] using royaltea-public
Erwartete Tools: get_platform_cuts

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet5 Tools
verifiziertVersion nicht aufgezeichnet5 Tools