Skip to main content
Glama

Related Servers

Alternatives to toolfence

No user-submitted related servers found.

    Related Servers

    • 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.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.
      436 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Runs read-only, offline static scans of the local machine's MCP server configs and agent skill folders, surfacing prompt injection, hidden Unicode, dangerous commands, credential paths, hardcoded secrets, unpinned packages, and over-broad filesystem or transport scope as text, JSON, SARIF, or HTML reports an agent can act on. Also allows scanning a single downloaded skill folder or a saved tools/list JSON so an agent can vet third-party components before installing them.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to run deterministic, read-only local repository audits for risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration, returning structured findings without sending source code to a service.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Security scanning for MCP servers from the inside out. Provides runtime inspection, AST-based static analysis, config audit, dependency analysis, and OWASP MCP Top 10 compliance in a single MCP server.
      55
      60 npm
      6
      MIT

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool has a distinct input source: scan_tool_manifest works on a manifest you already hold offline, scan_repository pulls tool definitions from a public repo, and explain_rule documents a rule. The two 'scan' tools share the auditing verb and could momentarily be confused, but the descriptions clearly delimit offline-manifest vs repository input.

    Naming Consistency5/5

    All three names follow a consistent verb_noun snake_case pattern (scan_tool_manifest, explain_rule, scan_repository). No mixed conventions or casing irregularities.

    Tool Count4/5

    Three tools is focused and each earns its place within a small auditing surface. It sits at the low end of the well-scoped range but is not thin given the narrow domain.

    Completeness4/5

    Coverage spans both entry points for auditing (offline manifest and repository) plus rule explanation, which is a coherent lifecycle for a linter. A list-rules operation or batch/fleet scanning would round it out, but agents can work around these minor gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues