# Historical Baseball (npm · @pipeworx/mcp-historical-baseball)

historical-baseball -- MLB history from Retrosheet game logs and the SABR Lahman Baseball Database…

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

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-historical-baseball/historical-baseball-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-historical-baseball/historical-baseball-mcp)
- npm · `@pipeworx/mcp-historical-baseball`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball.md), [page](https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-historical-baseball`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-historical-baseball).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1148 tokens (~229/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Historical Baseball MCP server?

Historical Baseball runs locally as an npm package, launched with npx -y @pipeworx/mcp-historical-baseball. 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 pipeworx-io-historical-baseball -- npx -y @pipeworx/mcp-historical-baseball
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-historical-baseball": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-historical-baseball"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-historical-baseball": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-historical-baseball"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-historical-baseball -- npx -y @pipeworx/mcp-historical-baseball
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-historical-baseball": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-historical-baseball"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-historical-baseball --command npx --arg -y --arg @pipeworx/mcp-historical-baseball
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-historical-baseball:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-historical-baseball"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-historical-baseball": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-historical-baseball"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-historical-baseball -t stdio -c npx -a -y @pipeworx/mcp-historical-baseball
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-historical-baseball": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-historical-baseball"
      ]
    }
  }
}
```

## 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 83, +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.

### 2026-11-03 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (5)

### `baseball_player_history` (~211 tokens)

Year-by-year MLB batting and/or pitching statistics for one player's whole career, from the SABR Lahman Baseball Database (1871-2025). Pass a player NAME ("Babe Ruth", "Walter Johnson") or an exact Lahman player_id (e.g. "ruthba01") -- a name is resolved by exact then fuzzy match; if more than one player matches, a list of candidates (with player_id, birth year, debut) is returned instead of a guess, so the caller can re-ask with the exact player_id. Returns every season the player appears in Batting.csv and/or Pitching.csv (most players have only one; a few, like Babe Ruth, have both). Each season row has team, league, games and the standard counting stats. Unknown or ambiguous names are refused with a clear error/candidate-list, never an empty success.

Input parameters:

- `player` (string, required): Player name ("Hank Aaron") or exact Lahman player_id ("aaronha01").

### `baseball_team_season` (~202 tokens)

One MLB team's full-season record and stats for one year, from the SABR Lahman Baseball Database (1871-2025): wins/losses, division/league/World Series result, runs scored and allowed, team batting and pitching totals, home park and attendance. Pass team as a 3-letter-ish code ("NYA", "BOS") or a common name ("Yankees", "Red Sox", "Dodgers") -- codes changed for some relocated/renamed franchises over the years (e.g. the Athletics' code changed for 2025), so an unrecognized code for that year is refused with a clear error rather than an empty success; try the franchise's name instead, or call with a nearby year to see what code that franchise used.

Input parameters:

- `team` (string, required): Team code ("LAN") or common name ("Dodgers").
- `year` (number, required): Season year, e.g. 1927.

### `baseball_game_log` (~256 tokens)

Box-score-level summary of MLB game(s) played by one team on one date, from Retrosheet game logs (1871-2025): final score, game length, day/night, park, attendance, winning/losing/saving pitcher, managers, and each side's at-bats/hits/doubles/triples/homers/RBI/walks/strikeouts/errors. Covers regular season plus All-Star, Division Series, League Championship Series, Wild Card and World Series games (see game_type in the response: R/A/D/L/C/W). Pass date as "YYYY-MM-DD" or "YYYYMMDD" and team as a code ("NYA") or common name ("Yankees"). Returns an array because doubleheaders are two games on one date. This is a per-game SUMMARY, not a play-by-play log -- no pitch or at-bat level detail is stored. No games found for a valid date/team combination is reported as found:false with the reason, never an empty array treated as success.

Input parameters:

- `date` (string, required): Game date, "YYYY-MM-DD" or "YYYYMMDD".
- `team` (string, required): Team code ("BOS") or common name ("Red Sox").

### `baseball_season_leaders` (~349 tokens)

Top players in one MLB season for one statistic, from the SABR Lahman Baseball Database. Batting stats: HR, AVG, RBI, R, H, SB, BB, SO, 2B, 3B (AVG = hits/at-bats, qualified at a simple AB>=100 floor -- NOT MLB's official plate-appearance qualifying rule, so this can include players who would not qualify for an official batting title). Pitching stats: W, ERA, SO_P, SV, L, WHIP (SO_P = pitcher strikeouts, to avoid colliding with batting SO; ERA and WHIP are qualified at a simple IPouts>=100 i.e. ~33 innings floor, also not the official rule). Pass stat exactly as listed (case-sensitive). Optionally scope to one league ("AL" or "NL"; pre-1901 leagues like "NA", "AA", "UA", "PL" also appear in the data). limit caps how many rows come back (default 10, max 50). An unrecognized stat name is refused with the list of valid ones, never an empty success.

Input parameters:

- `league` (string): Optional: scope to one league code ("AL", "NL", or an historical league code).
- `limit` (number): Max rows to return, 1-50. Default 10.
- `stat` (string, required): One of: HR, AVG, RBI, R, H, SB, BB, SO, 2B, 3B, W, ERA, SO_P, SV, L, WHIP.
- `year` (number, required): Season year, e.g. 1998.

### `baseball_coverage` (~75 tokens)

What this pack actually has loaded right now: the Retrosheet game-log date range, how many games, the latest Lahman season year, and when it was last loaded. Call this if a query for a date or year you expect to exist comes back not-found, to rule out a coverage gap before assuming a typo.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 66
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Historical Baseball MCP server?

Historical Baseball is an MCP server listed in the public MCP registry as io.github.pipeworx-io/historical-baseball. historical-baseball -- MLB history from Retrosheet game logs and the SABR Lahman Baseball Database… This page covers its npm package (@pipeworx/mcp-historical-baseball).

### Is the Historical Baseball MCP server safe to use?

Historical Baseball scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Historical Baseball MCP server expose?

Historical Baseball exposes 5 tools: baseball_player_history, baseball_team_season, baseball_game_log, baseball_season_leaders, baseball_coverage. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.

### Is the Historical Baseball MCP server still maintained?

Historical Baseball 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 licence is the Historical Baseball MCP server under?

Historical Baseball declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Historical Baseball MCP server?

VerifyMCP ran 16 checks on Historical Baseball, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-historical-baseball
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-historical-baseball
- Repository: https://github.com/pipeworx-io/mcp-historical-baseball
- Website: https://pipeworx.io/packs/historical-baseball
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-historical-baseball/pipeworx-mcp-historical-baseball
