Skip to main content
Glama
Sign In
rolefence-scan

rolefence-scan

by vtsol-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to rolefence-scan

No user-submitted related servers found.

    Related Servers

    • Palanit Core

      stasxr
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an agent or MCP client to scan MCP server configs and AI-agent tool manifests on demand, exposing tools that list detection rules and report hidden prompt injections, data-exfiltration attempts, embedded secrets, deceptive Unicode, unpinned packages and shell-launching tools. Each finding comes with a severity and location so risky tool descriptions can be caught before an attacker exploits them.
      64 PyPI
      Apache 2.0

    • agent-crashtest

      glibey
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.
      78 npm
      MIT

    • DB MCP Gateway

      mdadul
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to databases for MCP-compatible AI tools, allowing schema exploration and SELECT queries without exposing credentials or risking data changes.
      84 npm
      3
      MIT

    • FSV

      twayst0
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to perform authorized web security assessments through MCP tools and a guided review prompt, including passive and full scans, WAF detection, remediation fixes, report export, triage, scan comparison, and proof-of-control verification.
      12
      139 PyPI
      5
      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.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    The two scan tools target clearly different surfaces: scan_mcp covers remote MCP endpoints/backends and scan_local_program covers local stdio server configs, so an agent can pick between them. list_checks is a meta/discovery tool with a distinct purpose. The only mild risk is that both scan tools share the 'audit a surface' intent and an agent unsure whether a target is remote or local may hesitate.

    Naming Consistency4/5

    All names are snake_case and readable, with scan_mcp and scan_local_program forming a coherent scan_<target> family. list_checks breaks the verb pattern but reflects a genuinely different action, and the shared scan_ prefix keeps the set predictable.

    Tool Count4/5

    Three tools is on the lean side but each earns its place: two distinct scan surfaces plus a check-discovery tool that explains requirements. Nothing feels redundant or padded for this focused security-audit purpose.

    Completeness3/5

    Coverage spans remote endpoint scanning, local config scanning, and check introspection, which is solid for the stated purpose. However, the surface is asymmetric — scan_local_program offers list_tools enumeration for stdio servers, but there is no standalone way to enumerate tools on a remote endpoint, and no tool to retrieve or re-serialize a saved report.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources