# HVTracker MCP (remote · hvtracker.net)

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

- Trust score: 67/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `hvtracker.net`: 67/100 (this document), [markdown](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker.md), [page](https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker)
- npm · `hvtracker-mcp`: 76/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:v0.3.0`: 37/100, [markdown](https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp-v0-3-0.md), [page](https://verifymcp.io/servers/yugantm-hvtracker-mcp/ghcr-io-yugantm-hvtracker-mcp-v0-3-0)
- pypi · `hvtracker-mcp`: 21/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

- Endpoint: `https://hvtracker.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 43/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 363 tokens (~45/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yugantm-hvtracker-mcp https://hvtracker.net/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yugantm-hvtracker-mcp --url https://hvtracker.net/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yugantm-hvtracker-mcp:
    url: "https://hvtracker.net/mcp"
```

### Other

```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 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-08-03 (score 67, +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.

### 2026-08-01 (score 66, +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.

### 2026-07-31 (score 65, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, +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.

### 2026-07-28 (score 58, +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.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (8)

### `check_agent_trust` (~35 tokens)

Check Agent Trust

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

Input parameters:

- `name_or_repo` (string, required)

Output parameters:

- `capabilities`
- `category`
- `coverage_grade`
- `credential_url`
- `evidence_grade`
- `has_provenance`
- `message`
- `name`
- `profile_url`
- `query` (string)
- `rank`
- `repo`
- `scorecard_score`
- `submit_url`
- `tracked` (boolean)
- `trust_score`

### `verify_mcp_server` (~43 tokens)

Verify MCP Server

Pre-connect trust verdict for an MCP server, package, GitHub repo, or agent name before connecting an AI agent to it.

Input parameters:

- `server` (string, required)

Output parameters:

- `confidence`
- `grade`
- `mcp_server_support`
- `reasons` (array)
- `resolved`
- `server` (string)
- `slug`
- `submit_url`
- `tool_permissions` (array)
- `tracked` (boolean)
- `trust_score`
- `trusted` (boolean)

### `compare_agents` (~45 tokens)

Compare Agents

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

Input parameters:

- `a` (string, required)
- `b` (string, required)

Output parameters:

- `a`
- `b`
- `compare_url`
- `verdict` (string)

### `search_agents` (~50 tokens)

Search Agents

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

Input parameters:

- `category` (string)
- `limit` (integer)
- `query` (string)

Output parameters:

- `count` (integer)
- `results` (array)

### `scan_stack` (~54 tokens)

Scan Stack

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.

Input parameters:

- `input` (string, required)

Output parameters:

- `results` (array)
- `summary`

### `list_categories` (~27 tokens)

List Categories

List the HVTracker categories with agent counts, so you can then pull a category's leaderboard.

Output parameters:

- `categories` (array)
- `count` (integer)

### `get_leaderboard` (~43 tokens)

Get Leaderboard

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

Input parameters:

- `category` (string)
- `limit` (integer)

Output parameters:

- `category`
- `count` (integer)
- `results` (array)

### `get_agent_history` (~40 tokens)

Get Agent History

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

Input parameters:

- `name_or_repo` (string, required)

Output parameters:

- `count` (integer)
- `history` (array)
- `message` (string)
- `name`
- `note` (string)
- `repo`
- `slug`
- `tracked` (boolean)
- `window_days` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://hvtracker.net/mcp
- Repository: https://github.com/YugantM/hvtracker-mcp
- Changelog RSS feed: https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yugantm-hvtracker-mcp/hvtracker