liquidus-005
Related Servers
Alternatives to liquidus-005
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityDmaintenanceAn MCP server that exposes tools for issuing scoped agent credentials, delegating narrower child credentials, handling approvals, revoking task trees, and retrieving audit trails and evidence packets.141Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.301MIT
- AlicenseNot gradedqualityCmaintenanceMCP server wrapping the fallclaim-us SDK for sovereign, MIT-licensed, Ed25519 signed professional-service workflow automation.MIT
- AlicenseNot gradedqualityBmaintenanceMCP 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
- AlicenseAqualityDmaintenanceA thin MCP server that wraps provenance-receipts and quality-gate services as tools, enabling AI agents to certify content origin and score quality via Ed25519-signed receipts.569 npmMIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource (order, product, products, taxonomies) with no overlap. The operations are clearly differentiated: single retrieval vs. listing.
All tools follow a consistent verb_noun pattern: get_ for single entities and list_ for collections. The naming is predictable and uniform.
With 4 tools, the server is minimally scoped. While it could be sufficient for a read-only browsing service, it feels thin for a typical e-commerce server and may leave agents wanting more functionality.
The server covers only retrieval operations for products, orders, and taxonomies. Missing common actions like listing orders, creating or updating products, or managing carts, which are significant gaps for a storefront API.