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.

Ladderboard — round-robin ladders and match scores for small clubs

REMOTE · LADDER.ROWB.APP · SCANNED OCT 2

Round-robin ladders and match scores for small clubs. Players join by QR poster; no app, no account.

Available components

56 Trust /100
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 Security46
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 297 tokens (~59/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Ladderboard — round-robin ladders and match scores for… MCP server?

Ladderboard — round-robin ladders and match scores for… is a hosted endpoint at https://ladder.rowb.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 · ladder.rowb.app

# add to Claude Code
claude mcp add --transport http app-rowb-ladder-board 'https://ladder.rowb.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-rowb-ladder-board": {
      "url": "https://ladder.rowb.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-rowb-ladder-board": {
      "type": "http",
      "url": "https://ladder.rowb.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-rowb-ladder-board]
url = "https://ladder.rowb.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-rowb-ladder-board": {
      "type": "remote",
      "url": "https://ladder.rowb.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-rowb-ladder-board --url 'https://ladder.rowb.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-rowb-ladder-board:
    url: "https://ladder.rowb.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-rowb-ladder-board": {
      "Transport": "http",
      "Url": "https://ladder.rowb.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add app-rowb-ladder-board -t streamable-http -u 'https://ladder.rowb.app/mcp'
// mcp.json
{
  "mcpServers": {
    "app-rowb-ladder-board": {
      "type": "http",
      "url": "https://ladder.rowb.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 1 Oct 26 +1

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

  • 29 Sept 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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Sept 26 53

    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 2 Oct 2026 · Probed https://ladder.rowb.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rowb.app CN=WE1,O=Google Trust Services,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA256 eae3cda7ce3499250e8ac1cfe00ee57b
SANs: rowb.app, ladder.rowb.app, *.ladder.rowb.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ladder.rowb.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
rowb.app. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ladder.rowb.app/mcp Verified 200
http (plaintext) http://ladder.rowb.app/mcp Inconclusive 405
MCP tools · 5 exposed · ~297 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
add_player ~44

Register one player by name. Returns a 6-character code and a personal URL so the player can be identified at the courts without an account.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

create_ladder ~48

Create or update the club ladder: club name and sport. Returns the join URL (the poster target) that players scan.

NameTypeReqDescription
clubstringyes–
sportstring––

No output schema declared.

No examples provided.

get_standings ~53

The current table (rank, wins, losses, set percentage) plus the single most useful match to play next. Standings are computed with a fixed rule order, so the same results always give the same table.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

record_match ~99

Record a finished match result. Identify players by name, numeric id, or 6-character code. Give the set score (sets_a, sets_b) and optionally the games.

NameTypeReqDescription
games_ainteger––
games_binteger––
player_astringyes–
player_bstringyes–
roundinteger––
sets_aintegeryes–
sets_bintegeryes–

No output schema declared.

No examples provided.

schedule_match ~53

Put a match on the calendar before it is played. It appears as a pending card in the standings output.

NameTypeReqDescription
player_astringyes–
player_bstringyes–
roundinteger––

No output schema declared.

No examples provided.

Common questions

What is the Ladderboard — round-robin ladders and match scores for… MCP server?

Ladderboard — round-robin ladders and match scores for… is an MCP server listed in the public MCP registry as app.rowb.ladder/board. Round-robin ladders and match scores for small clubs. Players join by QR poster; no app, no account. This page covers its hosted endpoint (https://ladder.rowb.app/mcp).

Is the Ladderboard — round-robin ladders and match scores for… MCP server safe to use?

Ladderboard — round-robin ladders and match scores for… scores 56 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 Ladderboard — round-robin ladders and match scores for… MCP server expose?

Ladderboard — round-robin ladders and match scores for… exposes 5 tools: create_ladder, add_player, record_match, schedule_match, get_standings. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.

Does the Ladderboard — round-robin ladders and match scores for… MCP server require authentication?

No. We connected to Ladderboard — round-robin ladders and match scores for… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ladderboard — round-robin ladders and match scores for… MCP server still maintained?

Ladderboard — round-robin ladders and match scores for… is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.