Skip to main content
Glama
aygp-dr

liquidus-005

by aygp-dr

Related Servers

Alternatives to liquidus-005

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An 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.
      14
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      An 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.
      30
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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
    • A
      license
      A
      quality
      D
      maintenance
      A 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.
      5
      69 npm
      MIT

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource (order, product, products, taxonomies) with no overlap. The operations are clearly differentiated: single retrieval vs. listing.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: get_ for single entities and list_ for collections. The naming is predictable and uniform.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues