proofrelay
Related Servers
Alternatives to proofrelay
- AlicenseAqualityDmaintenanceSafety layer for autonomous DeFi agents. Scans contracts for exploit patterns, simulates transactions, blocks honeypots.44 npm1MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables proof-carrying project execution through a read-only remote MCP endpoint and WebMCP tools for managing Project Passports, task graphs, evidence-backed provider comparisons, route approvals, artifacts, verification records, and checkpoints without executing external providers.MIT
- FlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools to list archived snapshots, retrieve methodology and proof bundles, and verify supplied evidence bundles.-
- AlicenseNot gradedqualityAmaintenanceProvides read-only MCP tools for market snapshots, position risk, order reconciliation, and daily report previews with deterministic financial calculations, evidence chains, and audit trails.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only Model Context Protocol server exposing LCP tools to an AI agent — verify before pay, compute an atrHash, extract and place references across ten commerce protocols.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceOffers proof-only tools to inspect and verify remediation closure receipts, deterministically confirming asset coverage, fixed artifact deployment, rescanning, deadline compliance, and zero-residual closure without executing scans or touching live systems.MIT

Trooth Networkofficial
AlicenseNot gradedqualityBmaintenanceRemote, read-only MCP connector to check any company's witnessed trust record on the Trooth Network, across identity, security, privacy, and AI practices. Also does a neutral read of a domain's public security surface and verifies signed Trust Ledger Tokens. No key, no account.MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct concern: discovery status, checkpoint recommendation, bundle verification, MCP risk scanning, and helper documentation. The descriptions cross-reference one another and specify exactly when each tool should be used, leaving little room for misselection.
All tool names follow a consistent lowercase snake_case verb_object pattern: get_verifier_status, recommend_checkpoint, verify_bundle, scan_mcp_risk, describe_cli_sdk_helper. The verbs and objects are specific and predictable, with no mixed conventions or vague generic names.
With exactly 5 tools, the server is well-scoped for a read-only advisory utility. Each tool earns its place by covering a separate step in the ProofRelay workflow without redundancy or unnecessary expansion.
For the server's declared read-only advisory purpose, the tool surface is complete: discovery status, checkpoint recommendation, bundle verification, MCP risk scanning, and integration guidance are all present. The descriptions clearly separate local checks from hosted verification, so there are no obvious dead ends within the intended scope.