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.

Codestats

NPM · @PIPEWORX/MCP-CODESTATS · 2 COMPONENTS

Code::Stats MCP — public user XP / activity.

+4 this week 80 Trust /100

Last scanned (2 hours ago)

Scores higher than 65% of npm servers

Category Developer Tools

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-codestats). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 155 tokens (~77/item across 2 items; 2 tools + 0 resources), lean.Pass
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 +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.

  • 3 Nov 26 +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.

  • 1 Nov 26 +27
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 31 Oct 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 76

    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-codestats@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-codestats
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-codestats/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612145475
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4b0e37a27341ea84ba32ba107921caa543e18ad89e813c0978b7146048af5a6c23c702e756959bd44c03fad0bcaf2a68a387a94657264c33c59baf565

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 · 2 exposed · ~100 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
recent ~72

Code::Stats (codestats.net) — the XP one Code::Stats user has earned in roughly the last 12 hours, broken out by programming language and by machine, alongside their lifetime profile totals. Answers how much a Code::Stats user has coded today and in which languages.

NameTypeReqDescription
usernamestringyes–

No output schema declared.

No examples provided.

user ~28

Public profile — total XP, per-language XP, per-machine XP.

NameTypeReqDescription
usernamestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Codestats MCP server?

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

# add to Claude Code
claude mcp add pipeworx-io-codestats -- npx -y @pipeworx/mcp-codestats
Common questions

What is the Codestats MCP server?

Codestats is an MCP server listed in the public MCP registry as io.github.pipeworx-io/codestats. Code::Stats MCP, public user XP / activity. This page covers its npm package (@pipeworx/mcp-codestats).

Is the Codestats MCP server safe to use?

Codestats 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 Codestats MCP server expose?

Codestats exposes 2 tools: user, recent. Their descriptions and schemas cost roughly 100 tokens of context every time the server is loaded.

Is the Codestats MCP server still maintained?

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

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