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.

The Tennis Desk

REMOTE · THETENNISDESK.COM

Ratings, line win chances and lineup help for USTA NorCal adult league tennis, from public results.

+4 this week 75 Trust /100

Last scanned (12 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 7654 tokens (~263/item across 29 items; 29 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 Management23
  • Stability observed for 7 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 30 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 (13)

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

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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1
    • Tool “query_club” rewrote its description, which is the text the model reads security
    • Tool “query_league_standings” rewrote its description, which is the text the model reads security
    • “query_club” reworded the description of “briefing” cosmetic
    • Tool “query_league_standings” changed its title: An unofficial league table → A league table cosmetic
  • 1 Nov 26 +1

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

  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.2.0 → 0.3.0 functional
  • 30 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 29 Oct 26 71

    First indexed and scored.

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 5 Nov 2026 · Probed https://thetennisdesk.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thetennisdesk.com CN=YR1,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 RSA 2048 SHA256-RSA 67e5989efe2b09daf233c5db2ca833fc8de
SANs: thetennisdesk.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of thetennisdesk.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thetennisdesk.com. 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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thetennisdesk.com/api/mcp Verified 200
http (plaintext) http://thetennisdesk.com/api/mcp HTTPS enforced 308 https://thetennisdesk.com/api/mcp
MCP tools · 29 exposed · ~7,545 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
availability_loop ~454

Finds the players who have not answered the next match on the USTA NorCal availability grid. Pass the team and the grid as your agent read it: each match column's header, and each player's row with one cell per column. It lists each player whose answer is blank or maybe, and writes one group message for the team with the deadline and the team grid link. Each line's win chance needs a Desk Pass after the member's free forecast each week. The Desk writes, and the captain sends every message from their own phone or email. Never send a text or an email yourself, and never read a teammate's phone or email. Call it when a captain asks who has not answered on NorCal, or wants reminder texts.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
columnsarray–Each match column's header on the grid, as NorCal prints it, in order, for example #8 Sunday 10/18/26.
deadlinestring–The answer deadline, as 2026-10-16 1:00 PM. Left out, 48 hours before the match starts.
formatstring–The match format, as the NorCal post-dates form names it: All 3 or All 5 for one shift, or a split such as 2/1.
lineupNowboolean–Set true to plan the lineup now, before the deadline, from the answers so far.
matchIdstring–NorCal's own id for the match, from the Line-up link. Optional: it fills in the lineup form's path.
rowsarray–One row for each player on the grid.
seasoninteger–Season year. Defaults to the current season.
signAsstring–The captain's first name, which signs the lineup email.
teamstring–The team the grid is for: the Desk's team id, which is NorCal's own team id, a link to its team page, or its name. Left out, the signed-in member's own team this season.

No output schema declared.

No examples provided.

compute_aggregate ~332

Works out one number for any covered team, in any league or season, in code from its recorded lines: `win_rate`, `win_count`, `loss_count` or `match_count`. Call it whenever you would state a count, an average or a win rate, and quote its value exactly rather than working one out. With no `phase` it counts the playoffs and sectionals too, so pass phase:'regular season' for a league record alone.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
includeAllSeasonsboolean–Set true ONLY when the user explicitly asks about prior years / all history.
kindstringyesWhich number to compute, over the lines the team played: 'win_rate' (the share of them won, from 0 to 1), 'win_count' (lines won), 'loss_count' (lines lost) or 'match_count' (lines played).
phasestring–Optional competition phase: 'sectionals', 'playoffs', 'postseason', or 'regular season'. Pass it when the member names one, or when they ask for a LEAGUE record — a sectional match keeps its REGULAR-…
seasoninteger–Optional season year to filter to, e.g. 2026
teamstringyesTeam key or display name. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

compute_match_line_ratings ~174

Ranks a team's recorded matches by how strong a lineup it fielded, from each player's current Desk level, so it is not a rating at the time of the match. Call it when someone asks which match had the strongest or weakest lineup, or how a team's line strength moved.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
includeAllSeasonsboolean–Set true ONLY when the user explicitly asks about prior years / all history.
seasoninteger–Optional season year to filter to, e.g. 2026
teamstringyesTeam key or display name to resolve, e.g. 'Belvedere mixed 8.0'. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

compute_roster_strength ~242

Splits a team's roster by published NTRP level and gives each level group's players, wins, losses and win rate this season, over every league line those players appeared in. Call it for a roster's shape rather than its results, as in 'how strong is their 4.0 half' or 'who carries this team'. It works even before a season has been played, because it then reads the season before.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
phasestring–Optional competition phase: 'sectionals', 'playoffs', 'postseason', or 'regular season'. Pass it when the member names one, or when they ask how a level group did in their LEAGUE — a sectional match…
seasoninteger–Optional season year, e.g. 2026
teamstringyesTeam key or display name. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

get_desk_pass ~108

Says whether the signed-in member holds the Desk Pass, when it renews or ends, how many forecasts they have left this week and when more come. Call it when someone asks about their Desk Pass or their forecasts. It takes no arguments. Needs a signed-in member, because it answers about them. A key with no member gets the error member_required.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.

No output schema declared.

No examples provided.

match_date_check ~402

Checks a proposed date and time for a home match before the captain posts it on the USTA NorCal league site. Pass the team, the match and the proposed date and start time, and the format and second-shift time if the captain has them. It says whether the form offers that time, which formats the form offers for the team's lines, and whether the team already plays that day. The Desk never acts on the USTA site, so the captain, or their own agent in their own session, presses Submit. Call it when a captain asks whether a date works, or before an agent fills the post-dates form.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
datestring–The date the schedule shows for the match now, as 2026-10-24, to find it. Optional with opponent.
formatstring–The match format, as the form names it: All 3, 2/1 or 1/2 for three lines, and All 5, 3/2, 2/3, 4/1 or 1/4 for five.
opponentstring–The other team in the match, as the schedule names it. With date, or alone.
proposedDatestringyesThe date the captain wants to post, as 2026-10-24.
proposedTimestringyesThe start time the captain wants, as 6:30 PM.
seasoninteger–Season year. Defaults to the current season.
secondShiftTimestring–The second shift's start time, for a two-shift format.
teamstringyesThe member's team: the Desk's team id, which is USTA NorCal's own team id, a link to its team page, or its name.

No output schema declared.

No examples provided.

plan_lineup ~377

Plans a doubles and singles lineup for a team the Desk covers. It lists who has played most for your team this season, with their appearances, usual line and Desk level, the Desk's estimate of how they play now. Against a covered opponent it adds each line's win chance, each team's Desk level there and the expected number of lines won. Call it for 'what lineup should we play against X', 'who has played most for us' or 'how do we beat X'. Pass `unavailable` for your players who are out, but pass `lineup` only for the players the person put on each line. Needs a Desk Pass after the member's free forecast each week. Past that, a call gets the free part, with no chance for anything still to be played, and `deskPass`, whose `message` you give the person. Its error is free_forecast_used, or desk_pass_required for a key with no member.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
lineuparray–Your own team's lineup, only as the person states it, line by line. Never fill it in yourself. Each line named is read from those players.
opponentstring–The opponent team to plan against, by name or Desk page link. Optional.
seasoninteger–Season year. Defaults to the current season.
teamstringyesYour team, e.g. 'Belvedere 18AM3.5A', or its Desk page link or number. Must be a covered team.
unavailablearray–Players on YOUR team who are out. They leave your list and the averages your side of each line is read from. Names may be abbreviated ('Jane').

No output schema declared.

No examples provided.

plan_lineup_from_availability ~367

Plans a lineup from the availability a member's agent read on the USTA NorCal league site, so the agent can fill in the lineup form. Pass the team, the match and each player's answer in USTA's own words: yes, No, maybe, call last, First shift only or Second shift only. The result also holds the values for the lineup form, and what to confirm with the member before Save. Each line's win chance needs a Desk Pass after the member's free forecast each week. The Desk never acts on the USTA site, so the member, or their own agent in their own session, presses Save. Call it when someone pastes or describes who can play a match and asks for a lineup.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
availabilityarrayyesEach player's answer, as the agent read it on NorCal's availability grid or as the member pasted it.
datestring–The match date, as 2026-10-24. With opponent, or alone. With neither, the plan is for the team's next match.
matchIdstring–USTA NorCal's own id for the match, read from the link on the team page. Optional: it fills in the form's path.
opponentstring–The other team in the match, as the schedule names it. With date, or alone.
seasoninteger–Season year. Defaults to the current season.
teamstringyesThe member's team: the Desk's team id, which is USTA NorCal's own team id, a link to its team page, or its name.

No output schema declared.

No examples provided.

predict_matchup ~269

Gives the home side's win probability for one line between named players. It weighs each player's Desk level, how a pair plays together and who is available, while a player the Desk has not yet rated gets a default level. Call it when someone asks who would win, the odds of a matchup, or how a pairing stacks up. Needs a Desk Pass after the member's free forecast each week. Past that, a call gets the free part, with no chance for anything still to be played, and `deskPass`, whose `message` you give the person. Its error is free_forecast_used, or desk_pass_required for a key with no member.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
away_playersarrayyesAway-side player name(s), ideally as they appear on recorded lines. Each may also be a player's Desk page link or number.
home_playersarrayyesHome-side player name(s), ideally as they appear on recorded lines, e.g. 'Last, First'. Each may also be a player's Desk page link or number.
line_typestring–Optional; inferred from side sizes when omitted. One of 'singles' or 'doubles'.

No output schema declared.

No examples provided.

prepare_score_entry ~392

Prepares the values for the score form on the USTA NorCal league site, from the scores a member reports. Pass the team, the match and each line: its players on both sides, its set scores, and its status when a line was not completed. Give the sets from the member's own side, unless scoresFrom says otherwise. Pass posted too, with each line as NorCal shows it, so it can list every line where the two differ. The Desk never acts on the USTA site, so the member, or their own agent in their own session, presses Submit. Call it when someone wants to enter or check a match score on NorCal.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
datestring–The date the match was played, as 2026-10-11. The form takes the date played, even when the schedule shows another.
linesarrayyesEach line as the member reports it.
matchIdstring–USTA NorCal's own id for the match, read from the link on the team page. Optional: it fills in the form's path.
opponentstring–The other team in the match, as the schedule names it. With date, or alone.
postedarray–Each line as NorCal shows it after the other team entered the score, to compare with the member's record.
seasoninteger–Season year. Defaults to the current season.
teamstringyesThe member's team: the Desk's team id, which is USTA NorCal's own team id, a link to its team page, or its name.
weAreHomeboolean–Whether the member's team was the home team. Read from the schedule when left out.

No output schema declared.

No examples provided.

project_standings ~287

Projects how a league table could finish, from the matches left and the Desk's line forecasts. It gives each team's likely place, its chance to finish first and, when the Desk knows the playoff cut, its chance to make the playoffs. It also says what the named team needs, while a Desk Pass adds the team's live playoff report. Call it for a team's playoff chances or what it needs. Pass the team, or `league` and `area` for a whole league, or neither for the member's own team. Needs a Desk Pass. Without one, a call gets the free part, with no chance in it, and `deskPass`, whose `message` you give the person.

NameTypeReqDescription
areastring–The area of that league, e.g. 'Marin'. Used only with `league`.
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
leaguestring–A league to project when no team is named, with its words, e.g. "55 & over men's 8.0". Used only without `team`.
teamstring–The team whose league to project, e.g. 'Belvedere men's 7.5'. Omit for the signed-in member's own team. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_club ~476

Returns what a club's page on The Tennis Desk shows, in one call. That is its teams in a season by league, each with its place in the Desk's league table and its record. It also gives the club's next matches, latest results and record against each other club. Call it when someone asks how a club is doing, its record against other clubs, or where its teams stand. For only its list of teams, or which plays next, query_club_teams is enough. Pass `club`: the club's name as people say it or as USTA prints it, or its page address or number. Pass `season`, a year, for that season's page, and `briefing` true for the club's week. A team's `firstPlace` says whether it can still finish first, which assumes each scheduled match is played. In a result, * marks a line won or lost by default.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
briefingboolean–True for the club's week instead of its page: every team match in the next 7 days, counting the day of the call in Pacific time, each with the other team's place in the Desk's league table and their…
clubstringyesThe club: its name as people say it or as USTA prints it, e.g. 'Scott Valley', or its club page address or number, e.g. '/c/218'.
seasoninteger–A season year, 2022 or later: the club's page in that season, its teams, places and records then. Leave it out for the newest season the club fielded a team. A season the club has no team in is not f…

No output schema declared.

No examples provided.

query_club_teams ~202

Returns the teams a named club fields this year, and which of them plays next. Call it whenever someone asks about a whole club by name, before you narrow the question to a single team. For how the club is doing, call query_club, which reads the club's page. Pass any league words the person used in `qualifier`, such as 'combo', 'mixed', 'womens', '40 & over' or '3.5', because dropping them answers a different question.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
clubstringyesThe club name, e.g. 'Belvedere'.
qualifierstring–Any league words the asker used alongside the club — 'combo', 'mixed', 'womens', '40 and over', '3.5'. Omit only when they named the club alone.

No output schema declared.

No examples provided.

query_cohort_standing ~311

Ranks a group of players by Desk level and gives the member's place in it. Call it for 'where do I stand', 'how do I compare to the top players', a ranking or a percentile, or the top players in an age group or level. Define the group with `ageBand`, `division` and `level`, or leave them out so it fills the group from the member's team. Needs a signed-in member, because it answers about them. A key with no member gets the error member_required.

NameTypeReqDescription
ageBandstring–Age group: '18', '40', '55', '65', or '70' (the '& Over' band).
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
divisionstring–'men', 'women', or 'mixed' — the gender ladder. Omit to use the member's own.
includeAllSeasonsboolean–Set true ONLY to pool cohort membership across all years.
levelstring–NTRP level as a string, e.g. '4.0' or '8.0' (mixed). Omit for a whole age-group ladder.
seasoninteger–Optional league year for cohort membership, e.g. 2026. Defaults to the current season.
topNinteger–How many top players to show (default 10).

No output schema declared.

No examples provided.

query_coverage ~112

Answers what the Desk covers: which areas, leagues, levels, clubs, teams and seasons are on record, and what kinds of question it can answer at all. Call it whenever someone asks what you can look up, what data you have, or which leagues, levels or areas are covered. It takes no arguments, because it reports the whole census rather than a slice of it.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.

No output schema declared.

No examples provided.

query_forecast_results ~188

Gives a team's latest matches that the Desk forecast before they were played. For each line, it gives the team's chance as the Desk logged it the night before, and whether the team won the line. It also gives each match's result. Call it for how the Desk's forecasts did for a team, or what the Desk gave a team in a past match. Pass the team, or nothing for the member's own team. It gives only matches already played, never a chance for a match still to come, which comes with the Desk Pass.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
teamstring–The team, e.g. 'Belvedere men's 7.5'. Omit for the signed-in member's own team. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_league_standings ~354

Builds the Desk's league table for a team's flight, with the named team's place, which it ranks from recorded results by the league's own rule and tie-breaks. Call it for the standings, how a team finished, who won the league or 'the table'. Pass the team name, or nothing for the member's own team. For a whole league, pass `league` and `area` instead, such as "55 & over men's 8.0" and 'Marin'. Never pass a club or an area as the team.

NameTypeReqDescription
areastring–The area of that league, as the Desk names it, e.g. 'Marin' or 'San Francisco'. Used only with `league`.
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
leaguestring–A league to build the table of when no team is named, with every league word the question gives, the age group included: its name, e.g. 'Adult 55 & Over Mens 8.0', or its words, e.g. "55 & over men's…
seasoninteger–League year, e.g. 2025. Defaults to the current season.
teamstring–Team or club name whose league table to build, e.g. 'Belvedere' or 'Belvedere mixed 8.0'. Omit to use the signed-in member's own team, or to ask by `league`. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_match_log ~166

Returns a player's match-by-match rating history for one season: each match they played, their level before and after it, and the other players on court with their levels then. Call it when someone asks how a player's level changed, how they reached it, what one result did to it, or asks to see their matches. Prefer it to query_player_history when the question is about the level rather than the results, because it follows the level match by match.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
playerstringyesPlayer name as the member wrote it. Or the player's Desk page link or number.
seasoninteger–Season year. Omit for the current season.

No output schema declared.

No examples provided.

query_matchup ~194

Returns the recorded lines from the scorecards where two named teams played each other, in any season, each with an evidenceId. Call it for the head-to-head between two teams, or before you state a fact about it.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
includeAllSeasonsboolean–Set true ONLY when the user explicitly asks about prior years / all history.
limitinteger–Max rows to return (default 9, max 60).
seasoninteger–Optional season year to filter to, e.g. 2026
team_astringyesFirst team name or partial name to resolve. Or the team's Desk page link or number.
team_bstringyesSecond team name or partial name to resolve. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_my_teams ~173

Returns the member's own teams, the ones they are on or have played for, which come from their affiliations. Call it when the person asks about their own teams, as in 'what teams am I on', and set thisYear:true for this year's. A question that names a team, a club or a player is about that one, so use the other tools for it, signed in or not. Needs a signed-in member, because it answers about them. A key with no member gets the error member_required.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
thisYearboolean–Set true for 'this year / this season' — the current league year's teams only. Omit for all covered teams.

No output schema declared.

No examples provided.

query_player_history ~190

Returns the recorded lines a named player appeared in, as cited rows told from the player's side, with the player's record, which is already counted by season, team and stage. Call it when someone asks about a player's results, form or history. Never guess at their injury or availability, because the Desk does not hold it.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
includeAllSeasonsboolean–Set true ONLY when the user explicitly asks about prior years / all history.
limitinteger–Max rows to return (default 9, max 60).
playerstringyesPlayer name to resolve, e.g. 'First Last'. Or the player's Desk page link or number.
seasoninteger–Optional season year to filter to, e.g. 2026

No output schema declared.

No examples provided.

query_player_rating ~149

Returns the Desk's read of a named player: their Desk level, their record by season, team, stage and format, the model card id and the lines behind it. Call it when someone asks how strong a player is, or about their rating, level, trend or bump risk. The USTA band is not here, because it is the `rating` on a query_roster row. The Desk publishes no bump prediction.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
playerstringyesPlayer name to resolve, e.g. 'First Last'. Or the player's Desk page link or number.

No output schema declared.

No examples provided.

query_playoff_history ~175

Gives a team's playoff chances from a week ago and earlier, one a week, each as of its day. It also says what moved the chance most: the change between two days and the matches played between them. Call it for how a team's playoff chances have changed, or what its chances were last week. Pass the team, or nothing for the member's own team. It never gives today's chance: the `project_standings` tool gives that, with the Desk Pass.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
teamstring–The team, e.g. 'Belvedere men's 7.5'. Omit for the signed-in member's own team. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_roster ~230

Returns a team's roster for a season, one row per player with an evidenceId: name, NTRP rating, wins, losses, matches and Desk level. Call it when someone asks who is on a team, or before you state a fact about a roster. Pass `season` when the person named a year, because without it the answer covers the current season. If `moreRows` is true, call again with a larger `limit`, up to 60.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
includeAllSeasonsboolean–Set true ONLY when the user explicitly asks about prior years / all history.
limitinteger–Max roster rows to return (default 30 = the full roster, max 60). Omit to get the whole team.
seasoninteger–Optional season year to filter to, e.g. 2026
teamstringyesTeam name or partial name to resolve. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_team_forecast ~223

Returns a team's upcoming matches on the league schedule, or those of every team a player is on: the opponent, the day, the start time, and home or away. Call it for a next match, today's or tomorrow's match, or the schedule. Pass `team` for a named team, or `player` for a first-person ask like 'who am I playing'. It gives no team win chance. A team match's chance is only in the live playoff report from project_standings, which comes with the Desk Pass.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
playerstring–Player whose teams' upcoming matches to fetch, e.g. 'First Last'. Or the player's Desk page link or number.
teamstring–Team name to resolve, e.g. 'Belvedere mixed 8.0' or 'BELVEDERE TC 40MX8.0A'. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

query_team_record ~334

Returns the recorded lines of any team the Desk covers, in any league and season, each with an evidenceId you can cite. It also gives the team's record, which is already counted, every team match of the period and its next matches. Call it when someone asks about a named team's matches, results or next match, or before you state a fact about them.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
datestring–Optional match day, as YYYY-MM-DD, e.g. '2026-02-05'. The rows are then that day's lines, from any season unless `season` is given. Pass it when the question names the day of a match.
includeAllSeasonsboolean–Set true ONLY when the user explicitly asks about prior years / all history.
limitinteger–Max rows to return (default 9, max 60).
phasestring–Optional competition phase: 'sectionals', 'playoffs', 'postseason', or 'regular season'. Pass it when the member names one — a sectional match keeps its REGULAR-SEASON league name in our data, so the…
seasoninteger–Optional season year to filter to, e.g. 2026
teamstringyesTeam name or partial name to resolve, e.g. 'Tiburon' or 'Mill Valley men's 18'. Or the team's Desk page link or number.

No output schema declared.

No examples provided.

read_docs ~259

Reads The Tennis Desk's own docs, word for word. They cover what the Desk is, a Desk level, what is free and what the Desk Pass adds, coverage and updates, agents, privacy and how a league table is ordered. Call it when someone asks about the Desk itself rather than a team, a player or a match. Pass `about`, a few words on what to find, and `pages` for a page you know. It needs no Desk Pass, and a call does not count toward the account's daily or monthly limit.

NameTypeReqDescription
aboutstring–A few words on what to find, for example 'how it compares with NTRP'. With no `pages`, the sections of any page that match it.
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
pagesarray–One or two docs pages, each named by its address after /docs/, as https://thetennisdesk.com/docs.md lists them, for example 'desk-level'. The front page is 'index'. A page read_docs does not hold is…

No output schema declared.

No examples provided.

read_research ~218

Reads the Desk's published research about players in general, word for word. Each piece comes with its question, headline, answers and figures, the group of past players it counts and the day it was measured. Call it when someone asks about players or teams in general, such as how often players move up or back down, or home advantage. Never call it for one named player, team or match, because every figure is a rate over a group. Pass `about`, a few words on the question, or `pieces` for a piece you know. It needs no Desk Pass.

NameTypeReqDescription
aboutstring–A few words on the question, for example 'how players do after a bump, and how many move back down'.
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
piecesarray–One or two pieces, each named by its address after /research/, as https://thetennisdesk.com/research lists them. Optional.

No output schema declared.

No examples provided.

scout_team ~187

Writes the Desk's scout of one team it covers: its ranked reads of who matters and how the lines go, each with its evidence. Call it when someone asks for a scout, a breakdown of a team, or how to beat a named team. Pass `team`, a team the Desk covers, by name or Desk page link. Never call it for a whole club, because a scout is of one team. Needs a Desk Pass. Without one, a call gets the free part, with no chance in it, and `deskPass`, whose `message` you give the person.

NameTypeReqDescription
askedstring–The person's question word for word, never paraphrased. Leave it out rather than invent one.
teamstringyesThe team to scout, e.g. 'Belvedere 18AM3.5A', or its Desk page link or number.

No output schema declared.

No examples provided.

Install

How do I install the The Tennis Desk MCP server?

The Tennis Desk is a hosted endpoint at https://thetennisdesk.com/api/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 · thetennisdesk.com

# add to Claude Code
claude mcp add --transport http chungty-thetennisdesk 'https://thetennisdesk.com/api/mcp'
Common questions

What is the The Tennis Desk MCP server?

The Tennis Desk is an MCP server listed in the public MCP registry as io.github.chungty/thetennisdesk. Ratings, line win chances and lineup help for USTA NorCal adult league tennis, from public results. This page covers its hosted endpoint (https://thetennisdesk.com/api/mcp).

Is the The Tennis Desk MCP server safe to use?

The Tennis Desk scores 75 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 The Tennis Desk MCP server expose?

The Tennis Desk exposes 29 tools: plan_lineup, query_team_record, query_matchup, query_roster, query_player_history, and 24 more. Their descriptions and schemas cost roughly 7,545 tokens of context every time the server is loaded.

Does the The Tennis Desk MCP server require authentication?

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

Is the The Tennis Desk MCP server still maintained?

The Tennis Desk is still listed as active in the MCP registry. We last reached this channel on 5 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 The Tennis Desk MCP server?

VerifyMCP ran 13 checks on The Tennis Desk, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.