HVTracker MCP
REMOTE · HVTRACKER.NET · 4 COMPONENTS · SCANNED SEP 20
Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 363 tokens (~45/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the HVTracker MCP server?
HVTracker MCP is a hosted endpoint at https://hvtracker.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hvtracker.net
claude mcp add --transport http yugantm-hvtracker-mcp 'https://hvtracker.net/mcp'
{
"mcpServers": {
"yugantm-hvtracker-mcp": {
"url": "https://hvtracker.net/mcp"
}
}
} {
"servers": {
"yugantm-hvtracker-mcp": {
"type": "http",
"url": "https://hvtracker.net/mcp"
}
}
} [mcp_servers.yugantm-hvtracker-mcp] url = "https://hvtracker.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yugantm-hvtracker-mcp": {
"type": "remote",
"url": "https://hvtracker.net/mcp",
"enabled": true
}
}
} openclaw mcp add yugantm-hvtracker-mcp --url 'https://hvtracker.net/mcp' --transport streamable-http
mcp_servers:
yugantm-hvtracker-mcp:
url: "https://hvtracker.net/mcp" {
"McpServers": {
"yugantm-hvtracker-mcp": {
"Transport": "http",
"Url": "https://hvtracker.net/mcp"
}
}
} assistant mcp add yugantm-hvtracker-mcp -t streamable-http -u 'https://hvtracker.net/mcp'
{
"mcpServers": {
"yugantm-hvtracker-mcp": {
"type": "http",
"url": "https://hvtracker.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://hvtracker.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hvtracker.net | CN=YE2,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 697e3356eb86a131f5fd17e779d39bd8157 |
| SANs: *.hvtracker.net, hvtracker.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hvtracker.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| hvtracker.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hvtracker.net/mcp | Verified | 200 | |
| http (plaintext) | http://hvtracker.net/mcp | HTTPS enforced | 301 | https://hvtracker.net/mcp |
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 ~35
Get the HVTracker supply-chain trust profile for a tracked AI agent or framework.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_repo | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | – | – | – |
| category | – | – | – |
| coverage_grade | – | – | – |
| credential_url | – | – | – |
| evidence_grade | – | – | – |
| has_provenance | – | – | – |
| message | – | – | – |
| name | – | – | – |
| profile_url | – | – | – |
| query | string | yes | – |
| rank | – | – | – |
| repo | – | – | – |
| scorecard_score | – | – | – |
| submit_url | – | – | – |
| tracked | boolean | yes | – |
| trust_score | – | – | – |
No examples provided.
compare_agents Compare Agents ~45
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 | – |
| b | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| a | – | yes | – |
| b | – | yes | – |
| compare_url | – | yes | – |
| verdict | string | yes | – |
No examples provided.
get_agent_history Get Agent History ~40
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 | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| history | array | – | – |
| message | string | – | – |
| name | – | – | – |
| note | string | – | – |
| repo | – | – | – |
| slug | – | – | – |
| tracked | boolean | yes | – |
| window_days | integer | – | – |
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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | yes | – |
| count | integer | yes | – |
| results | array | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| count | integer | yes | – |
No examples provided.
scan_stack Scan Stack ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| summary | – | yes | – |
No examples provided.
search_agents Search Agents ~50
Search tracked AI agents and frameworks by name, repo, description, or category, ranked by trust score.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| results | array | yes | – |
No examples provided.
verify_mcp_server Verify MCP Server ~43
Pre-connect trust verdict for an MCP server, package, GitHub repo, or agent name before connecting an AI agent to it.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | – | yes | – |
| grade | – | yes | – |
| mcp_server_support | – | yes | – |
| reasons | array | yes | – |
| resolved | – | yes | – |
| server | string | yes | – |
| slug | – | – | – |
| submit_url | – | – | – |
| tool_permissions | array | yes | – |
| tracked | boolean | yes | – |
| trust_score | – | yes | – |
| trusted | boolean | yes | – |
No examples provided.
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 hosted endpoint (https://hvtracker.net/mcp).
Is the HVTracker MCP server safe to use?
HVTracker MCP scores 84 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: check_agent_trust, verify_mcp_server, compare_agents, search_agents, scan_stack, and 3 more. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Does the HVTracker MCP server require authentication?
No. We connected to HVTracker MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HVTracker MCP server still maintained?
HVTracker MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.