Public layer
- Free leaderboard browsing
- Public JSON snapshot
- Open methodology and specs
- Read-only REST API (v1)
Commercial access
- Higher-rate data access
- Historical exports and change feeds
- Watchlists, alerts, and shared team usage
REST API v1
Two read-only endpoints are available now, no auth required. CORS-enabled for browser use.
GET /api/v1/agents
Full agent leaderboard with trust scores, evidence grades, and metadata.
curl -s https://hvtracker.net/api/v1/agents | python -m json.tool | head
GET /api/v1/graph
Dependency and ecosystem graph data for all tracked agents.
curl -s https://hvtracker.net/api/v1/graph | python -m json.tool | head
POST /api/v1/scan
Bulk trust check for a whole dependency set — paste a requirements.txt, package.json, or MCP config and get a verdict per item. Powers the Scan your stack tool.
curl -s https://hvtracker.net/api/v1/scan -H 'Content-Type: application/json' -d '{"input": "langchain
crewai
autogen"}' | python -m json.tool
GET /api/v1/mcp/verify?server=<repo|url|npm|pypi>
Pre-connect trust verdict for an MCP server — a signed attestation when the server is tracked, an explicit "not tracked, unverified" verdict when it isn't. Spec: MCP Server Trust v0.1.
curl -s 'https://hvtracker.net/api/v1/mcp/verify?server=deepset-ai/haystack' | python -m json.tool
GET /data/agents/<slug>.json · GET /data/latest.json
Per-agent record with the full signal set and an Ed25519-signed trust_credential (verify it offline — see verify a score yourself), and the full-registry snapshot. Machine discovery starts at /.well-known/hvtracker.json.
GET /api/v1/agents/<slug>/history
An agent's public trust fields over the last 90 days, one entry per daily snapshot (rank, HVTrust, grades, provenance, Scorecard, downloads, stars). Beyond 90 days, use the quarterly dataset export below; deeper continuous history is reserved for a future tier.
curl -s https://hvtracker.net/api/v1/agents/haystack/history | python -m json.tool | head
Stability promise: within v1, fields are add-only — existing fields are never renamed or removed; breaking changes ship under a new path version. Data license: CC BY 4.0, attribution "HVTracker (hvtracker.net)". Auth and rate quotas for a paid tier are intentionally out of scope for now.
Quarterly dataset export
A citable, versioned snapshot of every public field for research and press — refreshed through the quarter, frozen when the quarter ends. CC BY 4.0; attribution: "HVTracker (hvtracker.net)".
curl -sO https://hvtracker.net/data/exports/hvtrust-2026-Q4.json.gz
curl -sO https://hvtracker.net/data/exports/hvtrust-2026-Q4.csv
Filename pattern: hvtrust-<year>-Q<n>. Past quarters stay at their end-of-quarter state.
Ended quarters are archived on Zenodo with a DOI, so a citation always points at a fixed copy: 2026-Q3 is doi:10.5281/zenodo.23084548 (every quarter: 10.5281/zenodo.23084547). Agents and skills are ranked on separate boards, each from 1; the listing_class column says which (the archived 2026-Q3 copy adds it).
MCP registry feed
The official MCP Registry entries for every server we score, served as a v0.1 registry with HVTrust in _meta, plus Grade A, B and C allowlists for GitHub Copilot's Registry only policy. Base URLs and setup →
MCP server — trust layer for agents
Add HVTracker as a Model Context Protocol server so a coding agent can check supply-chain trust before installing a dependency or connecting to an MCP server. Streamable HTTP, no auth, no install.
{
"mcpServers": {
"hvtracker": { "url": "https://hvtracker.net/mcp" }
}
}
Tools: verify_mcp_server (pre-connect "Safe Browsing for MCP" verdict), check_agent_trust (incl. runtime capabilities + signed-credential URL), scan_stack (verdict for a whole requirements.txt / package.json / mcp config), compare_agents, get_leaderboard, list_categories, get_agent_history (90-day trust trend), search_agents.
Early pricing stub
Public registry
Leaderboard, agent profiles, compare pages, methodology, and the public JSON layer.
Builder
Email alerts, small watchlists, expanded exports, and early access to new comparison workflows.
Team
Shared watchlists, deeper history, bulk exports, and commercial usage support.
Request API or data access
If you want to use HVTracker data commercially, tell me how. The point of this page is to validate which export shapes and usage rights are worth productizing first.