Log inSubmit server
X402 Repohealth MCP logo

X402 Repohealth MCP

Scores GitHub repository health from live public data, covering maintenance activity, responsiveness, releases, and abandonment risk.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install X402 Repohealth MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "x402-repohealth-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "x402-repohealth-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 1 tools correctly (1d ago).

Overview

The x402-repohealth-mcp MCP server evaluates GitHub repository maintenance using live data from GitHub’s public REST API. Its single `check_repo_health` tool accepts an owner and repository name, then returns a 0–100 score, dimension breakdown, metrics, verdict, and numerical reasoning. Use it when an agent needs to assess whether a dependency or project is actively maintained, slowing down, abandoned, or archived. It runs locally over stdio without a GitHub API key, but each call uses roughly three to four unauthenticated GitHub requests.

Use cases

  • Assess dependency maintenance before adoption
  • Screen GitHub repositories for abandonment risk
  • Compare project activity using consistent score dimensions
  • Give agents repository health evidence from live GitHub data

Key features

  • Live GitHub REST API scoring
  • 0–100 weighted health score
  • Commit, issue, pull request, and release metrics
  • Archived-repository override
  • Human-readable score reasoning
  • stdio MCP execution with npx

Tools1

What X402 Repohealth MCP lets your agent do. Expand a tool for its parameters.

Verified live~272 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 57d

What it can do

From the 1 tool this server returned when we ran it.

Makes network requests · 1Read-only tools · 1
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age97 days
Maintainers1

Observed 2026-11-07 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · x402-repohealth-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads143Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.

How X402 Repohealth MCP works

What x402-repohealth-mcp MCP server does

The x402-repohealth-mcp MCP server exposes one MCP tool, check_repo_health, for assessing a public GitHub repository. Provide an owner and repo, such as facebook and react, and the tool fetches current repository data before calculating a health result.

The result contains repository metadata, collection time, computed metrics, a score breakdown, an overall score from 0 to 100, a verdict, and a reasoning array based on the fetched values. The verdict categories are actively maintained, slowing down, likely abandoned, and archived. GitHub’s archived flag takes precedence over the numerical score.

The score allocates up to 25 points each to commit recency, commit activity, issue and pull request responsiveness, and release cadence. Metrics include values such as days since the last commit, commits during the previous 90 days, issue close ratios, and release timing.

How it works

At request time, the x402-repohealth-mcp MCP server queries GitHub’s unauthenticated public REST API. It does not use repository-specific hardcoded results or mocked data, and it does not cache responses. Each request therefore reflects the repository data available when the tool runs.

Commit recency is graded using time windows ranging from 14 days or less to more than one year. Commit activity counts commits in the trailing 90 days. Responsiveness examines recently updated issues and pull requests, using closure ratio and median close time where applicable. Release cadence is based on the time since the latest tagged release. Repositories with no recent issue activity or no releases receive neutral values for those dimensions.

An archived repository is treated as confirmed archived regardless of its calculated score. Otherwise, scores of 75 or higher are actively maintained, scores from 45 through 74 are slowing down, and scores below 45 are likely abandoned.

Setup and configuration

Run the published package with:

Terminal
npx x402-repohealth-mcp

A stdio MCP client can launch it with npx -y x402-repohealth-mcp. The README provides a Claude Desktop configuration using the repohealth server name, npx as the command, and -y x402-repohealth-mcp as arguments. No GitHub authentication variable is required for the local server.

For local development, the repository documents npm install, npm run dev, npm run build, and npm run test:health. The development server runs the TypeScript entry point over stdio; the health test calls the health function directly against real repositories.

Tools and capabilities

  • Check one GitHub repository with check_repo_health.
  • Return a weighted 0–100 maintenance score.
  • Report commit, issue or pull request, and release metrics.
  • Provide score components and human-readable reasoning.
  • Distinguish archived repositories from score-based abandonment verdicts.

Limitations and notes

The x402-repohealth-mcp MCP server uses GitHub’s unauthenticated limit of 60 requests per hour per IP, shared by local users of that IP. A health check consumes approximately three to four GitHub requests, so the local package is intended for free, local, or low-volume use. It has no caching, meaning repeated checks fetch the data again.

The repository also describes a separate paid HTTP Worker with the same scoring logic for non-MCP or higher-volume use. That endpoint is not part of the local MCP server and uses a server-side GitHub token. The local server itself is available under the MIT license.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about X402 Repohealth MCP

x402-repohealth-mcp is an MCP server that connects to GitHub’s public REST API and provides the `check_repo_health` tool. It accepts a repository owner and name, then returns live maintenance metrics, a 0–100 score, score dimensions, a verdict, and reasoning about activity, responsiveness, releases, or archival status.

Install and run it with `npx x402-repohealth-mcp`, or configure an MCP client to launch `npx -y x402-repohealth-mcp` over stdio. The README includes a Claude Desktop configuration example.

No, the local MCP server does not require a GitHub API key. It uses GitHub’s unauthenticated public REST API, which allows 60 requests per hour per IP; each health check uses approximately three to four requests.

It measures commit recency, commit activity, issue and pull request responsiveness, and release cadence, with up to 25 points for each dimension. The result also includes raw metrics, a total score, a verdict, and reasoning derived from the fetched values.

No, it does not cache results. Every `check_repo_health` call fetches current data from GitHub and recalculates the score at request time.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewX402 Repohealth MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/x402-repohealth-mcp?style=directory)](https://allmcps.com/mcp/x402-repohealth-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/x402-repohealth-mcp"><img src="https://allmcps.com/api/badge/x402-repohealth-mcp?style=directory" alt="X402 Repohealth MCP on AllMCPs" /></a>