# HVTracker MCP (oci · ghcr.io/yugantm/hvtracker-mcp) Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry. - Trust score: 46/100 (low) - Change this week: −5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `hvtracker.net`: 84/100, [markdown](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker.md), [page](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker) - npm · `hvtracker-mcp`: 92/100, [markdown](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker-mcp.md), [page](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker-mcp) - oci · `ghcr.io/yugantm/hvtracker-mcp`: 46/100 (this document), [markdown](https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp.md), [page](https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp) - pypi · `hvtracker-mcp`: 75/100, [markdown](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker-mcp-2.md), [page](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker-mcp-2) ## Channel facts - Registry: `oci` - Package: `ghcr.io/yugantm/hvtracker-mcp` - Version: `v0.4.0` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 36 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 69/100 - AI-judged instruction clarity (good). - Tool/resource definitions use about 450 tokens (~56/item across 8 items; 8 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 67/100 - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the HVTracker MCP server? HVTracker MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/yugantm/hvtracker-mcp:v0.4.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add yugantm-hvtracker-mcp -- docker run --rm -i ghcr.io/yugantm/hvtracker-mcp:v0.4.0 ``` ### Cursor ```json { "mcpServers": { "yugantm-hvtracker-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/yugantm/hvtracker-mcp:v0.4.0" ] } } } ``` ### VS Code ```json { "servers": { "yugantm-hvtracker-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/yugantm/hvtracker-mcp:v0.4.0" ] } } } ``` ### Codex ```bash codex mcp add yugantm-hvtracker-mcp -- docker run --rm -i ghcr.io/yugantm/hvtracker-mcp:v0.4.0 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "yugantm-hvtracker-mcp": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/yugantm/hvtracker-mcp:v0.4.0" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: yugantm-hvtracker-mcp: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/yugantm/hvtracker-mcp:v0.4.0"] ``` ### Netclaw ```json { "McpServers": { "yugantm-hvtracker-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/yugantm/hvtracker-mcp:v0.4.0" ] } } } ``` ### Other ```json { "mcpServers": { "yugantm-hvtracker-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/yugantm/hvtracker-mcp:v0.4.0" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 46, −5) - [functional] Stability: pass → 0.63 ### 2026-10-29 (score 51, 0) - [security] Stability: 0.97 → pass ### 2026-10-28 (score 51, +1) No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-26 (score 50, +1) No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-24 (score 49, +1) No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-22 (score 48, +1) No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-20 (score 47, +1) No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-17 (score 46, +1) No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (8) ### `verify_mcp_server` (~81 tokens) Verify MCP Server Pre-connect trust verdict for an MCP server or AI agent. Pass a GitHub owner/repo, GitHub URL, npm/PyPI package, display name, slug, or MCP server URL. Unknown servers return trusted=false because HVTracker has no independent evidence, not because harm is proven. Input parameters: - `server` (string, required) ### `check_agent_trust` (~58 tokens) Check Agent Trust Get the HVTracker trust profile for a tracked AI agent or framework, including its runtime capability surface and the URL of its Ed25519-signed trust credential (verifiable offline). Input parameters: - `name_or_repo` (string, required) ### `compare_agents` (~58 tokens) Compare Agents Compare two tracked AI agents side by side: both trust profiles, an evidence-based one-line verdict, and the HVTracker compare-page URL when one is published. Input parameters: - `a` (string, required) - `b` (string, required) ### `search_agents` (~43 tokens) Search Agents Search tracked AI agents and frameworks by name, repo, or description. Input parameters: - `category` (string) - `limit` (integer) - `query` (string) ### `scan_stack` (~61 tokens) Scan Stack Bulk pre-connect trust check for a whole dependency set. Paste a requirements.txt, package.json, MCP client config, or a newline/comma list; each item is returned with a trust verdict plus a stack summary. Input parameters: - `input` (string, required) ### `list_categories` (~33 tokens) List Categories List HVTracker categories with agent counts (most-populated first), so you can then pull a category's leaderboard. ### `get_leaderboard` (~50 tokens) Get Leaderboard Top tracked AI agents and MCP servers by HVTrust score, optionally scoped to one category (exact name from list_categories). Input parameters: - `category` (string) - `limit` (integer) ### `get_agent_history` (~53 tokens) Get Agent History 90-day trust-score, grade, and rank history for one tracked agent — is it improving or declining? Accepts the same identifiers as check_agent_trust. Input parameters: - `name_or_repo` (string, required) ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp#diagnostics ## Score history - 2026-11-05: 46 - 2026-11-04: 46 - 2026-11-03: 51 - 2026-11-02: 51 - 2026-11-01: 51 - 2026-10-31: 51 - 2026-10-30: 51 - 2026-10-29: 51 - 2026-10-28: 51 - 2026-10-27: 50 - 2026-10-26: 50 - 2026-10-25: 49 - 2026-10-24: 49 - 2026-10-23: 48 - 2026-10-22: 48 - 2026-10-21: 47 - 2026-10-20: 47 - 2026-10-19: 46 - 2026-10-18: 46 - 2026-10-17: 46 - 2026-10-16: 45 - 2026-10-15: 9 - 2026-10-14: 9 - 2026-10-13: 9 - 2026-10-12: 9 - 2026-10-10: 9 - 2026-10-04: 37 - 2026-10-03: 37 - 2026-10-02: 37 - 2026-10-01: 37 ## Common questions ### What is the HVTracker MCP server? HVTracker MCP is listed in the public MCP registry as io.github.YugantM/hvtracker-mcp. Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry. This page covers its container image (ghcr.io/yugantm/hvtracker-mcp). ### Is the HVTracker MCP server safe to use? HVTracker MCP scores 46 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the HVTracker MCP server expose? HVTracker MCP exposes 8 tools: verify_mcp_server, check_agent_trust, compare_agents, search_agents, scan_stack, and 3 more. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded. ### Is the HVTracker MCP server still maintained? HVTracker MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the HVTracker MCP server under? HVTracker MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - GitHub Container Registry: https://ghcr.io/yugantm/hvtracker-mcp - Repository: https://github.com/YugantM/hvtracker-mcp - Changelog RSS feed: https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp.json - HTML version of this page: https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp