# x402-repohealth-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/liminalpepe/x402-repohealth-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 143  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/x402-repohealth-mcp

## Description
Free MCP server: compute a GitHub repo maintenance/abandonment health score from live data.

## Tools
Capabilities this server exposes over MCP:

- **check_repo_health** — Compute a maintenance/abandonment health verdict for a public GitHub repo from live GitHub data: a 0-100 score across commit recency, commit activity, issue/PR responsiveness, and release cadence, plus a verdict (actively maintained / slowing down / likely abandoned / archived) and human-readable reasoning. Free, unauthenticated MCP tool — the open twin of the paid x402-gated repo-health HTTP API (https://x402-repohealth-poc.theliminalguy.workers.dev/repo-health/:owner/:repo), same scoring logic, no payment required. Useful before depending on a library/tool: is this repo safe to build on? Uses GitHub's unauthenticated public REST API (60 requests/hour/IP) — for higher-volume or agent-automated x402-metered use, call the paid Worker endpoint instead.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "x402-repohealth-mcp": {
    "command": "npx",
    "args": ["-y","x402-repohealth-mcp"]
  }
}
```

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/x402-repohealth-mcp/readme_