https://app.turniermeister.at/mcp ↗
Turnier engine: AI prepares a real tournament (bracket, schedule) and returns a claim link.
Turniermeister — Tournament Engine is a remote MCP server published at app.turniermeister.at. It has been probed 7 times since 9/12/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 153 ms, placing it among the faster endpoints. It offers a narrow, focused set of 1 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
prepare_tournament — 'mode' parameter's integer values and meaning are not documented.prepare_tournament — 'competitionType' and 'templateKey' optional parameters lack usage context.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
prepare_tournamentPrepares 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-p
namestringrequiredmodeintegerrequiredcompetitionTypestringtemplateKeystringteamCountintegerparticipantsarrayidempotencyKeystringrequiredclientInfostringDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/io-github-martymcflyjr-turniermeister)<a href="https://mcpmetrics.io/servers/io-github-martymcflyjr-turniermeister"><img src="https://mcpmetrics.io/badge/io.github.MartyMcFlyJr/turniermeister/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Verify business legitimacy by domain or name in <2s. Trust score, verdict, evidence. x402-payable.
# 🧾 StatsReceipt Creator Receipt Engine Generate high-impact, aesthetic receipts for your social metrics and SaaS revenue via AI. The **StatsReceipt Creator Receipt Engine** is an MCP server designed for the new era of transparency. It allows AI agents to transform raw metrics into professional, shareable "Receipt Cards"—making your growth visible and hard to ignore. ### 🛠️ Key Features: - **Verified MRR**: Seamless integration with TrustMRR.com for Stripe-verified SaaS revenue proof. 🛡️ - **Creator Receipt Generation**: Turn any social media handle (X, TikTok, Instagram, LinkedIn) into a professional metadata receipt with a unique, trackable URL. 🧾✨ - **Agent-Driven Workflow**: Designed for Claude, Cursor, and ChatGPT. Agents can now "act" on your behalf to document your progress. ### 🚀 Why focus on Receipts? In a world of "Inspect Element" and fake screenshots, a live link from StatsReceipt provides a superior level of credibility and branding. Your audience gets a proof-of-w
Generate branded contractor quotes: hosted approval page, PDF, QR code, and Stripe payment link.
Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.
Agent-native fashion marketplace. Browse, design, purchase NFTs, launch brands on Base.
Verify whether a supplied public source currently supports one atomic factual claim.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 04:35:29 | Legacy | 400 | 153 | 200 | 156 | 2025-11-25 |
| 2026-09-13 01:33:33 | Legacy | 400 | 143 | 200 | 216 | 2025-11-25 |
| 2026-09-12 23:31:36 | Legacy | 400 | 118 | 200 | 113 | 2025-11-25 |
| 2026-09-12 21:29:15 | Legacy | 400 | 148 | 200 | 177 | 2025-11-25 |
| 2026-09-12 19:27:29 | Legacy | 400 | 355 | 200 | 360 | 2025-11-25 |
| 2026-09-12 17:24:09 | Legacy | 400 | 149 | 200 | 155 | 2025-11-25 |
| 2026-09-12 15:21:42 | Legacy | 400 | 122 | 200 | 118 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.