Skip to main content
Glama
actions-marketplace-validations

MCProbe

by actions-marketplace-validations
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCProbe

No user-submitted related servers found.

    Related Servers

    • MCProbe

      alitiknazoglu
      A
      license
      A
      quality
      A
      maintenance
      A stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.
      6
      6
      MIT

    • 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

    • Schema Sentinel

      SanjoyDat1
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that validates tool calls against JSON Schema, performs deterministic repair, redacts secrets, and maintains a hash-chained audit ledger.
      -

    • 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.
      9 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.
      48 npm
      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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: connect opens connections, list enumerates tools, lint validates schemas, fuzz tests inputs, report aggregates results, and disconnect closes connections. Even though report includes lint and fuzz, its purpose as a high-level summary is unambiguous.

    Naming Consistency5/5

    All tools follow a consistent 'probe_' prefix with a verb-noun structure (probe_connect, probe_lint, probe_fuzz, probe_report, probe_list, probe_disconnect). No mixing of conventions or vague names.

    Tool Count5/5

    Six tools is well-scoped for a server that probes MCP targets. Each tool covers a necessary step in the workflow without redundancy or bloat.

    Completeness5/5

    The tool set covers the full probe lifecycle: connect, enumerate, lint, fuzz, report, and disconnect. There are no obvious missing operations for the stated purpose of probing and assessing MCP servers.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources