Achromat MCP server
OfficialRelated Servers
Alternatives to Achromat MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to execute tool calls with CCS runtime verification across six dimensions, ensuring fail-closed conformance before any action is executed.141 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to govern downstream tool servers by enforcing default-deny authority and attestation on every tool call, with live monitoring, approval, and mid-session revocation.3Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP-speaking agents to execute tool calls through an authorization gate, producing signed decision records and reconciled effect rows for accountability.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to route MCP tool calls through an inline policy proxy that enforces OWASP ASI safeguards, gates destructive or high-cost actions behind expiring HMAC-signed human approvals, and records tamper-evident Merkle audit receipts.MIT

Guwahofficial
AlicenseNot gradedqualityCmaintenanceEnforces local, fail-closed policy validation on MCP tool calls, blocking unauthorized or mutated agent payloads before they are dispatched.1Apache 2.0- AlicenseBqualityBmaintenanceEnforces consensus-hardened tool approval with HMAC-signed receipts, policy gates, and host-bound argument checks for MCP clients.1228 npmMIT
TDQS
Scored across 1 tool
With only one tool exposed there is no overlap risk, so selection is trivially unambiguous. However, the description references achromat_recall and achromat_calibrate as if they were sibling tools, which an agent may search for and not find, adding mild confusion.
The single name achromat_register_identity follows a clear namespace_verb_noun snake_case convention that would obviously extend to the other referenced tools (achromat_recall, achromat_calibrate). No inconsistent styles are present.
One tool is far too thin for a service whose own description implies at least three operations (register, recall, calibrate). Registration alone leaves the server nearly unusable, even if the remaining tools are dynamically unlocked later.
The surface covers only identity bootstrap; there is no way to recall information or calibrate, which are presented as the core capabilities. An agent can register an identity but has no follow-up operations, creating an immediate dead end.