HVTracker MCP
OCI · GHCR.IO/YUGANTM/HVTRACKER-MCP · 4 COMPONENTS
Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.
Last scanned (8 hours ago)
Scores higher than 65% of OCI servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 450 tokens (~56/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/yugantm/hvtracker-mcp@v0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent_trust Check Agent Trust ~58
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).
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_agents Compare Agents ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | – |
| b | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_agent_history Get Agent History ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_leaderboard Get Leaderboard ~50
Top tracked AI agents and MCP servers by HVTrust score, optionally scoped to one category (exact name from list_categories).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_categories List Categories ~33
List HVTracker categories with agent counts (most-populated first), so you can then pull a category's leaderboard.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
scan_stack Scan Stack ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_agents Search Agents ~43
Search tracked AI agents and frameworks by name, repo, or description.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_mcp_server Verify MCP Server ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
oci · ghcr.io/yugantm/hvtracker-mcp
claude mcp add yugantm-hvtracker-mcp -- docker run --rm -i ghcr.io/yugantm/hvtracker-mcp:v0.4.0
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.