signafaide
OfficialRelated Servers
Alternatives to signafaide
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceTamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.329 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables capturing a tamper-evident, hash-chained local record of every AI agent tool call — both the decision before a tool runs and its outcome — so you can review what the agent actually did in order, detect edits, deletions, or reordering at the exact index, and export a signed evidence pack any third party can verify with no installs.2MIT
- AlicenseNot gradedqualityBmaintenanceTamper-evident recorder for AI agent tool calls. Every MCP call is written to a hash-chained, signed log the agent cannot edit, delete or hide; anyone can verify the chain offline.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceCaptures AI agent runs and turns them into tamper-evident execution records showing tool use, timing, failures, recoveries, and human interventions. Records can be inspected, exported, and verified offline.MIT
- AlicenseAqualityBmaintenanceEnables AI agents and their hosts to record actions, tool calls, and human approvals in an append-only, hash-chained log; verify tamper evidence; mask secrets; retrieve recent events; and export audit-ready JSON or CSV on self-hosted infrastructure.4192 PyPIApache 2.0
- AlicenseNot gradedqualityCmaintenanceTamper-evident audit logging for AI agents. Append-only, hash-chained, optionally Ed25519-signed log. The MCP server lets an agent keep and verify a record of what it actually did.8MIT
TDQS
Scored across 7 tools
signafaide_setup and signafaide_quickstart overlap heavily: both return an install command plus framework-specific integration code, differing mainly in that setup also detects the stack and previews actions. The claim link is surfaced by three tools (claim_link, status, and init's return), creating further boundary blur. init vs setup is at least clarified by descriptions (init is the real side-effecting call, setup is a read-only preview).
Every tool uses the signafaide_ prefix with snake_case, which is predictable and easy to scan. Minor deviation: some names are verbs (verify, setup, init) while others are nouns (status, claim_link), but the meaning stays clear.
Seven tools is well-matched to the scope: preview, initialize, quickstart, status, claim link, verify, and error explanation. Nothing feels padded, and no obvious operation is crammed into an overloaded tool.
The lifecycle of onboarding and verification is covered, but there is no tool to read, list, or search the actual recorded events, and no explicit way to ship pending outbox records (it happens implicitly inside verify). Rekey/rotate, unclaim/revoke, and cleanup of local .signafaide state are also absent, leaving a few dead ends.