Skip to main content
Glama

Related Servers

Alternatives to Verity MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      HallucC — an MCP server for hallucination detection and AI agent safety. Claim-by-claim fact-checking of LLM/agent output with cited sources, a prompt-injection & jailbreak guard, and L0–L3 risk gating for computer-use (CUA) agent actions. 5 tools, 3 free checks/day, works with Claude Code, Cursor and Claude Desktop.
      8
      4
      41 npm
      MIT
    • 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
      59 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables trust, reputation, and economic accountability for MCP by proxying between clients and servers, enriching every tool invocation with trust evaluation, KYA tiers, spending limits, and delegation chains.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server lets agents inspect every Model Context Protocol server on the machine, verify tools by running them in a sandbox, and check each call against a human-approved baseline so that changed or newly appeared tools are blocked before they execute. It also surfaces token cost, capability facts, and drift history for each tool entirely locally, without uploading inventory or requiring an account.
      1,065 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that gates agent tool calls by normalizing intent, denying unknown/unattended destructive actions, and requiring HITL prove approval for high-risk operations. It maintains an append-only hash-chained Action Ledger and exposes gate_check and ledger_verify tools without ever executing tools.
      MIT

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    The three verify tools (quick_verify, grounded_verify, pro_verify) are intentionally similar but clearly differentiated by pricing, grounding, and model tier, so an agent can choose based on stakes. verify_receipt, detect_injection, moderate_content, redact_pii, and guard_action each target distinct safety concerns with little overlap.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (verify_receipt, detect_injection, moderate_content, redact_pii, guard_action). The verify tier breaks the pattern by putting the adjective before the verb (quick_verify, grounded_verify, pro_verify), which is a minor deviation but still readable and predictable within its own subgroup.

    Tool Count5/5

    Eight tools is well-scoped for a safety/verification server. Each tool serves a distinct purpose—claim verification at three tiers, receipt checking, injection detection, content moderation, PII redaction, and action gating—without unnecessary bloat or missing essentials.

    Completeness5/5

    The set covers the full lifecycle of agent safety: verifying claims before use, detecting prompt injection on input, moderating output content, redacting sensitive data, and gating irreversible actions. The receipt verification tool closes the loop for auditability, and no obvious gap is apparent for the stated domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues