HVTracker MCP
MCP server for checking supply-chain trust before connecting to AI agents, frameworks, or MCP servers.
The hosted remote server is:
{
"mcpServers": {
"hvtracker": {
"url": "https://hvtracker.net/mcp"
}
}
}
This repository also provides a local stdio package for clients that prefer package-based installation.
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.
Local Install
With npm:
npm install -g hvtracker-mcp
With PyPI:
python3 -m pip install hvtracker-mcp
Example MCP client config:
{
"mcpServers": {
"hvtracker": {
"command": "hvtracker-mcp"
}
}
}
Development
python3 -m pip install -e ".[dev]"
python3 -m pytest
hvtracker-mcp
Use a different HVTracker base URL while testing:
HVTRACKER_BASE_URL=http://localhost:8080 hvtracker-mcp
Registry Publishing
The official MCP Registry manifest is server.json.
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:
io.github.YugantM/hvtracker-mcp
Claude Desktop Extension
Tagged releases build an .mcpb bundle for Claude Desktop from manifest.json.
To build it locally:
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.
Release files for hvtracker-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hvtracker_mcp-0.3.0.tar.gz | 10.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hvtracker_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.2 kB
Release files / hvtracker_mcp-0.3.0.tar.gz
| Download URL | hvtracker_mcp-0.3.0.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
785a3cae9ee955170893c97368293de0a8f34af1ad3615735704e575c5742e67
|
|
BLAKE2b-256 checksum How to use checksums |
a199b9fa8b840ba6d88cc5e370d643b9f1018437734e988d85b0b744900e869b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency logRelease files / hvtracker_mcp-0.3.0-py3-none-any.whl
| Download URL | hvtracker_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26abfdbb0be2e526a7cc252250349c4dee60305a844a6c295a1b3b5875a721c4
|
|
BLAKE2b-256 checksum How to use checksums |
f7190f6f0c87f4835d7d718749caa86c065508df4d08f62b1c4dbfcbd80c619d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency log