HVTracker MCP Server

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

Remote serverstreamable-http

What is the HVTracker MCP MCP server?

Most developer tooling work still happens through a UI a human drives. HVTracker MCP MCP server moves it into the conversation instead. Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.

The short version

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

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 4 tools. What each one is for:

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

What it needs from you

Configuration is passed through the environment: HVTRACKER_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. HVTracker MCP's toolset — verify_mcp_server, check_agent_trust, compare_agents and 1 more — is a fair guide to whether it matches your workflow. It is maintained by YugantM; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against HVTracker MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
verify_mcp_serverpre-connect trust verdict for an MCP server, package, GitHub repo, or agent name.
check_agent_trusttrust 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_agentstwo agents side by side with an evidence-based verdict and the published compare-page link.
search_agentssearch the HVTracker registry by name, repo, description, or category.

How to install the HVTracker MCP MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
HVTRACKER_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use HVTracker MCP to verify mcp server.
  • Use HVTracker MCP to check agent trust.
  • Use HVTracker MCP to compare agents.

Frequently asked questions

It connects HVTracker MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (verify_mcp_server, check_agent_trust, compare_agents, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with HVTracker MCP directly.