Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.

Is pofa-mcp free to use?

Yes — the hub reached it with no key and no payment.

Is pofa-mcp safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 3h ago

pofa-mcp

https://pofa.app

Registry code: 221c1ff62181f57d

api record

POFA runs small tennis & pickleball tournaments. Player side (no credentials): search_tournaments to discover events, get_tournament for one event's details, get_schedule for match courts/times, register_player to sign a player up — two-step: summary first, commit with confirm=true only after the user approves. Organizer side: create_tournament starts a new event and returns a manage_code, the per-tournament write credential required by import_players, generate_bracket, schedule_matches and report_result — run them in that order and keep the code. generate_bracket and schedule_matches are…

endpoint: https://pofa.app/mcp/
protocol: streamable-http ·2024-11-05
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is pofa-mcp live?: Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is pofa-mcp free to use?: Yes — the hub reached it with no key and no payment.
What tools does pofa-mcp have?: 12 tools: report_result, register_player, create_tournament, import_players, generate_bracket, schedule_matches, screen_clear, search_tournaments, ….
Is pofa-mcp safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

684ms

last good check

priced tools

of 12 tools

_ answered our checks, 90 days 3 checks · signed record

2026-11-08 14:18 unknown → live

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 12 tools

5 open 7 never probed 5 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

search_tournaments open 3h ago

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.

mcp-tool

{
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City filter, matched against the event's location text"
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "description": "Max results to return, 1-25"
    },
    "query": {
      "type": "string",
      "description": "Keyword matched against the event name"
    },
    "date_from": {
      "type": "string",
      "description": "Only events starting on/after this date (YYYY-MM-DD)"
    }
  }
}

arguments 22 lines

get_tournament open 3h ago
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.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Tournament id, e.g. from search_tournaments" } } }
arguments 12 lines
get_schedule open 3h ago
Get a tournament's published schedule: match court/time assignments, dates and courts, plus the bracket size. Returns schedule: null with a note when the organizer has not published a schedule yet. Use for when/where questions about matches; use get_tournament for the event's own facts (format, fee, location). Read-only.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Tournament id, e.g. from search_tournaments" } } }
arguments 12 lines

screen_show open 30h ago

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.

mcp-tool

{
  "type": "object",
  "required": [
    "tournament_id",
    "code",
    "player_a",
    "player_b",
    "court"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "manage_code from create_tournament"
    },
    "note": {
      "type": "string",
      "description": "Optional line shown with the match, e.g. 'Semifinal' or 'Final'"
    },
    "court": {
      "type": "string",
      "description": "Court label as shown, e.g. '3' or 'Center'"
    },
    "player_a": {
      "type": "string",
      "description": "First player / side name, exactly as it should appear on the big screen"
    },
    "player_b": {
      "type": "string",
      "description": "Second player / side name, exactly as it should appear on the big screen"
    },
    "tournament_id": {
      "type": "string",
      "description": "Tournament id"
    }
  }
}

arguments 36 lines

get_screen open 30h ago
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.

mcp-tool
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Tournament id" } } }
arguments 12 lines

report_result unknown never probed

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). Overwriting an existing result is logged as a correction.

mcp-tool

{
  "type": "object",
  "required": [
    "tournament_id",
    "code",
    "match_id"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "manage_code from create_tournament"
    },
    "undo": {
      "type": "boolean",
      "description": "Set true (with match_id; winner/score not needed) to revert that match's result and its downstream effects"
    },
    "score": {
      "type": "string",
      "description": "e.g. 6-4 6-3"
    },
    "winner": {
      "type": "string",
      "description": "exact player name as in the bracket (spelling must match)"
    },
    "match_id": {
      "type": "string",
      "description": "e.g. M1 (the player page's label for the match; legacy R1M1-style ids are also accepted)"
    },
    "score_sets": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "p1",
          "p2"
        ],
        "properties": {
          "p1": {
            "type": "integer",
            "description": "points/games won by the player in slot p1 in this set"
          },
          "p2": {
            "type": "integer",
            "description": "points/games won by the player in slot p2 in this set"
          },
          "tb": {
            "type": "array",
            "items": {
              "type": "integer"
            },
            "maxItems": 2,
            "minItems": 2,
            "description": "optional tie-break score [p1, p2], exactly two integers"
          }
        }
      },
      "description": "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, integer]}, e.g. [{\"p1\": 6, \"p2\": 4}, {\"p1\": 7, \"p2\": 6, \"tb\": [7, 5]}], where tb is the optional tie-break points [p1, p2]. Stored in the match object and used to report results back to DUPR (required for rated events; the referee scoring UI blocks confirmation without it). Omitting it on an overwrite PRESERVES the existing score_sets (unlike `score`); pass an empty array [] to explicitly clear it, or a full array to replace it."
    },
    "tournament_id": {
      "type": "string",
      "description": "Tournament id"
    }
  }
}

arguments 64 lines

register_player unknown never probed

Register one player into a tournament (player-side sign-up; no manage code needed). Duplicate-checked by email. 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.

mcp-tool

{
  "type": "object",
  "required": [
    "tournament_id",
    "name",
    "email"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Player full name"
    },
    "email": {
      "type": "string",
      "description": "Player email — duplicates are detected by this address"
    },
    "phone": {
      "type": "string",
      "description": "Optional contact phone"
    },
    "confirm": {
      "type": "boolean",
      "description": "Set true only after user confirms the summary"
    },
    "division": {
      "type": "string",
      "description": "Optional division / group label, if the event uses divisions"
    },
    "tournament_id": {
      "type": "string",
      "description": "Tournament id to register into"
    }
  }
}

arguments 34 lines

create_tournament unknown never probed

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) and cannot be recovered later.

mcp-tool

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Tournament name as shown to players"
    },
    "courts": {
      "type": "integer",
      "description": "Number of courts available"
    },
    "format": {
      "type": "string",
      "default": "single_elimination",
      "description": "single_elimination (default), double_elimination, or round_robin"
    },
    "location": {
      "type": "string",
      "description": "Venue / city text shown to players"
    },
    "entry_fee": {
      "type": "string",
      "description": "Entry fee as display text, e.g. '$20' or 'Free'"
    },
    "start_date": {
      "type": "string",
      "description": "First day of the event, YYYY-MM-DD"
    },
    "description": {
      "type": "string",
      "description": "Public event description (max 500 chars)"
    }
  }
}

arguments 37 lines

import_players unknown never probed

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 and phone are optional per player, but entries whose email duplicates an existing roster email are skipped. This roster is what generate_bracket seeds from. Returns how many were imported and which rows were skipped, and why.

mcp-tool

{
  "type": "object",
  "required": [
    "tournament_id",
    "code",
    "players"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "manage_code from create_tournament"
    },
    "players": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "phone": {
            "type": "string"
          }
        }
      },
      "description": "Player objects to add: {name (required), email?, phone?}. Max 500 per call"
    },
    "tournament_id": {
      "type": "string",
      "description": "Tournament id"
    }
  }
}

arguments 36 lines

generate_bracket unknown never probed

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.

mcp-tool

{
  "type": "object",
  "required": [
    "tournament_id",
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "manage_code from create_tournament"
    },
    "format": {
      "type": "string",
      "default": "single_elimination",
      "description": "Only 'single_elimination' is supported"
    },
    "players": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional list of player names to preview with instead of the current roster"
    },
    "tournament_id": {
      "type": "string",
      "description": "Tournament id"
    },
    "confirm_preview_id": {
      "type": "string",
      "description": "preview_id from the preview call — pass only to commit that exact preview"
    }
  }
}

arguments 33 lines

schedule_matches unknown never probed

Assign the bracket's matches to courts and start times (organizer step 4, after generate_bracket; needs manage_code). PREVIEW FIRST: call without confirm_preview_id — returns a preview_id plus per-match court/time assignments and conflict validation, and nothing is written. Show the preview to the user, then commit with {tournament_id, code, confirm_preview_id}.

mcp-tool

{
  "type": "object",
  "required": [
    "tournament_id",
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "manage_code from create_tournament"
    },
    "courts": {
      "type": "integer",
      "description": "Number of courts to schedule across"
    },
    "start_time": {
      "type": "string",
      "description": "First match start time, HH:MM, default 09:00"
    },
    "match_minutes": {
      "type": "integer",
      "default": 30,
      "description": "Minutes allotted per match"
    },
    "tournament_id": {
      "type": "string",
      "description": "Tournament id"
    },
    "confirm_preview_id": {
      "type": "string",
      "description": "preview_id from the preview call — pass only to commit that exact preview"
    }
  }
}

arguments 34 lines

screen_clear unknown never probed
Take a match off the venue call screen (needs manage_code). With a court, only that court's screen is cleared and the other courts keep showing their matches; without a court, EVERY court's screen is cleared at once. 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.

mcp-tool
{ "type": "object", "required": [ "tournament_id", "code" ], "properties": { "code": { "type": "string", "description": "manage_code from create_tournament" }, "court": { "type": "string", "description": "Optional: clear only this court's screen. Omit to clear every screen at once." }, "tournament_id": { "type": "string", "description": "Tournament id" } } }
arguments 21 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 221c1ff62181f57d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/221c1ff62181f57d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/221c1ff62181f57d/badge.svg)](https://brick.blue/agent/221c1ff62181f57d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.