macp-mcp
OfficialRelated Servers
Alternatives to macp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for verifying high-impact decisions with Trust OS.2MIT
- AlicenseNot gradedqualityCmaintenanceProvides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that acts as a temporal verification firewall, checking structured assumptions or diffs against immutable version receipts to return allow/block/abstain with cited evidence.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that evaluates agent actions against a Policy State Machine, emits a tamper-evident audit trail, and dispatches approved transitions to internal or federated handlers.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that puts a human approval gate in front of long-running autonomous processes, with tools for proposals, process control, logs, parameters, records, and optional EVM balance checks.MIT
- AlicenseAqualityCmaintenanceMCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access31MIT
TDQS
Scored across 8 tools
Each tool maps cleanly to a distinct step in the MACP decision protocol: session setup, proposing, optional evaluation, voting, committing, and retrieval/verification. The descriptions sharply distinguish the closely related read operations (get_session returns full state, get_commitment returns only the binding commitment, verify recomputes a hash).
All names are snake_case and use clear verb-based forms, with read operands prefixed by get_ (get_session, get_commitment) and actions as bare verbs (propose, evaluate, vote, commit). The mix of get_x and bare action verbs is a minor deviation from a single verb_noun pattern but remains readable and predictable.
Eight tools is well-scoped for a focused decision-session protocol, with each tool earning its place in the lifecycle. There is no bloat or missing obvious primitive that would make the set feel thin.
The surface covers the core decision lifecycle: session creation, proposal, evaluation, voting, commitment, state inspection, and hash verification. Minor gaps remain—no explicit join/leave, abort/cancel, or list-sessions operation—but these are not central to the stated protocol.