# NextArena Tournament Tools (remote · www.nextarena.co)

Free padel Americano and Mexicano draws, pickleball round robins and knockout brackets.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.nextarena.co`: 74/100 (this document), [markdown](https://verifymcp.io/servers/co-nextarena-tournament-tools/api-mcp.md), [page](https://verifymcp.io/servers/co-nextarena-tournament-tools/api-mcp)

## Channel facts

- Endpoint: `https://www.nextarena.co/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2599 tokens (~433/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 72% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the NextArena Tournament Tools MCP server?

NextArena Tournament Tools is a hosted endpoint at https://www.nextarena.co/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.

### Claude

```bash
claude mcp add --transport http co-nextarena-tournament-tools 'https://www.nextarena.co/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-nextarena-tournament-tools": {
      "url": "https://www.nextarena.co/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-nextarena-tournament-tools": {
      "type": "http",
      "url": "https://www.nextarena.co/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-nextarena-tournament-tools]
url = "https://www.nextarena.co/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-nextarena-tournament-tools": {
      "type": "remote",
      "url": "https://www.nextarena.co/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-nextarena-tournament-tools --url 'https://www.nextarena.co/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-nextarena-tournament-tools:
    url: "https://www.nextarena.co/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-nextarena-tournament-tools": {
      "Transport": "http",
      "Url": "https://www.nextarena.co/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-nextarena-tournament-tools -t streamable-http -u 'https://www.nextarena.co/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-nextarena-tournament-tools": {
      "type": "http",
      "url": "https://www.nextarena.co/api/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 74, +1)

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

### 2026-11-02 (score 73, +1)

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

### 2026-10-30 (score 72, +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.

### 2026-10-28 (score 71, +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.

### 2026-10-26 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 69)

First indexed and scored.

## MCP tools (6)

### `get_supported_tournament_options` (~114 tokens)

Choose supported tournament options

Use for a generic tournament request with no confirmed sport or format, or to discover NextArena's supported sports, formats, entrant types and limits. Does not generate a tournament or select defaults. With no sport, ask Pickleball or padel first; with a confirmed sport, return only its formats. Do not display all formats as interchangeable across sports.

Input parameters:

- `sport` (string): Only include a sport the user has selected for this tournament. Omit it when unknown; never infer it from unrelated previous requests.

### `generate_round_robin` (~608 tokens)

Generate a round robin

MANDATORY BEFORE CALLING: the user must have chosen BOTH sport and format for THIS tournament. If either is missing, ask instead of generating, or call get_supported_tournament_options to discover choices. Never infer sport or format from unrelated previous conversations, previous tool use, player/court counts or a default. 'Make a tournament for 20 players on four courts' requires clarification, not an Americano. Reuse choices explicitly confirmed earlier in this same tournament setup. Clarify individuals versus fixed teams when ambiguous. For PICKLEBALL only: generate singles, fixed-team or rotating-doubles round-robin fixtures. Establish sport first; offer pickleball round robin or knockout, and padel Americano or Mexicano. Before calling, establish singles vs fixed teams vs rotating partners, whether the count means players or teams, full round robin vs a limited number of rounds, match duration and available session time. Never infer fixed teams from an individual player count. A full singles/fixed-team draw has n*(n-1)/2 matches and may require multiple court waves per round. Pickleball rotating partners use mode rotating_doubles here, with a numeric round count, not generate_americano. Do not promise everyone meets everyone in rotating doubles. Always show the returned fixtures in full, round by round; never replace them with a summary. Return total matches and estimated session length; if it exceeds the user's time, discuss a shorter partial draw rather than silently changing format. Free draft only; no saving or publishing.

Input parameters:

- `count` (integer, required): Confirmed entrant count: individual players for singles or rotating doubles, complete teams for fixed doubles. Never silently divide a player count into teams; confirm the format and team count first.
- `courts` (integer, required): Number of available courts.
- `durationMinutes` (integer, required): Confirmed match duration in minutes, including any changeover allowance. Ask rather than silently assuming 20 minutes.
- `mode` (string, required): Required pickleball choice: singles, fixed doubles teams or rotating doubles with individual players. Ask when unspecified. Keep pickleball rotating doubles here; Americano is the padel tool.
- `names` (array): Optional player names, or team names for fixed doubles. Supply exactly count names, or omit for numbered placeholders. Do not include contact details.
- `restMinutes` (integer)
- `rounds` (required): Required schedule choice. For rotating doubles, supply a numeric round count. Use auto only when the user wants a full singles or fixed-team round robin; a number limits the draw to that many rounds.…
- `seed` (integer): Keep this value unchanged to reproduce a draw; change it only when requesting a new draw.
- `sport` (string, required): Confirmed sport. NextArena offers pickleball round robin and knockout brackets; ask for the sport if missing.
- `startTime` (string): Local start time in HH:MM, 24-hour format.

### `generate_americano` (~428 tokens)

Generate an Americano

MANDATORY BEFORE CALLING: the user must have chosen BOTH sport and format for THIS tournament. If either is missing, ask instead of generating, or call get_supported_tournament_options to discover choices. Never infer sport or format from unrelated previous conversations, previous tool use, player/court counts or a default. 'Make a tournament for 20 players on four courts' requires clarification, not an Americano. Reuse choices explicitly confirmed earlier in this same tournament setup. Clarify individuals versus fixed teams when ambiguous. Use this when the user wants a PADEL Americano tournament (not pickleball; use generate_round_robin with rotating_doubles for pickleball rotating partners), rotating doubles partners, balanced rests and varied opponents. Plans rounds before play. Each entrant is an individual player. Always show the returned schedule in full, round by round: start time, court, both pairs and who rests. Never replace it with a summary. Set restMinutes when the user wants a break between rounds. After the schedule, pass on any warning about uneven rests and its suggested round counts. Does not save or publish an event; do not use for score-led Mexicano pairings.

Input parameters:

- `count` (integer, required)
- `courts` (integer, required): Number of available courts.
- `durationMinutes` (integer)
- `names` (array): Optional player names, or team names for fixed doubles. Supply exactly count names, or omit for numbered placeholders. Do not include contact details.
- `pointsPerMatch` (integer): Combined rally points shared by the two pairs, not points per pair. Both final scores must add to this number.
- `preference` (string)
- `restMinutes` (integer)
- `rounds`
- `seed` (integer): Keep this value unchanged to reproduce a draw; change it only when requesting a new draw.
- `sport` (string, required): Confirmed sport. NextArena offers padel Americano and Mexicano; ask for the sport if missing.
- `startTime` (string): Local start time in HH:MM, 24-hour format.

### `generate_bracket` (~333 tokens)

Generate a knockout bracket

MANDATORY BEFORE CALLING: the user must have chosen BOTH sport and format for THIS tournament. If either is missing, ask instead of generating, or call get_supported_tournament_options to discover choices. Never infer sport or format from unrelated previous conversations, previous tool use, player/court counts or a default. 'Make a tournament for 20 players on four courts' requires clarification, not an Americano. Reuse choices explicitly confirmed earlier in this same tournament setup. Clarify individuals versus fixed teams when ambiguous. Use this when the user wants a PICKLEBALL seeded or random single-elimination tournament bracket with byes, court assignments and provisional match times. Always show every returned match with its round, court and time; never replace it with a summary. Does not record winners, save an event or support double elimination.

Input parameters:

- `count` (integer, required)
- `courts` (integer, required): Number of available courts.
- `durationMinutes` (integer)
- `names` (array): Optional player names, or team names for fixed doubles. Supply exactly count names, or omit for numbered placeholders. Do not include contact details.
- `seed` (integer): Keep this value unchanged to reproduce a draw; change it only when requesting a new draw.
- `seeded` (boolean): When true, names are in seed order, strongest first. When false, randomize using seed.
- `sport` (string, required): Confirmed sport. NextArena offers pickleball round robin and knockout brackets; ask for the sport if missing.
- `startTime` (string): Local start time in HH:MM, 24-hour format.

### `generate_mexicano_round` (~345 tokens)

Generate a Mexicano round

MANDATORY BEFORE CALLING: the user must have chosen BOTH sport and format for THIS tournament. If either is missing, ask instead of generating, or call get_supported_tournament_options to discover choices. Never infer sport or format from unrelated previous conversations, previous tool use, player/court counts or a default. 'Make a tournament for 20 players on four courts' requires clarification, not an Americano. Reuse choices explicitly confirmed earlier in this same tournament setup. Clarify individuals versus fixed teams when ambiguous. Use this when the user asks to generate or run a PADEL Mexicano tournament. Creates round 1 from player count and courts, or the next round using all completed prior scores and individual standings. Always show the returned round in full: time, court, both pairs and who rests. Future pairings cannot be known in advance. If players must rest (count not a multiple of 4, or more players than court places), offer config.ranking: average (points per match) so extra rests do not cost anyone, and suggest a round count that gives equal rests. Set config.restMinutes when the user wants a break between rounds. Stateless: return the prior state with scores filled in. Does not save, publish or change a live tournament.

Input parameters:

- `config` (object, required)
- `previousRounds` (array): Completed rounds with scores. Player IDs are zero-based indexes in config.names. Preserve pairings and byes from the returned state; fill in scores. If an earlier score changes, discard later rounds…
- `seed` (integer): Keep this value unchanged to reproduce a draw; change it only when requesting a new draw.

### `calculate_mexicano_standings` (~242 tokens)

Calculate Mexicano standings

MANDATORY BEFORE CALLING: the user must have chosen BOTH sport and format for THIS tournament. If either is missing, ask instead of generating, or call get_supported_tournament_options to discover choices. Never infer sport or format from unrelated previous conversations, previous tool use, player/court counts or a default. 'Make a tournament for 20 players on four courts' requires clarification, not an Americano. Reuse choices explicitly confirmed earlier in this same tournament setup. Clarify individuals versus fixed teams when ambiguous. Use this when the user wants individual PADEL Mexicano standings from completed round scores, without generating another round. Supply config and all completed previousRounds. Each player receives their pair's rally points. Does not save or publish results.

Input parameters:

- `config` (object, required)
- `previousRounds` (array): Completed rounds with scores. Player IDs are zero-based indexes in config.names. Preserve pairings and byes from the returned state; fill in scores. If an earlier score changes, discard later rounds…
- `seed` (integer): Keep this value unchanged to reproduce a draw; change it only when requesting a new draw.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-nextarena-tournament-tools/api-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69

## Common questions

### What is the NextArena Tournament Tools MCP server?

NextArena Tournament Tools is an MCP server listed in the public MCP registry as co.nextarena/tournament-tools. Free padel Americano and Mexicano draws, pickleball round robins and knockout brackets. This page covers its hosted endpoint (https://www.nextarena.co/api/mcp).

### Is the NextArena Tournament Tools MCP server safe to use?

NextArena Tournament Tools scores 74 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 NextArena Tournament Tools MCP server expose?

NextArena Tournament Tools exposes 6 tools: get_supported_tournament_options, generate_round_robin, generate_americano, generate_bracket, generate_mexicano_round, calculate_mexicano_standings. Their descriptions and schemas cost roughly 2,070 tokens of context every time the server is loaded.

### Does the NextArena Tournament Tools MCP server require authentication?

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

### Is the NextArena Tournament Tools MCP server still maintained?

NextArena Tournament Tools 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.

## Links

- Remote endpoint: https://www.nextarena.co/api/mcp
- Website: https://www.nextarena.co/tools/mcp
- Changelog RSS feed: https://verifymcp.io/servers/co-nextarena-tournament-tools/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-nextarena-tournament-tools/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-nextarena-tournament-tools/api-mcp