DJZS Trust MCP vs HVTracker MCP
A side-by-side look at the DJZS Trust MCP and HVTracker MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DJZS Trust MCP for security work over a hosted endpoint; choose HVTracker MCP for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DJZS Trust MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
query_pol_certificates, query_agent_trust, verify_pm_trade.
Choose HVTracker MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
verify_mcp_server, check_agent_trust, compare_agents.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 57/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 4 | 8 |
| Full listing | View DJZS Trust MCP | View HVTracker MCP |
Tools & capabilities
DJZS Trust MCP tools 4
query_pol_certificatesQuery immutable ProofOfLogic certificates stored on Irys Datachain by DJZS Protocol. USE THIS TOOL when you need to verify audit history for an agent or project before delegating work, check FAIL verdicts, or retrieve certificates by Irys tx ID. DO NOT use for on-chain trust scores — use query_agent_trust for those.query_agent_trustQuery an agent's DJZS trust score, aggregated on-chain (Base mainnet) from its audit history and indexed via the DJZS subgraph. USE BEFORE delegating work, releasing escrow, or executing agent transactions. Returns scored_audits, pass/fail counts, the raw fail rate, and a Wilson 95% lower bound on it, plus latest verdict/risk and DJZS-S01/DJZS-X01 flag counts. WAIT verdicts are abstentions: they are excluded from BOTH the numerator and the denominator of the fail rate and are reported separately as wait_count. Below 10 scored audits the tool returns INSUFFICIENT_HISTORY and NO rate - a 0-of-0 record is not evidence of reliability and must not compare as better than a 3-of-50. This tool returns evidence, not a decision: it applies no threshold and emits no HALT. Interpreting the bound against your own risk tolerance is the caller's job.verify_pm_tradeDeterministic pre-execution audit of a prediction-market trade thesis, run before capital is committed. USE THIS TOOL before opening, sizing, or increasing any prediction-market position, and whenever a user or an upstream agent asks whether a thesis is sound, carries a falsification condition, or has a sourced probability basis. Audits against the calibrated DJZS-M taxonomy (M01 narrative/resolution gap, M02 falsification absent, M03 probability unsourced, M04 consensus-as-edge advisory) and returns PASS->PROCEED, WAIT->HALT, or FAIL with the flagged defects and a reproducible verdict_hash. DO NOT use to retrieve past verdicts or certificates - use query_pol_certificates for those. DO NOT use for an agent's historical trust score - use query_agent_trust for that. DO NOT use for spot, perpetuals, or equities: out-of-scope submissions are refused WITHOUT CHARGE. Audit before act. Paid tool: 2 USDC per audit via x402 on Base.verify_perp_tradeDeterministic pre-execution audit of a perpetual or spot TRADE thesis (direction, size, leverage, entry, stop, target, venue, and the REASON), run before capital is committed. USE THIS TOOL before opening, sizing, or increasing any perpetual or spot position. Returns PASS / WAIT / FAIL with a reproducible verdict hash. A position stated with no thesis FAILS (DJZS-S01); an unbounded position FAILS (DJZS-X01); an unresolvable stop or thesis WAITs. Prediction-market bets are refused here (use verify_pm_trade) and are not charged. Price 2.00 USDC per audit on Base.
HVTracker MCP tools 8
verify_mcp_serverPre-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.check_agent_trustGet 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).compare_agentsCompare 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.search_agentsSearch tracked AI agents and frameworks by name, repo, or description.scan_stackBulk 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.list_categoriesList HVTracker categories with agent counts (most-populated first), so you can then pull a category's leaderboard.get_leaderboardTop tracked AI agents and MCP servers by HVTrust score, optionally scoped to one category (exact name from list_categories).get_agent_history90-day trust-score, grade, and rank history for one tracked agent — is it improving or declining? Accepts the same identifiers as check_agent_trust.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
DJZS Trust MCP
{
"mcpServers": {
"djzs-trust-mcp": {
"url": "https://mcp.djzs.ai/mcp"
}
}
}
HVTracker MCP
{
"mcpServers": {
"hvtracker-mcp": {
"command": "uvx",
"args": [
"hvtracker-mcp"
]
}
}
}
Frequently asked questions
DJZS Trust MCP is categorized under Security and uses a remote HTTP/SSE transport. HVTracker MCP belongs to Security and uses a local stdio subprocess. Pick DJZS Trust MCP for security work and HVTracker MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
DJZS Trust MCP has no declared pricing — check the project's own site. HVTracker MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add djzs-trust-mcp and hvtracker-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DJZS Trust MCP has a quality signal of 57/100 (Good) with 1 views, 0 installs and 3 GitHub stars. HVTracker MCP has 60/100 (Good) with 4 views, 0 installs and 1 GitHub stars.