HVTracker MCP
NPM · HVTRACKER-MCP · 4 COMPONENTS
Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.
Last scanned (19 hours ago)
Scores higher than 94% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to YugantM/hvtracker-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 399 tokens (~49/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 −2
- Stability: pass → 0.90 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Package version: 0.3.0 → 0.4.0 functional
- 19 Oct 26 0
- Package version: 0.3.0 → 0.4.0 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −3
- Stability: pass → 0.83 functional
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 4 Nov 2026 · Analysed npm/hvtracker-mcp@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | YugantM/hvtracker-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/YugantM/hvtracker-mcp/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 3000220022 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a539a5734d372e3068c5cf2eda9d59e5ebee3d4767f29ec607e0dde374736d78f2d04224ec9de168f4fbfdbe19f342c61576a19c9906f108230487207 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~47
Get the HVTracker trust profile for a tracked AI agent or framework.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_repo | string | yes | Agent name, slug, GitHub repo, package, or MCP URL. |
No output schema declared.
No examples provided.
compare_agents Compare Agents ~75
Compare two tracked AI agents side by side: trust scores, grades, runtime capabilities, and an evidence-based verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | First agent — name, slug, GitHub repo/URL, or package. |
| b | string | yes | Second agent — name, slug, GitHub repo/URL, or package. |
No output schema declared.
No examples provided.
get_agent_history Get Agent History ~54
90-day trust-score, grade, and rank history for one tracked agent — is it improving or declining?
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_repo | string | yes | Agent name, slug, GitHub repo, package, or MCP URL. |
No output schema declared.
No examples provided.
get_leaderboard Get Leaderboard ~43
Top tracked AI agents and MCP servers ranked by HVTrust score, optionally filtered to one category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_categories List Categories ~27
List the HVTracker categories with agent counts, so you can then pull a category's leaderboard.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_stack Scan Stack ~67
Bulk pre-connect trust check for a whole dependency set — paste a requirements.txt, package.json, MCP client config, or list and get a verdict per item plus a stack summary.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | A requirements.txt, package.json, MCP client config, or newline/comma list. |
No output schema declared.
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 | – | – |
No output schema declared.
No examples provided.
verify_mcp_server Verify MCP Server ~43
Pre-connect trust verdict for an MCP server or AI agent.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | GitHub repo, package, display name, slug, or MCP URL. |
No output schema declared.
No examples provided.
How do I install the HVTracker MCP server?
HVTracker MCP runs locally as an npm package, launched with npx -y hvtracker-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · hvtracker-mcp
claude mcp add yugantm-hvtracker-mcp -- npx -y hvtracker-mcp
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 npm package (hvtracker-mcp).
Is the HVTracker MCP server safe to use?
HVTracker MCP scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 399 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 4 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.