io.github.yugantm/hvtracker-mcp
by YugantM
README.md
# HVTracker MCP
[](https://smithery.ai/servers/hvtracker/hvtracker-mcp)
[](https://www.npmjs.com/package/hvtracker-mcp) [](https://pypi.org/project/hvtracker-mcp/) [](LICENSE)
MCP server for checking supply-chain trust before connecting to AI agents,
frameworks, or MCP servers.
The hosted remote server is:
```json
{
"mcpServers": {
"hvtracker": {
"url": "https://hvtracker.net/mcp"
}
}
}
```
This repository also provides a local stdio package for clients that prefer
package-based installation.
<!-- mcp-name: io.github.YugantM/hvtracker-mcp -->
## Tools
- `verify_mcp_server`: pre-connect trust verdict for an MCP server, package, GitHub repo, or agent name.
- `check_agent_trust`: trust profile for a tracked AI agent or framework — incl. runtime capabilities (MCP status, providers, plugin surface, provenance drift) and the URL of its Ed25519-signed trust credential.
- `compare_agents`: two agents side by side with an evidence-based verdict and the published compare-page link.
- `search_agents`: search the HVTracker registry by name, repo, description, or category.
- `scan_stack`: bulk pre-connect trust check for a whole dependency set — paste a requirements.txt, package.json, MCP client config, or a plain list and get a trust verdict per item plus a stack summary.
- `list_categories`: list the HVTracker categories with agent counts, so you can then pull a category's leaderboard.
- `get_leaderboard`: top tracked AI agents and MCP servers ranked by HVTrust score, optionally filtered to one category.
- `get_agent_history`: 90-day trust-score, grade, and rank history for one tracked agent — is it improving or declining?
## Local Install
With npm:
```bash
npm install -g hvtracker-mcp
```
With PyPI:
```bash
python3 -m pip install hvtracker-mcp
```
Example MCP client config:
```json
{
"mcpServers": {
"hvtracker": {
"command": "hvtracker-mcp"
}
}
}
```
## Development
```bash
python3 -m pip install -e ".[dev]"
python3 -m pytest
hvtracker-mcp
```
Use a different HVTracker base URL while testing:
```bash
HVTRACKER_BASE_URL=http://localhost:8080 hvtracker-mcp
```
## Registry Publishing
The official MCP Registry manifest is `server.json`.
```bash
mcp-publisher login github
mcp-publisher publish
```
In GitHub Actions, run the "Publish MCP Registry" workflow after the npm,
PyPI, and GHCR packages for the same version are live.
The server name is:
```text
io.github.YugantM/hvtracker-mcp
```
## Claude Desktop Extension
Tagged releases build an `.mcpb` bundle for Claude Desktop from `manifest.json`.
To build it locally:
```bash
npm ci --omit=dev
npx @anthropic-ai/mcpb@2.1.2 pack
```
## Privacy
HVTracker MCP sends the user-supplied search string or server identifier to
`https://hvtracker.net` to fetch public trust data. It does not require an API
key and does not write to user systems. See the HVTracker site for current data
and methodology, and see `PRIVACY.md` for the repository privacy note.
TDQS
A3.9/5.0
Scored across 8 tools
Disambiguation4/5
Most tools have distinct purposes, but check_agent_trust and verify_mcp_server both provide trust verdicts for agents/servers, potentially causing confusion. Descriptions help differentiate, but overlap remains.
Naming Consistency5/5
All tool names consistently follow a verb_noun pattern in snake_case, such as check_agent_trust, compare_agents, and list_categories.
Tool Count5/5
With 8 tools, the server covers core querying needs without being cluttered. Each tool serves a clear function, and the count feels appropriate for a trust tracker.
Completeness4/5
The set covers trust checks, comparison, history, leaderboard, categories, bulk scanning, search, and MCP verification. Minor gaps exist, such as no individual category detail tool, but overall coverage is solid.
Maintenance
ActivityMaintained
ResponsivenessNo issues