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.

Openpowerlifting

NPM · @PIPEWORX/MCP-OPENPOWERLIFTING · 2 COMPONENTS

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

+3 this week 80 Trust /100

Last scanned (7 hours ago)

Scores higher than 65% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openpowerlifting). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 2 Nov 26 +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.

  • 31 Oct 26 +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.

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 77

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-openpowerlifting@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-openpowerlifting
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-openpowerlifting/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3685130848
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7ccee863a0c500538b65c8fcbdac86c1947a53227d5a678b5f9db40a8bf921ae42069759c23e28d84d8deaba044cc77d2e83a78bf1ec36e691c0acdee

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~993 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
opl_lifter_history ~293

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.

NameTypeReqDescription
equipmentstring–Only entries in this equipment category.
limitnumber–Entries per page, 1-200 (default 50).
namestringyesLifter name as in results, e.g. "Ray Williams" or "John Smith #2".
offsetnumber–Entries to skip (default 0).

No output schema declared.

No examples provided.

opl_meet_results ~368

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.

NameTypeReqDescription
divisionstring–Division text, e.g. "Open", "Juniors 20-23".
equipmentstring––
federationstring–Federation code, e.g. "IPF", "USAPL", "WRPF".
limitnumber–Lifters per page, 1-200 (default 50).
meetstring–Meet name search, e.g. "world classic".
meet_idnumber–Meet id from an earlier opl_meet_results / opl_lifter_history call.
offsetnumber–Lifters to skip (default 0).
sexstring––
weight_classstring–Weight class as recorded, e.g. "83" or "84+".
yearnumber–Meet year.

No output schema declared.

No examples provided.

opl_records ~332

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.

NameTypeReqDescription
age_classstring–e.g. "24-34", "40-44".
equipmentstring–Default Raw.
eventstring–SBD, B, D, BD, SB... Default SBD for lift=total; none otherwise.
federationstring–Federation code, e.g. "IPF".
liftstring–What to rank by (default total).
limitnumber–Lifters to return, 1-50 (default 10).
sexstringyesM, F or Mx.
testedboolean–true = drug-tested meets only.
weight_classstring–e.g. "83", "93", "120+".
yearnumber–Only meets in this year.

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-openpowerlifting

# add to Claude Code
claude mcp add pipeworx-io-openpowerlifting -- npx -y @pipeworx/mcp-openpowerlifting
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.