# Openpowerlifting (npm · @pipeworx/mcp-openpowerlifting)

openpowerlifting -- powerlifting competition results from the OpenPowerlifting project's…

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

## Components

- remote · `gateway.pipeworx.io`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-openpowerlifting/openpowerlifting-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-openpowerlifting/openpowerlifting-mcp)
- npm · `@pipeworx/mcp-openpowerlifting`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-openpowerlifting/pipeworx-mcp-openpowerlifting.md), [page](https://verifymcp.io/servers/pipeworx-io-openpowerlifting/pipeworx-mcp-openpowerlifting)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-openpowerlifting`
- 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-openpowerlifting).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1047 tokens (~349/item across 3 items; 3 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**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Openpowerlifting MCP server?

Openpowerlifting runs locally as an npm package, launched with npx -y @pipeworx/mcp-openpowerlifting. 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-openpowerlifting -- npx -y @pipeworx/mcp-openpowerlifting
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 65, −14)

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

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

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

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

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

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `opl_lifter_history` (~293 tokens)

Competition history of one powerlifter from the OpenPowerlifting results database: every meet entered (most recent first) with federation, event, equipment, division, bodyweight and weight class, best squat/bench/deadlift, total, place and Dots/Wilks/Goodlift points, plus career bests. Pass name as shown in results (e.g. "Ray Williams"; case-insensitive, exact name). Lifters who share a name are disambiguated in the data as "Name #1", "Name #2": a name that matches several lifters returns their candidates (name, country, entry count, years, best total) instead of mixing them -- pass the exact "Name #N". equipment (Raw, Wraps, Single-ply, Multi-ply, Unlimited, Straps) narrows the history and the bests. Rows page with limit/offset and report truncated/total_matching. An unknown name returns found:false with data_as_of, never an empty list. Weights are in kilograms.

Input parameters:

- `equipment` (string): Only entries in this equipment category.
- `limit` (number): Entries per page, 1-200 (default 50).
- `name` (string, required): Lifter name as in results, e.g. "Ray Williams" or "John Smith #2".
- `offset` (number): Entries to skip (default 0).

### `opl_meet_results` (~368 tokens)

Results of one powerlifting meet from the OpenPowerlifting database. Pass meet_id (from a previous call) or meet, a name search (every word must appear, e.g. "arnold classic"), optionally with federation (e.g. "USAPL", "IPF") and year to narrow it. If the search matches several meets the call returns the candidate list (meet_id, name, date, federation, town, country, entries) instead of guessing; with one match it returns the lifters ordered by sex, equipment, division, weight class and place, with bodyweight, best lifts, total, place and points. Optional filters sex (M/F/Mx), equipment, weight_class (e.g. "83", "84+") and division narrow the lifters. Rows page with limit/offset and report truncated/total_matching. No matching meet returns found:false with data_as_of. Weights are in kilograms.

Input parameters:

- `division` (string): Division text, e.g. "Open", "Juniors 20-23".
- `equipment` (string)
- `federation` (string): Federation code, e.g. "IPF", "USAPL", "WRPF".
- `limit` (number): Lifters per page, 1-200 (default 50).
- `meet` (string): Meet name search, e.g. "world classic".
- `meet_id` (number): Meet id from an earlier opl_meet_results / opl_lifter_history call.
- `offset` (number): Lifters to skip (default 0).
- `sex` (string)
- `weight_class` (string): Weight class as recorded, e.g. "83" or "84+".
- `year` (number): Meet year.

### `opl_records` (~332 tokens)

All-time best powerlifting performances from the OpenPowerlifting database: the top lifters by total, squat, bench, deadlift or Dots points for a sex and equipment category, optionally narrowed by weight_class (e.g. "83", "84+"), federation, age_class (e.g. "24-34"), tested (drug-tested meets only) and year. One row per lifter (their best qualifying entry), with the meet and date. Lifts are in kilograms. total is only ranked over full three-lift (SBD) entries unless event is given. These are the best entries IN THE DATA, filtered as asked -- not an official federation record list (federations apply their own rules and equipment definitions). Nothing matching returns found:false with data_as_of.

Input parameters:

- `age_class` (string): e.g. "24-34", "40-44".
- `equipment` (string): Default Raw.
- `event` (string): SBD, B, D, BD, SB... Default SBD for lift=total; none otherwise.
- `federation` (string): Federation code, e.g. "IPF".
- `lift` (string): What to rank by (default total).
- `limit` (number): Lifters to return, 1-50 (default 10).
- `sex` (string, required): M, F or Mx.
- `tested` (boolean): true = drug-tested meets only.
- `weight_class` (string): e.g. "83", "93", "120+".
- `year` (number): Only meets in this year.

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 65
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77

## Common questions

### What is the Openpowerlifting MCP server?

Openpowerlifting is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openpowerlifting. openpowerlifting -- powerlifting competition results from the OpenPowerlifting project's… This page covers its npm package (@pipeworx/mcp-openpowerlifting).

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

Openpowerlifting scores 80 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 Openpowerlifting MCP server expose?

Openpowerlifting exposes 3 tools: opl_lifter_history, opl_meet_results, opl_records. Their descriptions and schemas cost roughly 993 tokens of context every time the server is loaded.

### Is the Openpowerlifting MCP server still maintained?

Openpowerlifting 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 Openpowerlifting MCP server under?

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

## Links

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