Skip to main content
Glama
io.github.yugantm/hvtracker-mcp

io.github.yugantm/hvtracker-mcp

HVTracker MCP

Smithery npm PyPI License: MIT

MCP server for checking supply-chain trust before connecting to AI agents, frameworks, or MCP servers.

The hosted remote server is:

{
  "mcpServers": {
    "hvtracker": {
      "url": "https://hvtracker.net/mcp"
    }
  }
}

This repository also provides a local stdio package for clients that prefer package-based installation.

Tools

  • verify_mcp_server: pre-connect trust verdict for an MCP server, package, GitHub repo, or agent name.

  • check_agent_trust: trust profile for a tracked AI agent or framework — incl. runtime capabilities (MCP status, providers, plugin surface, provenance drift) and the URL of its Ed25519-signed trust credential.

  • compare_agents: two agents side by side with an evidence-based verdict and the published compare-page link.

  • search_agents: search the HVTracker registry by name, repo, description, or category.

  • 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.

  • list_categories: list the HVTracker categories with agent counts, so you can then pull a category's leaderboard.

  • get_leaderboard: top tracked AI agents and MCP servers ranked by HVTrust score, optionally filtered to one category.

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

Related MCP server: Agent Identity MCP Server

Check your AI dependencies in CI

HVTrust Gate runs the same trust checks in GitHub Actions. With no configuration it reads your requirements.txt, pyproject.toml, package.json and MCP client configs, and comments on pull requests that change them with the HVTrust grade of each AI agent and MCP server you depend on.

name: HVTrust
on: [pull_request]
permissions:
  contents: read
  pull-requests: write
jobs:
  trust:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: YugantM/hvtrust-gate@v1

Local Install

With npm:

npm install -g hvtracker-mcp

With PyPI:

python3 -m pip install hvtracker-mcp

Example MCP client config:

{
  "mcpServers": {
    "hvtracker": {
      "command": "hvtracker-mcp"
    }
  }
}

Development

python3 -m pip install -e ".[dev]"
python3 -m pytest
hvtracker-mcp

Use a different HVTracker base URL while testing:

HVTRACKER_BASE_URL=http://localhost:8080 hvtracker-mcp

Registry Publishing

The official MCP Registry manifest is server.json.

mcp-publisher login github
mcp-publisher publish

In GitHub Actions, run the "Publish MCP Registry" workflow after the npm, PyPI, and GHCR packages for the same version are live.

The server name is:

io.github.YugantM/hvtracker-mcp

Claude Desktop Extension

Tagged releases build an .mcpb bundle for Claude Desktop from manifest.json. To build it locally:

npm ci --omit=dev
npx @anthropic-ai/mcpb@2.1.2 pack

Privacy

HVTracker MCP sends the user-supplied search string or server identifier to https://hvtracker.net to fetch public trust data. It does not require an API key and does not write to user systems. See the HVTracker site for current data and methodology, and see PRIVACY.md for the repository privacy note.

Available Tools

8 tools
check_agent_trustCheck Agent TrustB
Read-onlyIdempotent
Inspect

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).

Inputs: name_or_repo (required). Returns: object

compare_agentsCompare AgentsA
Read-onlyIdempotent
Inspect

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.

Inputs: a (required), b (required). Returns: object

get_agent_historyGet Agent HistoryA
Read-onlyIdempotent
Inspect

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.

Inputs: name_or_repo (required). Returns: object

get_leaderboardGet LeaderboardA
Read-onlyIdempotent
Inspect

Top tracked AI agents and MCP servers by HVTrust score, optionally scoped to one category (exact name from list_categories).

Inputs: limit, category. Returns: object

list_categoriesList CategoriesA
Read-onlyIdempotent
Inspect

List HVTracker categories with agent counts (most-populated first), so you can then pull a category's leaderboard.

Inputs: no named parameters. Returns: object

scan_stackScan StackA
Read-onlyIdempotent
Inspect

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.

Inputs: input (required). Returns: object

search_agentsSearch AgentsA
Read-onlyIdempotent
Inspect

Search tracked AI agents and frameworks by name, repo, or description.

Inputs: limit, query, category. Returns: object

verify_mcp_serverVerify MCP ServerA
Read-onlyIdempotent
Inspect

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.

Inputs: server (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes, but check_agent_trust and verify_mcp_server both provide trust verdicts for agents/servers, potentially causing confusion. Descriptions help differentiate, but overlap remains.

    Naming Consistency5/5

    All tool names consistently follow a verb_noun pattern in snake_case, such as check_agent_trust, compare_agents, and list_categories.

    Tool Count5/5

    With 8 tools, the server covers core querying needs without being cluttered. Each tool serves a clear function, and the count feels appropriate for a trust tracker.

    Completeness4/5

    The set covers trust checks, comparison, history, leaderboard, categories, bulk scanning, search, and MCP verification. Minor gaps exist, such as no individual category detail tool, but overall coverage is solid.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
      8
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent trust verification, enabling agents to verify identities, check trust scores, and build reputation across multiple blockchain and web platforms.
      12
      20 npm
      1
      MIT