Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

HVTracker MCP

REMOTE · HVTRACKER.NET · 4 COMPONENTS · SCANNED AUG 3

Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.

+10 this week 67 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability43
  • AI-judged instruction clarity (poor).Fail
  • 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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · hvtracker.net

# add to Claude Code
claude mcp add --transport http yugantm-hvtracker-mcp https://hvtracker.net/mcp
# ~/.codex/config.toml
[mcp_servers.yugantm-hvtracker-mcp]
url = "https://hvtracker.net/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yugantm-hvtracker-mcp": {
      "type": "remote",
      "url": "https://hvtracker.net/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yugantm-hvtracker-mcp --url https://hvtracker.net/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  yugantm-hvtracker-mcp:
    url: "https://hvtracker.net/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • 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 56

    First indexed and scored.

Diagnostics

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 3 Aug 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 21 Jul 2026 19 Oct 2026 ECDSA 256 ECDSA-SHA384 5ba8ca21f08b6deb822dcbb45f48c3ee490
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
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=()
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
MCP tools — 8 exposed · ~337 tokens

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.

Tool Tokens
check_agent_trust ~35

Get the HVTracker supply-chain trust profile for a tracked AI agent or framework.

NameTypeReqDescription
name_or_repostringyes
NameTypeReqDescription
capabilities
category
coverage_grade
credential_url
evidence_grade
has_provenance
message
name
profile_url
querystringyes
rank
repo
scorecard_score
submit_url
trackedbooleanyes
trust_score

No examples provided.

compare_agents ~45

Compare two tracked AI agents side by side: trust scores, grades, runtime capabilities, and an evidence-based verdict.

NameTypeReqDescription
astringyes
bstringyes
NameTypeReqDescription
ayes
byes
compare_urlyes
verdictstringyes

No examples provided.

get_agent_history ~40

90-day trust-score, grade, and rank history for one tracked agent — is it improving or declining?

NameTypeReqDescription
name_or_repostringyes
NameTypeReqDescription
countinteger
historyarray
messagestring
name
notestring
repo
slug
trackedbooleanyes
window_daysinteger

No examples provided.

get_leaderboard ~43

Top tracked AI agents and MCP servers ranked by HVTrust score, optionally filtered to one category.

NameTypeReqDescription
categorystring
limitinteger
NameTypeReqDescription
categoryyes
countintegeryes
resultsarrayyes

No examples provided.

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.

NameTypeReqDescription
categoriesarrayyes
countintegeryes

No examples provided.

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.

NameTypeReqDescription
inputstringyes
NameTypeReqDescription
resultsarrayyes
summaryyes

No examples provided.

search_agents ~50

Search tracked AI agents and frameworks by name, repo, description, or category, ranked by trust score.

NameTypeReqDescription
categorystring
limitinteger
querystring
NameTypeReqDescription
countintegeryes
resultsarrayyes

No examples provided.

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.

NameTypeReqDescription
serverstringyes
NameTypeReqDescription
confidenceyes
gradeyes
mcp_server_supportyes
reasonsarrayyes
resolvedyes
serverstringyes
slug
submit_url
tool_permissionsarrayyes
trackedbooleanyes
trust_scoreyes
trustedbooleanyes

No examples provided.