Mmcp.market

Turniermeister — Tournament Engine MCP server

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.

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

full report

Adoption
Growing

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-schnapsen). Do not guess unknown keys — omit it instead. - 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. - Validation problems come back as structured errors: fix your input from the error JSON 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.9 · 2026-09-20 · same rubric, same numbers if you re-run it

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

Install directly

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

Turniermeister — Tournament Engine: common questions

Is Turniermeister — Tournament Engine MCP server safe?
Yes, by our scan: it is graded A (91/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, Claude Desktop or Cursor 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 14 days ago (2026-09-06). The latest release is v1.0.0.
Is Turniermeister — Tournament Engine up?
100% of our last 6 checks got an answer. We check remote servers about four times a day.

More from MartyMcFlyJr →