ComputeLedger MCP Server
Related Servers
Alternatives to ComputeLedger MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenancePrivacy-first, tamper-evident receipts for MCP tool calls. It hashes and signs arguments/results so you can verify what ran, when, without storing raw payloads.2MIT
- AlicenseAqualityCmaintenanceCryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.246 npm1MIT
- AlicenseAqualityAmaintenanceProvides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.435 npm1MIT
- AlicenseAqualityAmaintenanceRecords privacy-preserving receipts for AI-assisted tasks and enables optional onchain reward claiming via AIPOU tokens. Integrates with MCP-compatible clients like Claude and Cursor.114MIT
- AlicenseAqualityDmaintenanceTamper-evident audit logging for AI decisions. Three tools (record_decision, verify_decision, list_decisions) write to a regulator-grade ledger built on AWS S3 Object Lock with 7-year retention. Designed for EU AI Act Article 12 and FCA SS1/23 evidence requirements. Try zero-config: npx audit-ledger-mcp boots in sandbox mode against a public hosted tenant.332 npm1Apache 2.0
- AlicenseAqualityCmaintenanceUniversal MCP server that emits Context Passport records for AI agent decisions and actions. Drop into any MCP-compatible client to give your agent a commit/verify/replay/export toolset for verifiable, tamper-evident records.568 npmApache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: record_usage creates a new receipt, verify_receipt checks a single receipt, list_ledger lists all receipts, and verify_ledger audits the entire chain. Descriptions explicitly cross-reference when to use which, leaving no ambiguity.
All four tool names follow the same verb_noun pattern: record_usage, verify_receipt, list_ledger, verify_ledger. The verbs (record, verify, list, verify) and nouns (usage, receipt, ledger) are consistently used and intuitive.
Four tools is ideal for a focused compute-ledger server: one for creating records, one for verifying individual receipts, one for listing history, and one for full-chain audit. There is no bloat or redundancy; each tool earns its place.
The tool set covers the entire lifecycle of compute-usage receipts: recording, single-receipt verification, listing, and whole-ledger integrity verification. The only missing piece (key generation) is handled externally via CLI, which is outside the server's scope, so the MCP surface is complete.