x402-repohealth-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_repo_healthA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly and specifically defined, making it unambiguous for agents.
The single tool name follows a clean verb_noun pattern ('check_repo_health'), which is internally consistent. With only one tool, there are no conflicting conventions.
The server has exactly one tool, which feels thin for a typical server but is justified by its narrow, single-purpose scope. It is borderline, as 1-2 tools are on the edge of being too few.
The tool covers the entire domain of repo health assessment, providing a score, verdict, and reasoning based on all relevant GitHub data. There are no obvious gaps for the stated purpose.