Turniermeister — Tournament Engine
REMOTE · APP.TURNIERMEISTER.AT · SCANNED OCT 4
Turnier engine: AI prepares a real tournament (bracket, schedule) and returns a claim link.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 802 tokens (~802/item across 1 items; 1 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Turniermeister — Tournament Engine MCP server?
Turniermeister — Tournament Engine is a hosted endpoint at https://app.turniermeister.at/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 · app.turniermeister.at
claude mcp add --transport http martymcflyjr-turniermeister 'https://app.turniermeister.at/mcp'
{
"mcpServers": {
"martymcflyjr-turniermeister": {
"url": "https://app.turniermeister.at/mcp"
}
}
} {
"servers": {
"martymcflyjr-turniermeister": {
"type": "http",
"url": "https://app.turniermeister.at/mcp"
}
}
} [mcp_servers.martymcflyjr-turniermeister] url = "https://app.turniermeister.at/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"martymcflyjr-turniermeister": {
"type": "remote",
"url": "https://app.turniermeister.at/mcp",
"enabled": true
}
}
} openclaw mcp add martymcflyjr-turniermeister --url 'https://app.turniermeister.at/mcp' --transport streamable-http
mcp_servers:
martymcflyjr-turniermeister:
url: "https://app.turniermeister.at/mcp" {
"McpServers": {
"martymcflyjr-turniermeister": {
"Transport": "http",
"Url": "https://app.turniermeister.at/mcp"
}
}
} assistant mcp add martymcflyjr-turniermeister -t streamable-http -u 'https://app.turniermeister.at/mcp'
{
"mcpServers": {
"martymcflyjr-turniermeister": {
"type": "http",
"url": "https://app.turniermeister.at/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 −1
- Tool “prepare_tournament” rewrote its description, which is the text the model reads security
- “prepare_tournament” reworded the description of “teamCount” cosmetic
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Oct 2026 · Probed https://app.turniermeister.at/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.turniermeister.at | CN=YE1,O=Let's Encrypt,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5426461d99dfcef1d9e5dd8bc875095aa57 |
| SANs: app.turniermeister.at | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.turniermeister.at. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| at. | present | 1253, 60960 | 13, 13 | Verified |
| turniermeister.at. | 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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; img-src 'self' data: blob: https://img.clerk.com; media-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' blob: https://clerk.turniermeister.at https://challenges.cloudflare.com wss://app.turniermeister.at; script-src 'self' https://clerk.turniermeister.at https://challenges.cloudflare.com; script-src-elem 'self' 'sha256-yei5Fza+Eyx4G0smvN0xBqEesIKumz6RSyGsU3FJowI=' https://clerk.turniermeister.at https://challenges.cloudflare.com; script-src-attr 'unsafe-hashes' 'sha256-MhtPZXr7+LpJUY5qtMutB+qWfQtMaPccfe7QXtCcEYc='; style-src 'self' 'unsafe-inline'; style-src-elem 'self' 'unsafe-inline' blob:; frame-src 'self' https://clerk.turniermeister.at https://challenges.cloudflare.com; frame-ancestors 'self'; worker-src 'self' blob:; manifest-src 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.turniermeister.at/mcp | Verified | 200 | |
| http (plaintext) | http://app.turniermeister.at/mcp | HTTPS enforced | 308 | https://app.turniermeister.at/mcp |
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 →
prepare_tournament Prepare a Turniermeister tournament ~731
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. - 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).
| Name | Type | Req | Description |
|---|---|---|---|
| clientInfo | string | – | Optional free-form identifier of the calling agent, used for funnel attribution only. |
| competitionType | string | – | Fixed to "bracket" — other competition types are not exposed yet. |
| idempotencyKey | string | yes | Unique key for this preparation request (UUID). Same key returns the same preparation instead of a duplicate. |
| mode | integer | yes | Tournament mode as a numeric ITournamentMode value from the Turniermeister catalog. Values: 0 = knockout (single elimination), 1 = double elimination, 2 = single-day league, 3 = swiss system, 4 = mul… |
| name | string | yes | Tournament name as agreed with the user. Max 120 chars. |
| participants | array | – | Participant names, ONLY when the user explicitly provided them. Stored encrypted and migrated at claim time. |
| teamCount | integer | – | Number of teams. Required unless participants are supplied. Must match participants length if both are given. The app supports up to 250 teams (8 for single-day league mode, or 128 with mode 2 and te… |
| templateKey | string | – | Optional catalog template key (e.g. preset-padel). Omit instead of guessing. |
No output schema declared.
No examples provided.
What is the Turniermeister — Tournament Engine MCP server?
Turniermeister — Tournament Engine is an MCP server listed in the public MCP registry as io.github.MartyMcFlyJr/turniermeister. Turnier engine: AI prepares a real tournament (bracket, schedule) and returns a claim link. This page covers its hosted endpoint (https://app.turniermeister.at/mcp).
Is the Turniermeister — Tournament Engine MCP server safe to use?
Turniermeister — Tournament Engine scores 76 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 Turniermeister — Tournament Engine MCP server expose?
Turniermeister — Tournament Engine exposes 1 tool: prepare_tournament. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.
Does the Turniermeister — Tournament Engine MCP server require authentication?
No. We connected to Turniermeister — Tournament Engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Turniermeister — Tournament Engine MCP server still maintained?
Turniermeister — Tournament Engine is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.