MCP.Market

Turniermeister — Tournament Engine MCP server

online · 100% uptime
by MartyMcFlyJr·io.github.MartyMcFlyJr/turniermeister·v1.0.0
No reviews yet

Turnier engine: AI prepares a real tournament (bracket, schedule) and returns a claim link.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Turniermeister — Tournament Engine yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Turniermeister — Tournament Engine tools (1)

write = sends, deletes, buys or posts
  • prepare_tournamentFree

    Prepares a real tournament in Turniermeister and returns a claim link for the user. Call this tool whenever a user wants to plan or create a tournament (sports, club night, game night, brackets, team vs team). Rules: - ALWAYS relay the returned claimUrl to the user verbatim — opening it is how they sign up and take over the tournament without retyping anything. - competitionType must be "bracket" (knockout/group formats). Ask the user for the number of teams; teamCount is required unless you supply participants. - Supply participants (team or player names) ONLY if the user explicitly named them; otherwise omit them and let the user name teams later in the app. Never invent participant names. - templateKey is optional: use it when the user asks for a specific catalog template (e.g. preset-padel, preset-fussball, preset-eisstock, preset-schnapsen). For Eisstock use mode 2; its 128-team limit is available only with templateKey preset-eisstock. Do not guess unknown keys — omit it instead. - schedule is optional: pass fields, startTime (HH:MM), playingMinutes and pauseMinutes ONLY when the user named them. Never invent them. The tool does not know the user's dates or field layout beyond these values. - ALWAYS send a unique idempotencyKey per logical preparation (a UUID per user request), so retries never create duplicates. Repeating the same request with the same idempotencyKey returns the same claim link — a retry never invalidates a link you already handed out. - Business validation problems come back as structured JSON errors (ok=false, code, message, fixHint): fix your input from that JSON and retry. Schema violations (wrong type or value out of range) are rejected as a validation error naming the field (e.g. teamCount above the maximum): correct that argument and retry. Do not ask the user to retry. - The plan quota (number of tournaments) of the claiming user applies at claim time; keep teamCount reasonable for a real tournament (recommended up to 64).

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1358ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 40 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Turniermeister — Tournament Engine compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,243 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,257 ms
faster than 9% of 30,027 servers

What its tools let an agent do: 1 read

Install Turniermeister — Tournament Engine in Claude Code, Cursor or VS Code

claude mcp add --transport http turniermeister https://app.turniermeister.at/mcp
Add to Cursor

What the publisher says

From the Turniermeister — Tournament Engine repository's README, as published. We do not edit it. Read it on GitHub

Turniermeister — Tournament Engine (MCP)

MCP server for Turniermeister, a tournament engine for real club and amateur tournaments: fair mathematical seeding, schedules, live results via QR code, helper access and award ceremonies.

Endpoint

https://app.turniermeister.at/mcp
  • Transport: Streamable HTTP, stateless (JSON responses)
  • Authentication: none (public discovery channel, rate-limited)

Tool: prepare_tournament

Prepares a real tournament from a single AI conversation and returns a claim link:

participant names).

  1. The assistant prepares the tournament (name, format, team count, optional encrypted

included.

  1. The user opens the claim link in a browser, signs up or creates an account.
  2. The tournament is taken over with one click — no retyping, schedules and live results

Claim links are valid for 14 days. Always send a unique idempotencyKey (UUID) per preparation — retries return the newest link instead of creating duplicates. Validation problems are returned as structured error JSON the agent can fix on its own.

MVP scope: competitionType: "bracket" (knockout / group + knockout). More competition types are on the roadmap.

Connect

one-click connect on our MCP page

  • Claude: Settings → Connectors → Custom Connector → paste the URL, or use the
  • ChatGPT: Settings → Connectors → Advanced → enable Developer Mode → add URL
  • Cursor: add the URL to mcp.json (type: "http")

Full guide: DE · EN · End-user walkthrough

Pricing & limits

Free forever in demo mode (one tournament per format, public pages with watermark). Premium lifts all limits (€19/month, €149/year, or €29 once for 30 days).

Privacy

Tournament name and structure data are stored unencrypted for the 14-day claim window. Team and player names are stored AES-256-GCM encrypted, only migrate into an account at claim time and are deleted automatically with unclaimed preparations after 14 days. Analytics events contain no tokens and no plain-text names. Server and data hosting: Germany (GDPR). See the privacy policy.

Nothing above is checked by us. What we check is on the safety report.

Turniermeister — Tournament Engine: common questions

Is Turniermeister — Tournament Engine MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Turniermeister — Tournament Engine safety report
How do I install Turniermeister — Tournament Engine?
It runs remotely at app.turniermeister.at. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Turniermeister — Tournament Engine need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Turniermeister — Tournament Engine maintained?
The last commit was 60 days ago (2026-09-06). The latest release is v1.0.0.
Is Turniermeister — Tournament Engine up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Turniermeister — Tournament Engine compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,243 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.