Skip to main content
Glama
Rul1an

assay-mcp-server

by Rul1an
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to assay-mcp-server

No user-submitted related servers found.

    Related Servers

    • WhitePact

      Guruprasath-Annadurai
      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

    • iris-eval/mcp-server

      iris-eval
      A
      license
      A
      quality
      A
      maintenance
      MCP-native agent evaluation and observability server. Log traces, evaluate output quality with 12 built-in rules (PII detection, prompt injection, cost thresholds), and track agent costs. Real-time dashboard, OTel-compatible spans. Self-hosted, MIT licensed.
      9
      1,358 npm
      9
      MIT

    • @palveron/mcp-server

      palveron
      A
      license
      A
      quality
      A
      maintenance
      Provides advisory AI-governance checks for MCP hosts and coding agents, enabling policy verdicts, PII masking, and audit traces before executing tool calls.
      3
      44 npm
      MIT

    • governed-mcp

      rsiraj0
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enforces governance on agentic decisions with auditable evidence records, providing tools for understanding, calibrating confidence, and navigating handoffs based on policy.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of policy analysis: argument validation, coverage, sequence validation, trace explanation, and policy decision. No overlap in purpose.

    Naming Consistency5/5

    All tools follow the consistent pattern 'assay_<verb>_<noun>', using snake_case throughout. The prefix 'assay_' unifies the set.

    Tool Count5/5

    Five tools is a well-scoped set for a policy analysis server. Each tool serves a clear role without redundancy, covering the core operations.

    Completeness4/5

    The tools cover essential policy checking operations (validate args, check coverage, sequence validation, explain traces, decide policy). Missing a tool to list or retrieve policies, but the set is otherwise solid for its domain.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources