Skip to main content
Glama
jagmarques

asqav-mcp

by jagmarques
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to asqav-mcp

No user-submitted related servers found.

    Related Servers

    • dingdawg-governance

      dingdawg
      A
      license
      A
      quality
      D
      maintenance
      Universal governance layer for AI agents — MCP-native, fail-closed, LNN interpretability. Governed receipts, IPFS audit proofs, and rollback for any agent in any framework.
      3
      79 npm
      Apache 2.0

    • VaultMind

      ik123a
      A
      license
      Not graded
      quality
      B
      maintenance
      Offline-first MCP proxy with policy engine and immutable audit trail for secure AI coding agents.
      2
      MIT

    • attestix

      VibeTensor
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for compliance automation of AI agents, enabling EU AI Act compliance, verifiable credentials, and decentralized identity management with 47 tools across 9 modules.
      329 PyPI
      874
      Apache 2.0

    • sigmodx-mcp

      Sigmodx
      A
      license
      A
      quality
      D
      maintenance
      Audit infrastructure for AI agents to log consequential decisions (invoice, GL, anomaly) and verify attestations via MCP tools.
      6
      MIT
    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

    A3.5/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes, but verify_output and verify_signature are closely related, though their descriptions differentiate them (output hash vs. general signature). check_policy and preflight_check also overlap slightly, but preflight_check adds agent status checking.

    Naming Consistency3/5

    The majority of tools follow a verb_noun pattern (e.g., check_policy, create_tool_policy, list_agents), but exceptions like enforced_tool_call (adjective_noun_noun) and gate_action (noun_noun) break the pattern. The naming is readable but not perfectly consistent.

    Tool Count5/5

    15 tools cover policy management, enforcement, scanning, signing, and verification without feeling bloated. Each tool serves a specific function in the security workflow.

    Completeness4/5

    The tool set provides CRUD for policies (via upsert create), gating, enforcement, scanning, and verification. Minor gaps exist, such as no explicit agent creation/removal tools, but the core security audit workflow is well-covered.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources