Skip to main content
Glama
alitiknazoglu

MCProbe

by alitiknazoglu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCProbe

No user-submitted related servers found.

    Related Servers

    • mcp-proof

      YuCPbit
      A
      license
      Not graded
      quality
      A
      maintenance
      Audits any MCP server (stdio or Streamable HTTP, legacy or modern era) with wire-level conformance, security, and behavior-regression checks, producing a fingerprinted delivery report and CI regression suite.
      1
      MIT

    • mcp-audit

      andreolf
      A
      license
      Not graded
      quality
      A
      maintenance
      npm audit for MCP servers. Point it at an MCP server and get a security grade (A–F) covering missing auth, SSRF surface, high-privilege tools, prompt-injection-prone tool descriptions, and leaked secrets.
      12 npm
      MIT

    • owasp-mcp-scan

      CodingSelim
      A
      license
      Not graded
      quality
      B
      maintenance
      Passive security scanner that audits a running MCP server against the OWASP MCP Top 10 and grades it A-F. Read-only static analysis of the advertised tools, prompts and resources with console/JSON/SARIF output, and it also runs as an MCP server itself.
      42 npm
      MIT

    • mcp-audit

      saagpatel
      A
      license
      Not graded
      quality
      A
      maintenance
      Audits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.
      4
      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.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: connect, lint, fuzz, report, list, disconnect. No overlap or ambiguity in their functions.

    Naming Consistency5/5

    All tools follow the consistent verb_noun pattern with 'probe_' prefix (e.g., probe_connect, probe_lint), ensuring predictability.

    Tool Count5/5

    Six tools cover the necessary operations for probing MCP servers (connect, list, lint, fuzz, report, disconnect) without being excessive or insufficient.

    Completeness5/5

    The tool set covers the full lifecycle: connection, introspection (list, report), linting, fuzzing, and disconnection. No obvious gaps for the stated domain.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources