Skip to main content
Glama
Sim-xia

Blind-Auditor-MCP

by Sim-xia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Blind-Auditor-MCP

No user-submitted related servers found.

    Related Servers

    • gristmill-mcp

      mattshuttle
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that inspects AI-generated code and returns a deterministic list of structural and safety violations, so an AI coding agent can fix its own output before the code lands.
      2
      MIT

    • kontexta

      safiyu
      A
      license
      A
      quality
      A
      maintenance
      A local-first MCP server that gives AI coding agents persistent memory and controlled commands. Features a git-backed markdown knowledge vault with FTS5 search, surgical section edits, token-aware context budgeting, and a sandboxed command engine with human approval gates. Works with Claude Code, Cursor, Copilot, Gemini, and more.
      4
      58
      316 npm
      1
      Apache 2.0

    • Cyber Skill Router

      Julia7856
      A
      license
      Not graded
      quality
      A
      maintenance
      A sandbox-first MCP server that enables AI agents to safely perform reverse-engineering tasks in fully isolated Docker containers, featuring zero-trust security, declarative YAML-based skills, and white-hat ethical safeguards.
      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

    B3.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: reset_session handles session management, submit_audit_result and submit_draft handle different submission types (final results vs. code drafts), and update_rules handles rule configuration. The tools target different resources and actions, making misselection unlikely.

    Naming Consistency4/5

    Three tools follow a consistent verb_noun pattern (reset_session, submit_audit_result, submit_draft), while update_rules also fits this pattern but uses a different verb style ('update' vs. 'reset'/'submit'). The naming is mostly consistent with only minor deviation in verb choice.

    Tool Count5/5

    With 4 tools, this is well-scoped for an audit server. Each tool earns its place by covering core audit workflow stages: session management, rule configuration, draft submission, and result submission. The count is neither too sparse nor bloated for the domain.

    Completeness4/5

    The toolset covers the essential audit lifecycle: configure rules, submit drafts, submit results, and manage sessions. A minor gap exists in lacking a tool to retrieve or review audit results/history, but agents can work around this using the existing submission tools. Core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources