# RallyIQ (remote · bigballi.com)

Tennis game plans, scouting reports and match breakdowns from shot-by-shot charted matches.

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

## Components

- remote · `bigballi.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp.md), [page](https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp)

## Channel facts

- Endpoint: `https://bigballi.com/RallyIQ/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1194 tokens (~238/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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).
  - Supports UI / widget rendering.

## Install

### How do I install the RallyIQ MCP server?

RallyIQ is a hosted endpoint at https://bigballi.com/RallyIQ/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 com-bigballi-rallyiq 'https://bigballi.com/RallyIQ/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-bigballi-rallyiq": {
      "url": "https://bigballi.com/RallyIQ/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-bigballi-rallyiq": {
      "type": "http",
      "url": "https://bigballi.com/RallyIQ/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-bigballi-rallyiq]
url = "https://bigballi.com/RallyIQ/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-bigballi-rallyiq": {
      "type": "remote",
      "url": "https://bigballi.com/RallyIQ/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-bigballi-rallyiq --url 'https://bigballi.com/RallyIQ/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-bigballi-rallyiq:
    url: "https://bigballi.com/RallyIQ/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-bigballi-rallyiq": {
      "Transport": "http",
      "Url": "https://bigballi.com/RallyIQ/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-bigballi-rallyiq -t streamable-http -u 'https://bigballi.com/RallyIQ/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-bigballi-rallyiq": {
      "type": "http",
      "url": "https://bigballi.com/RallyIQ/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-05 (score 88, +1)

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

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

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

### 2026-10-31 (score 86, +1)

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

### 2026-10-29 (score 85, +1)

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

### 2026-10-27 (score 84, +1)

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

### 2026-10-26 (score 83, +2)

- [functional improvement] Schema quality: 293 → 238
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 100
- [functional] Schema quality: excellent → good
- [functional] New resource “game-plan”

### 2026-10-25 (score 81, +1)

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

### 2026-10-23 (score 80, +1)

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

## MCP tools (4)

### `get_game_plan` (~213 tokens)

Tennis game plan for a matchup

A scouting game plan for one player against an opponent, from 11,822 shot-by-shot charted ATP and WTA matches: the match forecast with a 90% range (same tour only), where to serve first serves on each court against this returner and the optimal mix, which returns work best against this server, the rally shots to favour and to avoid, what the opponent tends to serve, career shot ratings side by side, style compatibility and the charted head-to-heads. Optionally for one surface.

Input parameters:

- `opponent` (string, required): The opponent, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
- `player` (string, required): The player the plan is for, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
- `surface` (string): Court surface for the forecast and rally plan (default all).

### `get_player` (~190 tokens)

Tennis player scouting report

One charted player's scouting report, found by name: serve and return points won against an average opponent, shot ratings per 100 shots (direction choice, shot selection, execution, long rallies, points left on the table) with tour percentiles, first-serve direction habits per court including on break points, how exploitable the serve is and the optimal mix, the shots they hurt opponents with most and the shots they are most exposed to, best-equipped opponents, stylistically similar players and recent charted matches. When the name matches several players it returns the best match and lists the others.

Input parameters:

- `name` (string, required): The player, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
- `tour` (string): Restrict the name search to one tour when a surname is shared (e.g. Williams).

### `explain_match` (~215 tokens)

Explain a charted tennis match

Why a charted match went the way it did: points won, and each player's gain or loss against expectation split into direction choice, shot selection and execution, by stroke and by set, the loser's biggest leaks and the points each player left on the table by not choosing the best-value direction. Finds the most recent charted match for a player, narrowed by opponent, tournament or year, and lists other matching matches.

Input parameters:

- `opponent` (string): The other player (optional), e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
- `player` (string, required): A player in the match, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
- `tournament` (string): Words from the tournament name, e.g. "Wimbledon", "Roland Garros", "Indian Wells".
- `year` (integer): Season of the match.

### `get_leaders` (~364 tokens)

Tennis tactical leaderboards

Top 10 ATP or WTA players on one tactical measure: direction_choice: Picks the more valuable direction for the stroke being hit (per 100 shots, opponent-adjusted). execution: Gets more out of a shot than the same choice usually yields (per 100 shots, opponent-adjusted). shot_selection: Chooses strokes worth more than the position average; partly reflects the ball they were given (per 100 shots, opponent-adjusted). fewest_points_left: Smallest gap per 100 shots between the direction chosen and the best-value direction for that stroke. most_exploitable_serve: Points per 100 first serves an optimal direction mix would win over the current one, allowing for returners reading a habit. serve_off_equilibrium: First-serve directions that win at clearly different rates (p < 0.01): usage-weighted gap per 100 first serves and the direction to use more. long_rallies_hold_up: Execution from the ninth shot of a rally on, minus the player's own earlier-rally execution, per 100 shots (ATP only). long_rallies_fade: The same long-rally measure, most fading first (ATP only). adaptability: Moves the first-serve mix toward what has been winning in earlier sets, per 100 first serves. A weak habit, not a proven gain. adapts_fastest: The same, every two to three service games, per 100 first serves. Players need at least 5,000 modelled shots.

Input parameters:

- `board` (string, required): Which leaderboard.
- `scope` (string): active: charted in the last three seasons (default); all_eras: every era.
- `tour` (string): atp (default) or wta.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 81
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-11: 74
- 2026-10-10: 74
- 2026-10-08: 73

## Common questions

### What is the RallyIQ MCP server?

RallyIQ is an MCP server listed in the public MCP registry as com.bigballi/rallyiq. Tennis game plans, scouting reports and match breakdowns from shot-by-shot charted matches. This page covers its hosted endpoint (https://bigballi.com/RallyIQ/mcp).

### Is the RallyIQ MCP server safe to use?

RallyIQ scores 88 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 RallyIQ MCP server expose?

RallyIQ exposes 4 tools: get_game_plan, get_player, explain_match, get_leaders. Their descriptions and schemas cost roughly 982 tokens of context every time the server is loaded.

### Does the RallyIQ MCP server require authentication?

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

### Is the RallyIQ MCP server still maintained?

RallyIQ 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 RallyIQ MCP server?

VerifyMCP ran 14 checks on RallyIQ, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.

## Links

- Remote endpoint: https://bigballi.com/RallyIQ/mcp
- Repository: https://github.com/BigBalli/rallyiq-mcp
- Website: https://bigballi.com/RallyIQ/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-bigballi-rallyiq/rallyiq-mcp