Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Turniermeister — Tournament Engine

REMOTE · APP.TURNIERMEISTER.AT

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

0 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 930 tokens (~930/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Oct 26 0
    • Tool “prepare_tournament” rewrote its description, which is the text the model reads security
    • “prepare_tournament” added an optional parameter “schedule” cosmetic
  • 12 Oct 26 0
    • Tool “prepare_tournament” rewrote its description, which is the text the model reads security
  • 9 Oct 26 0
    • Stability: 0.93 → pass security
Diagnostics

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 21 Nov 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 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA384 5b6e1f1c7cdbf2b62aa9e8f9109f2064422
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. DS published 1253, 60960 13, 13 Verified
turniermeister.at. No DS 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
MCP tools · 1 exposed · ~859 tokens

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 →

Tool Tokens
prepare_tournament ~859

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

NameTypeReqDescription
clientInfostring–Optional free-form identifier of the calling agent, used for funnel attribution only.
competitionTypestring–Fixed to "bracket" — other competition types are not exposed yet.
idempotencyKeystringyesUnique key for this preparation request (UUID). Same key returns the same preparation instead of a duplicate.
modeintegeryesTournament 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…
namestringyesTournament name as agreed with the user. Max 120 chars.
participantsarray–Participant names, ONLY when the user explicitly provided them. Stored encrypted and migrated at claim time.
scheduleobject–Optional schedule. Set only the values the user explicitly named; omitted values keep the app defaults and can be changed in the app after the takeover.
teamCountinteger–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…
templateKeystring–Optional catalog template key (e.g. preset-padel). Omit instead of guessing.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http martymcflyjr-turniermeister 'https://app.turniermeister.at/mcp'
Common questions

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 78 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 859 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Turniermeister — Tournament Engine MCP server?

VerifyMCP ran 12 checks on Turniermeister — Tournament Engine, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Turniermeister — Tournament Engine: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.