verify_mcp_serverLABSCO SUMMARY
The question it answers comes before every other server you are considering.
scan_stack is the shape that matters: paste the dependency list or MCP client config you already have and get a verdict per entry, rather than checking things one at a time and giving up halfway. The 90-day history is the other half — a good score today on something that has been sliding for a month reads very differently.
What it is
A supply-chain trust lookup for AI agents, frameworks and MCP servers. It returns a pre-connect verdict for one item or for a whole dependency set, with trust profiles, side-by-side comparisons and 90-day score history behind it.
What you get
- verify_mcp_server gives a pre-connect trust verdict for an MCP server, package, GitHub repo or agent name
- check_agent_trust returns a tracked agent's profile — runtime capabilities, MCP status, providers, plugin surface, provenance drift — and the URL of its Ed25519-signed trust credential
- compare_agents puts two side by side with an evidence-based verdict and the published compare page
- search_agents searches the registry by name, repo, description or category
- scan_stack takes a requirements.txt, package.json, MCP client config or a plain list and returns a verdict per item plus a stack summary
- list_categories and get_leaderboard rank tracked agents and servers by HVTrust score, filterable to one category
- get_agent_history returns 90-day score, grade and rank history — whether something is improving or sliding
Requirements
Point a client at https://hvtracker.net/mcp with nothing installed, or use the local package: npm install -g hvtracker-mcp, python3 -m pip install hvtracker-mcp, or the published container image. No API key. It sends the identifier or search string you supply to hvtracker.net to fetch public trust data, and does not write to your system. HVTRACKER_BASE_URL points at a different instance.
Setup effort
One command — npm install -g hvtracker-mcp
USE CASES
01
Vetting a server before connecting to it
One verdict for a server, package, repo or agent name, before the config change.
02
Auditing a whole dependency set at once
Paste the file you already have and get a per-item verdict plus a summary for the stack.
03
Choosing between two agent frameworks
A side-by-side comparison with the evidence behind the verdict, plus each one's runtime profile.
04
Seeing whether something is getting better or worse
Score, grade and rank over 90 days rather than a single reading today.
05
Finding the well-regarded options in a category
Category counts first, then the ranked leaderboard within one of them.
8 tools
Listed in project docs. Your client may show a different list.
check_agent_trustcompare_agentssearch_agentsscan_stacklist_categoriesget_leaderboardget_agent_historyBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
npm
TERMINAL
npm install -g hvtracker-mcpHosted endpoint
ENDPOINT URL
https://hvtracker.net/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Any MCP client — Local Package
ANY MCP CLIENT — LOCAL PACKAGE · JSON
{
"mcpServers": {
"hvtracker": {
"command": "hvtracker-mcp"
}
}
}
