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.

POFA Tournaments

REMOTE · POFA.APP

Run small tennis & pickleball tournaments from your AI assistant: brackets, schedules, results.

Available components

+3 this week 64 Trust /100

Last scanned (22 hours ago)

Scores higher than 46% 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 Security49
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4042 tokens (~212/item across 19 items; 18 tools + 1 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 Management43
  • Stability observed for 13 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_tournament" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities47
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (13)

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

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

  • 21 Nov 26 0
    • Tool “get_schedule” rewrote its description, which is the text the model reads security
  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • New resource “POFA Tournament Console” functional
    • Server version: 1.4.4 → 1.5.2 functional
    • New tool “get_event_context” functional
    • New tool “open_tournament_console” functional
  • 12 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_tournament” rewrote its description, which is the text the model reads security
    • Tool “import_players” rewrote its description, which is the text the model reads security
    • Tool “register_player” rewrote its description, which is the text the model reads security
    • Destructive annotations: pass → 0 functional
    • Server version: 1.4.2 → 1.4.4 functional
    • New tool “delete_tournament” functional
    • “import_players” reworded the description of “players” cosmetic
  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_schedule” rewrote its description, which is the text the model reads security
    • Tool “report_result” rewrote its description, which is the text the model reads security
    • Tool “schedule_matches” rewrote its description, which is the text the model reads security
    • Tool “screen_clear” rewrote its description, which is the text the model reads security
    • Schema quality: 196 → 224 ▼ functional
    • Server version: 1.3.0 → 1.4.2 functional
    • New tool “get_activity_log” functional
    • New tool “get_bracket” functional
    • New tool “get_roster” functional
    • “report_result” added an optional parameter “expect_score” cosmetic
    • “report_result” added an optional parameter “expect_winner” cosmetic
    • “report_result” added an optional parameter “undo_preview” cosmetic
    • “screen_clear” added an optional parameter “all” cosmetic
    • “generate_bracket” reworded the description of “players” cosmetic
    • “import_players” reworded the description of “players” cosmetic
    • “register_player” reworded the description of “name” cosmetic
    • “report_result” reworded the description of “score_sets” cosmetic
    • “screen_clear” reworded the description of “court” cosmetic
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://pofa.app/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pofa.app CN=YE1,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 51782dc2fe5000bc2b165cd09706c6ba9ad
SANs: *.pofa.app, pofa.app
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 secure

Validation of pofa.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
pofa.app. DS published 2371 13 Verified
pofa.app. Verified address RRset verified with the apex keys
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pofa.app/mcp/ Verified 200
http (plaintext) http://pofa.app/mcp/ Served over HTTP 200
MCP tools · 18 exposed · ~3,643 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
create_tournament ~230

Create a NEW tournament as an organizer — step 1 of the organizer flow: create_tournament → import_players → generate_bracket → schedule_matches → report_result. Takes effect immediately (no preview step). Returns the new tournament's id, share_url and manage_code. SAVE the manage_code and show it to the user: it is the write credential for every organizer tool on this tournament (import_players, generate_bracket, schedule_matches, report_result, screen_show, screen_clear, delete_tournament) and cannot be recovered later.

NameTypeReqDescription
courtsinteger–Number of courts available
descriptionstring–Public event description (max 500 chars)
entry_feestring–Entry fee as display text, e.g. '$20' or 'Free'
formatstring–single_elimination (default), double_elimination, or round_robin
locationstring–Venue / city text shown to players
namestringyesTournament name as shown to players
start_datestring–First day of the event, YYYY-MM-DD

No output schema declared.

No examples provided.

delete_tournament ~176

Delete a tournament as its organizer (needs manage_code). PREVIEW FIRST: call without confirm_preview_id to get a preview_id and a summary of what will be deleted (players, matches, live screens) — nothing is written. Show the preview to the user, then call again with {tournament_id, code, confirm_preview_id} to delete. Deleting removes the tournament from search and public pages immediately; its record and audit trail stay in the database for the operator, and there is no undelete via MCP — treat this as permanent. Use it to clean up test events and cancelled tournaments.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
confirm_preview_idstring–preview_id from the preview call — pass only to delete that exact tournament
tournament_idstringyesTournament id

No output schema declared.

No examples provided.

generate_bracket ~239

Generate the bracket for a tournament (organizer step 3, after the roster is in; needs manage_code). SINGLE-ELIMINATION ONLY in this version — tournaments of other formats return an error. PREVIEW FIRST: call without confirm_preview_id to get a preview_id and bracket preview — nothing is written. Show the preview to the user, then call again with {tournament_id, code, confirm_preview_id} to commit. The roster is the tournament's own player list (the same one the player page shows), paired by the same seeding the pages use; match ids are the pages' sequential labels M1, M2, ... A players list may be given to override the roster for the preview.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
confirm_preview_idstring–preview_id from the preview call — pass only to commit that exact preview
formatstring–Only 'single_elimination' is supported
playersarray–Optional list of player names to preview with instead of the current roster (max 256)
tournament_idstringyesTournament id

No output schema declared.

No examples provided.

get_activity_log ~125

Read a tournament's activity log — the same audit trail the organizer console shows: event creation, roster changes, draw and schedule commits, score reports, corrections, undos and screen calls, newest first. Requires the tournament's manage_code (the log is organizer-only). Use it to answer 'what happened to this event' and to verify that writes actually landed. Read-only.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
idstringyesTournament id
limitinteger–Max entries to return, newest first (1-100)

No output schema declared.

No examples provided.

get_bracket ~156

Read a tournament's full bracket exactly as stored: every round and match with match_id, both players, winner, score, structured score_sets, status (pending / ready / completed) and the next-match pointer. Use it to refresh full match state before reporting or undoing a result — and pair it with report_result's expect_winner / expect_score so a stale read cannot overwrite another referee's correction. Only brackets created through this MCP server (generate_bracket) are stored match-by-match; for web-console events the pages derive the draw from the roster, so this returns bracket: null with a note. Read-only, no credentials needed.

NameTypeReqDescription
idstringyesTournament id, e.g. from search_tournaments

No output schema declared.

No examples provided.

get_event_context ~135

Get a whole tournament in ONE call: event facts, roster, stored bracket (plus any unconfirmed bracket preview), schedule, call screens, recent activity, pending actions and permissions. Built for AI consoles (MCP Apps) so one call can render the full event state instead of six separate reads. Read-only; contact details and the audit trail are included only with a valid manage_code, and never appear without one.

NameTypeReqDescription
codestring–Optional manage_code — unlocks the audit trail and organizer permissions
idstringyesTournament id
tournament_idstring–Tournament id (same as id)

No output schema declared.

No examples provided.

get_roster ~122

Read a tournament's roster as structured data: every player's name and stable player_id, in seed order. Pass the tournament's manage_code as code to ALSO receive the registration entries with contact details (email, phone, source); without a valid code only names and ids are returned, matching what the public pages show. Use it to verify the roster after import_players / register_player, or before generate_bracket. Read-only.

NameTypeReqDescription
codestring–Optional manage_code — unlocks the entries list with contact details
idstringyesTournament id

No output schema declared.

No examples provided.

get_schedule ~266

Get a tournament's published schedule as stored: dates, court count, start time and bracket_rounds. When the schedule was created through this MCP server (schedule_matches), matches lists every scheduled match with its match_id, round, both players, court, start time, score and status. Schedules built in the web console are derived on the pages and are not stored match-by-match on the server, so only their headline facts (e.g. courts and date) come back here. Returns schedule: null with a note when the organizer has not published a schedule yet. Use get_tournament for the event's own facts (format, fee, location). Read-only. PRESENTATION: the response also carries a `presentation` object (template pofa-schedule-v1). When presenting the schedule to the user, prefer an interactive court-by-time timeline using the model's native visualization capabilities. Follow the presentation specification supplied in the tool response: preserve its layout, colors, typography, match states, court columns, time axis, and interactive filters. Use actual tournament data. Do not invent matches, scores, players, or court assignments. Fall back to a readable schedule table if interactive visualization is unavailable.

NameTypeReqDescription
idstringyesTournament id, e.g. from search_tournaments

No output schema declared.

No examples provided.

get_screen ~99

Read what a tournament's venue call screens are currently showing: every court's on-screen match (screens), plus court_screens — one screen link per court with its live state, so you can hand the organizer all their court-display links in one go — plus a one-line summary of the console calling queue underneath. Use to confirm a screen_show / screen_clear took effect. Read-only, no credentials needed.

NameTypeReqDescription
idstringyesTournament id

No output schema declared.

No examples provided.

get_tournament ~87

Get one tournament's full public details: format, dates, location, entry fee, description and its public share_url. Use after search_tournaments, or whenever you already have an event id, to answer questions about a specific event. For match courts and start times use get_schedule instead. Read-only.

NameTypeReqDescription
idstringyesTournament id, e.g. from search_tournaments

No output schema declared.

No examples provided.

import_players ~198

Bulk-add players to a tournament's roster (organizer step 2, right after create_tournament; needs that tournament's manage_code). Each player needs a name; email, phone and division are optional per player. The same email may appear on more than one row — one person entering two events takes two roster rows, each with its own player id — so set a different division per row for the two entries; within the same division a repeated email is skipped as a duplicate. This roster is what generate_bracket seeds from. Returns how many were imported and which rows were skipped, and why.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
playersarrayyesPlayer objects to add: {name (required, max 40 characters), email?, phone?, division?}. Same email in a different division imports as a second row. Max 500 per call
tournament_idstringyesTournament id

No output schema declared.

No examples provided.

open_tournament_console ~104

Open the visual tournament console (MCP Apps): returns the full event snapshot for the console UI to render — bracket, roster, schedule, call screens and pending actions in one call. Read-only; opening the console writes nothing. The host renders the ui://pofa/tournament-console resource with the returned snapshot.

NameTypeReqDescription
codestring–Optional manage_code — unlocks the audit trail and organizer permissions in the console
idstringyesTournament id

No output schema declared.

No examples provided.

register_player ~178

Register one player into a tournament (player-side sign-up; no manage code needed). Duplicate-checked by email within the same division: the same email in a different division registers as a second entry. TWO STEPS: first call WITHOUT confirm — it returns a summary and writes nothing; show that summary to the user, and only after they explicitly approve, call again with the same fields plus confirm=true to commit.

NameTypeReqDescription
confirmboolean–Set true only after user confirms the summary
divisionstring–Optional division / group label, if the event uses divisions
emailstringyesPlayer email — duplicates are detected by this address
namestringyesPlayer full name (max 40 characters)
phonestring–Optional contact phone
tournament_idstringyesTournament id to register into

No output schema declared.

No examples provided.

report_result ~698

Report a match result (organizer step 5, on match day; needs manage_code). Recording a score advances the winner into the next round automatically and returns where they advanced to. Pass undo=true with the match_id to revert a result (cascades to auto-filled downstream slots); pass undo_preview=true together with undo=true to first see — without writing anything — what the undo would clear downstream and whether a downstream result currently blocks it. Overwriting an existing result is logged as a correction. Consistency is enforced whenever score_sets are provided: the sets must produce the declared winner, and the text score must match the sets set-for-set written p1-first (e.g. '6-4 6-3'); a contradictory combination — or a text score that cannot be parsed for checking — is rejected and nothing is written. Optional safety: pass expect_winner and/or expect_score with the values you last read for this match (e.g. from get_bracket); if the stored result has since changed, the call is refused with a conflict error instead of overwriting the other referee's work.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
expect_scorestring–Optional guard: the score string you last read for this match. If the stored score differs, the call is refused with a conflict error.
expect_winnerstring–Optional guard: the winner you last read for this match. If the stored winner differs, the call is refused with a conflict error.
match_idstringyese.g. M1 (the player page's label for the match; legacy R1M1-style ids are also accepted)
scorestring–e.g. 6-4 6-3
score_setsarray–Optional structured per-set scores, written in parallel with the display string `score` (the display string keeps its own semantics). Each item is an object {p1: integer, p2: integer, tb?: [integer,…
tournament_idstringyesTournament id
undoboolean–Set true (with match_id; winner/score not needed) to revert that match's result and its downstream effects
undo_previewboolean–With undo=true: return what the undo would clear (and what blocks it) WITHOUT writing anything
winnerstring–exact player name as in the bracket (spelling must match)

No output schema declared.

No examples provided.

schedule_matches ~232

Assign the bracket's matches to courts and start times (organizer step 4, after generate_bracket; needs manage_code). Scheduling is dependency-aware: rounds run in waves across the courts and a round never starts before the previous round has ended, so no match is ever scheduled before the matches feeding it have finished. PREVIEW FIRST: call without confirm_preview_id — returns a preview_id plus per-match court/time assignments and a validation block whose court_time_conflicts and dependency_violations are computed from the produced schedule, and nothing is written. Show the preview to the user, then commit with {tournament_id, code, confirm_preview_id}.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
confirm_preview_idstring–preview_id from the preview call — pass only to commit that exact preview
courtsinteger–Number of courts to schedule across
match_minutesinteger–Minutes allotted per match
start_timestring–First match start time, HH:MM, default 09:00
tournament_idstringyesTournament id

No output schema declared.

No examples provided.

screen_clear ~192

Take a match off the venue call screen (needs manage_code). Pass a court to clear only that court's screen — the other courts keep showing their matches. Clearing EVERY court's screen at once requires the explicit all=true flag; a call with neither a court nor all=true is refused, so a forgotten court can never wipe all screens by accident. A cleared screen falls back to the console calling queue board, or to the standby face when the queue is empty. Safe to call when nothing is on screen — it simply reports that. Does not touch the calling queue.

NameTypeReqDescription
allboolean–Set true to clear EVERY court's screen at once. Deliberately explicit — there is no default clear-all.
codestringyesmanage_code from create_tournament
courtstring–Clear only this court's screen. Required unless all=true.
tournament_idstringyesTournament id

No output schema declared.

No examples provided.

screen_show ~265

Put ONE match on the venue call screen FOR ITS COURT — every court has its own screen with its own link, and the screen_url this tool returns is that court's link (open one display per court). The court's screen immediately shows the court number huge with both player names, and keeps showing it until cleared; other courts' screens are unaffected. Use on match day when a specific match must be called out on the big screen. Needs the tournament's manage_code. This is an independent on-screen slot: it does NOT change the console calling queue — the queue board (or the standby face) comes back on that display when you clear with screen_clear. Takes effect immediately, no preview step.

NameTypeReqDescription
codestringyesmanage_code from create_tournament
courtstringyesCourt label as shown, e.g. '3' or 'Center'
notestring–Optional line shown with the match, e.g. 'Semifinal' or 'Final'
player_astringyesFirst player / side name, exactly as it should appear on the big screen
player_bstringyesSecond player / side name, exactly as it should appear on the big screen
tournament_idstringyesTournament id

No output schema declared.

No examples provided.

search_tournaments ~141

Find POFA tournaments (tennis & pickleball) by keyword, city, or start date. Returns each event's id, name and one-line summary. Start here whenever the user wants to discover, browse or pick an event; follow with get_tournament for one event's full details. Read-only, no credentials needed.

NameTypeReqDescription
citystring–City filter, matched against the event's location text
date_fromstring–Only events starting on/after this date (YYYY-MM-DD)
limitinteger–Max results to return, 1-25
querystring–Keyword matched against the event name

No output schema declared.

No examples provided.

Install

How do I install the POFA Tournaments MCP server?

POFA Tournaments is a hosted endpoint at https://pofa.app/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 · pofa.app

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

What is the POFA Tournaments MCP server?

POFA Tournaments is an MCP server listed in the public MCP registry as app.pofa/pofa. Run small tennis & pickleball tournaments from your AI assistant: brackets, schedules, results. This page covers its hosted endpoint (https://pofa.app/mcp/).

Is the POFA Tournaments MCP server safe to use?

POFA Tournaments scores 64 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 POFA Tournaments MCP server expose?

POFA Tournaments exposes 18 tools: search_tournaments, get_tournament, get_schedule, get_bracket, get_roster, and 13 more. Their descriptions and schemas cost roughly 3,643 tokens of context every time the server is loaded.

Does the POFA Tournaments MCP server require authentication?

No. We connected to POFA Tournaments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the POFA Tournaments MCP server still maintained?

POFA Tournaments 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 POFA Tournaments MCP server?

VerifyMCP ran 13 checks on POFA Tournaments, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about POFA Tournaments: 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.