Skip to main content
Glama
lixiaowww

veragent-mcp

by lixiaowww

Related Servers

Alternatives to veragent-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to query trust scores for MCP servers and agent skills while scanning content for potential security issues. It provides direct access to the Vigile trust registry to help users evaluate the safety of third-party tools and integrations.
      9
      23 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables checking whether MCP servers are alive, maintained, and safe to use by scoring metadata health and trust, scanning MCP config files, and optionally wrapping a server to log tool calls and errors locally.
      315 npm
      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
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides trust infrastructure for AI agents by enabling reputation lookup, website trust scanning, and identity verification via MCP tools.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server exposing AgentForge Trust Score audit tools. Query trust, evaluate policies, list trusted servers, recommend with filter.
      4
      8 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A continuous, out-of-band trust and reliability layer for the MCP ecosystem. It fingerprints MCP server tool definitions, detects and classifies drift (e.g., rug pulls) via a severity taxonomy, maintains a hash-chained evidence ledger, and gates CI with SARIF—while also acting as an MCP server itself so agents can check a server's safety before binding.
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: checking a single tool, listing trusted tools, and scanning a full stack. No overlap.

    Naming Consistency5/5

    All tool names follow the consistent verb_noun pattern with snake_case, making them predictable.

    Tool Count5/5

    Three tools is appropriate for a security verification server, covering individual check, listing, and stack scan without excess.

    Completeness4/5

    The tool surface covers the main verification operations, though a detailed audit or reporting tool could enhance completeness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues