Skip to content

POFA Tournaments MCP server

app.pofa/pofapofa.appstreamable-httpv1.4.4Scanned

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

16 tools: 1 can delete or cancel things, 1 do something that can't be undone, 9 change things and 5 only read.

Tools: 1 delete, 1 irreversible, 9 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the POFA Tournaments MCP server can do

The POFA Tournaments MCP server is published by pofa.app, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (1 tool: delete_tournament), do things that cannot be undone, such as sending, paying or publishing (create_tournament) and create or change data (9 tools: get_roster, register_player, import_players, generate_bracket and 5 more). 5 tools only read.

1 tool reads private data (get_activity_log); 2 tools bring in text other people can write (get_tournament and screen_show); 1 tool can send data out of your system (register_player). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.4.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Deletes or cancels 1Claude Code: deny
  • delete_tournamentDelete a tournament as its organizer (needs manage_code).No findings

    Why it is in this group

    • The name "delete_tournament" says "delete": a word for removing or ending something.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
Can't be undone 1Claude Code: ask
  • create_tournamentCreate a NEW tournament as an organizer — step 1 of the organizer flow: create_tournament → import_players → generate_bracket → schedule_matches → report_result.1 finding

    Why it is in this group

    • The name "create_tournament" says "create": a word for a change.
    • The description says "cannot be recovered".

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...nd show it to the user: it is the write credential for every organizer tool on this tourna..."

      What this check looks for
    Description, as the server wrote it
    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.
Changes things 9Claude Code: ask
  • generate_bracketGenerate the bracket for a tournament (organizer step 3, after the roster is in; needs manage_code).No findings

    Why it is in this group

    • The name "generate_bracket" says "generate": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • get_activity_logRead 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 an…Reads private dataNo findings

    Why it is in this group

    • The name "get_activity_log" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • private-dataThe description's first sentence says "read" and "commit": it reads repositories.
    Description, as the server wrote it
    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.
  • get_rosterRead a tournament's roster as structured data: every player's name and stable player_id, in seed order.No findings

    Why it is in this group

    • The name "get_roster" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • import_playersBulk-add players to a tournament's roster (organizer step 2, right after create_tournament; needs that tournament's manage_code).No findings

    Why it is in this group

    • The name "import_players" says "import": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • register_playerRegister one player into a tournament (player-side sign-up; no manage code needed).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.
  • report_resultReport a match result (organizer step 5, on match day; needs manage_code).No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • schedule_matchesAssign the bracket's matches to courts and start times (organizer step 4, after generate_bracket; needs manage_code).No findings

    Why it is in this group

    • The name "schedule_matches" says "schedule": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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}.
  • screen_clearTake a match off the venue call screen (needs manage_code).No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • screen_showPut 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…Reads text others writeNo findings

    Why it is in this group

    • The name "screen_show" says "show": a word for reading.
    • The description's first verb is "put": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe description's first sentence says "put" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.
Only reads 5Show 5 read-only tools
  • get_bracketRead 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) an…1 finding

    Why it is in this group

    • The name "get_bracket" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...racket: null with a note. Read-only, no credentials needed."

      What this check looks for
    Description, as the server wrote it
    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.
  • get_scheduleGet a tournament's published schedule as stored: dates, court count, start time and bracket_rounds.No findings

    Why it is in this group

    • The name "get_schedule" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_screenRead 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 y…1 finding

    Why it is in this group

    • The name "get_screen" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...screen_clear took effect. Read-only, no credentials needed."

      What this check looks for
    Description, as the server wrote it
    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.
  • get_tournamentGet one tournament's full public details: format, dates, location, entry fee, description and its public share_url.Reads text others writeNo findings

    Why it is in this group

    • The name "get_tournament" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.
  • search_tournamentsFind POFA tournaments (tennis & pickleball) by keyword, city, or start date.1 finding

    Why it is in this group

    • The name "search_tournaments" says "search": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...one event's full details. Read-only, no credentials needed."

      What this check looks for
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__pofa__register_player"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (1 destructive, 1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pofa.app/mcp/: tools/list returned 18 tools to an anonymous client, including delete_tournament (destructive), create_tournament (irreversible), get_roster (write), register_player (write), import_players (write) and 8 more

    What this check looks for

Posture changes

  1. Nov 16, 2026
    • Tools that change things, listed without credentials: 8 to 13

Findings

Matches of fixed checks, with the text they matched.

4 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 13.View diff
    • Tools that change things, listed without credentials: 8 to 13
  2. Tools1 added, 3 changed.+1 added~3 changedView diff
  3. Tools2 changed.~2 changedView diff
  4. Tools3 added, 12 changed.+3 added~12 changedView diff
  5. Tools3 added.+3 addedView diff

Install

Pinned to version 1.4.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http pofa https://pofa.app/mcp/
claude mcp add --transport http pofa https://pofa.app/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pofa__search_tournaments",
      "mcp__pofa__get_tournament",
      "mcp__pofa__get_schedule",
      "mcp__pofa__get_bracket",
      "mcp__pofa__get_screen"
    ],
    "ask": [
      "mcp__pofa__get_roster",
      "mcp__pofa__register_player",
      "mcp__pofa__create_tournament",
      "mcp__pofa__import_players",
      "mcp__pofa__generate_bracket",
      "mcp__pofa__schedule_matches",
      "mcp__pofa__report_result",
      "mcp__pofa__screen_show",
      "mcp__pofa__screen_clear",
      "mcp__pofa__get_activity_log"
    ],
    "deny": [
      "mcp__pofa__delete_tournament"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pofa. Review it before you use it.

Capability tags behind 4 rules
  • mcp__pofa__get_tournament untrusted-input
  • mcp__pofa__register_player outbound
  • mcp__pofa__screen_show untrusted-input
  • mcp__pofa__get_activity_log private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.pofa/pofa/verify?hash=dce8e3565a2db421141f221ee4a2c6d54b8e0a3ed027d362b33fa4342dec910a" | jq -e '.changed == false'

Pinned hash dce8e3565a2d, from Nov 12, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.pofa/pofa/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.pofa/pofa
[![Anlyon Radar](https://radar.anlyon.com/badge/app.pofa/pofa.svg)](https://radar.anlyon.com/servers/app.pofa/pofa)

Source: MCP Registry. Synced Nov 12, 2026, 09:17 UTC.

POFA Tournaments MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the POFA Tournaments MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 11 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the POFA Tournaments MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_tournament.

Can the POFA Tournaments MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: create_tournament.

What tools does the POFA Tournaments MCP server have?

16 tools: 1 destructive, 1 irreversible, 9 write, 5 read. delete_tournament, create_tournament, get_roster, register_player, import_players, generate_bracket, schedule_matches, report_result and 8 more.

Does the POFA Tournaments MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the POFA Tournaments MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): register_player.

Has the POFA Tournaments MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.