Skip to main content
Glama
asif786ka

store-preflight-mcp

by asif786ka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to store-preflight-mcp

No user-submitted related servers found.

    Related Servers

    • repo-contract

      dager23
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enforces repository governance rules for AI coding agents, providing tools to validate plans, diffs, and scan for architectural and safety violations.
      1
      MIT

    • mcp-secret-sentinel

      AleBrito124356
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that scans code for exposed secrets (API keys, tokens, private keys, high-entropy strings) with placeholder-aware allowlisting and fully redacted reports, enabling agents to detect leaks before committing.
      2
      MIT
    • @squirex.dev/mcp-server by SquireX-dev

      @squirex.dev/mcp-serverofficial

      SquireX-dev
      A
      license
      A
      quality
      D
      maintenance
      MCP server that scans Salesforce Agentforce metadata for security vulnerabilities using 61+ SAST rules, integrating into AI coding workflows to guard against OWASP LLM top 10 risks.
      16
      5 npm
      Cryptographic Autonomy 1.0 (Combined Work Exception)

    • Security Scan MCP Server

      chrischabot
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides CVE-driven security prompts for code review, enabling coding agents to get actionable security checks based on real vulnerabilities.
      MIT

    • safe-code-mcp

      marcojourney
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that provides controlled repository access with policy-based file filtering, secret redaction, and audit logging for AI coding agents.
      -
    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.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: scanning, explaining rejections, and listing deadlines. However, check_api_declaration and get_required_declaration both retrieve declaration information from different inputs (API symbol vs rule_id), which could cause confusion for an agent trying to select the right one.

    Naming Consistency4/5

    Four tools follow a clear verb_noun pattern (check_api_declaration, explain_rejection, get_required_declaration, list_policy_deadlines). preflight_scan is a slight deviation as a compound noun, but it still clearly conveys its purpose.

    Tool Count5/5

    With five tools, the server covers the essential preflight workflow without extraneous tools. Each tool serves a distinct role in the submission preparation process, and the count feels well-scoped.

    Completeness4/5

    The tool surface covers the core workflow: scanning, declaration lookup, rejection interpretation, and policy deadlines. A minor gap is the lack of a tool to compare scan results or generate reports, but the set is sufficient for the primary use case.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources