sswp-mcp
Related Servers
Alternatives to sswp-mcp
- AlicenseAqualityBmaintenanceAI agent provenance, trust, and auditability layer. VERITAS multi-gate scoring, Cortex approval gates, S.E.A.L. hash-chain audit ledger, and semantic RAG with cryptographic provenance tracking for every decision an agent makes.275MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceA continuous, out-of-band trust and reliability layer for the MCP ecosystem. It fingerprints MCP server tool definitions, detects and classifies drift (e.g., rug pulls) via a severity taxonomy, maintains a hash-chained evidence ledger, and gates CI with SARIF—while also acting as an MCP server itself so agents can check a server's safety before binding.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceGovernance kernel for AI agents — policy enforcement, code safety verification, multi-model hallucination detection (CMVK), trust attestation (IATP), and immutable audit trails. Works with Claude Desktop, Cursor, and any MCP client.74MIT
- AlicenseAqualityCmaintenanceCryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.246 npm1MIT
- AlicenseBqualityAmaintenanceA governance proxy for AI tools — every MCP/agent tool call is policy-gated, secret-redacted, and written to a hash-chained, offline-verifiable audit trail.13MIT
- AlicenseCqualityAmaintenanceCommit-time audit engine for AI coding agents. Scans git diffs with 24 audit rules, writes HMAC-signed tamper-evident audit history, and ships MCP tools for governance aggregation.9544MIT
- FlicenseNot gradedqualityCmaintenanceCryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.-
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: single attestation, bulk attestation, verification, dependency analysis, pre-flight checking, registry health, ledger audit, and node search. Even the similar single vs. bulk witness tools are explicitly differentiated by scope.
All tools share the sswp_ prefix and snake_case, but base names mix conventions: verb-only (witness, verify), verb_noun (analyze_deps, check_repo), and noun forms (ledger, registry_health, node_search). The domain prefix keeps it readable, but there's no single verb_noun pattern.
8 tools is well-scoped for a supply-chain attestation workflow: single and bulk witnessing, verification, pre-check, dependency analysis, and three query/audit surfaces. No redundancy or bloat.
The lifecycle is well covered: witness, bulk witness, verify, pre-check, dependency analysis, registry health, ledger audit, and search. Minor gaps exist around registry lifecycle management (e.g., no explicit tool to update node status or remove a node), but core workflows are covered.