Skip to main content
Glama
vulnify

Vulnify MCP

Official
by vulnify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Vulnify MCP

No user-submitted related servers found.

    Related Servers

    • AgentShield

      shima78
      A
      license
      Not graded
      quality
      B
      maintenance
      Enforces configurable policies on AI agent tool calls, allowing, requesting review, or denying actions before they are executed.
      MIT

    • hejdar-mcp

      ARKALDA
      A
      license
      A
      quality
      C
      maintenance
      Runtime policy enforcement for AI agents. Evaluate every agent action against your organization's policies before execution, with observe and enforce modes.
      1
      1
      MIT

    • workflow-guard-mcp

      ultus-net
      A
      license
      A
      quality
      F
      maintenance
      Enables agentic coding clients to enforce portable policy guardrails by evaluating proposed shell, file write, git, and network actions and returning allow, deny, or ask decisions.
      2
      MIT

    • inkog

      inkog-io
      A
      license
      A
      quality
      B
      maintenance
      Security co-pilot for AI agents. Scans for vulnerabilities like prompt injection, infinite loops, and token bombing in AI Agents, audits MCP servers, verifies AGENTS.md governance, and generates EU AI Act compliance reports.
      10
      57 npm
      3
      Apache 2.0

    • abe

      flowinfosystems-index
      A
      license
      Not graded
      quality
      A
      maintenance
      A free, local check before your AI agent acts: every tool action is checked against your YAML rules and returns ACT, BLOCK or ESCALATE with an audit record. Optional: send escalations to Flow for a judgment.
      Apache 2.0
    • Vaikora Guard MCP by Data443

      Vaikora Guard MCPofficial

      Data443
      A
      license
      Not graded
      quality
      D
      maintenance
      Enforces deterministic policies on AI agent tool calls, evaluating actions against compliance modules (SOC 2, HIPAA, GDPR, etc.) and returning ALLOW, BLOCK, or CONSTRAIN decisions with an audit trail.
      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

    A4/5.0

    Scored across 7 tools

    Disambiguation3/5

    Several tools share the same underlying endpoint and near-identical semantics: check_action and test_policies both hit POST /v1/policies/test as dry-runs, and check_mcp_tool_call vs decide_action both record decisions (one keyed to MCP tool names, one to general actions). The descriptions do a good job cross-referencing each other to steer selection, but the boundaries are genuinely blurry in places.

    Naming Consistency4/5

    Names follow a mostly predictable verb_noun pattern (list_policies, test_policies, check_action, decide_action, get_decision). Minor deviations exist—plan_policy_changes uses a longer noun phrase and plural/singular usage is inconsistent (list_policies vs check_action)—but the convention is readable and consistent overall.

    Tool Count5/5

    Seven tools is well-scoped for a policy governance and decision-recording server. Each tool maps to a distinct capability (list, test, plan, check, decide, get) without redundancy that would bloat the surface.

    Completeness3/5

    The read/test/decide/get lifecycle is covered, but there are notable gaps: plan_policy_changes only produces a plan with no corresponding apply tool, and no tool can approve or deny a review (explicitly noted as out of scope). Agents hitting a REVIEW have no resolution path within this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources