Skip to main content
Glama
Decian-Inc

connectsecure-mcp

by Decian-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to connectsecure-mcp

No user-submitted related servers found.

    Related Servers

    • meloqa-mcp

      swl-informatica
      A
      license
      C
      quality
      C
      maintenance
      Exposes every operation from the meloQA v1 API as MCP tools, enabling LLM clients to read and manage meloQA projects, test cases, cycles, executions, bugs, links, and reference data.
      83
      11 npm
      MIT
    • ForIT MCP Gateway by ForITLLC

      ForIT MCP Gatewayofficial

      ForITLLC
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables turning selected OpenAPI operations into authenticated MCP tools with branded OAuth, operation allowlisting, and live schema refreshes.
      Apache 2.0

    • safe-oas2mcp

      Zzzzzkk98
      F
      license
      Not graded
      quality
      D
      maintenance
      Turns OpenAPI specs into MCP tools with secure defaults, risk inspection, confirmation gates, response limits, audit logging, and secret redaction.
      -

    • cloudradial-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes the CloudRadial REST API (client portal / PSA-adjacent MSP platform) as MCP tools, enabling operations on companies, articles, feedback, archives, flexible assets, and more via 34 tools with HTTP Basic Auth.
      1
      -

    • openapi-to-mcp

      The-Swarm-Corporation
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to call any OpenAPI-defined API by automatically converting its operations into tools, with built-in support for authentication, rate limiting, and response handling.
      7
      Apache 2.0
    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

    C2.4/5.0

    Scored across 359 tools

    Disambiguation2/5

    Many tools are distinguished only by long report-query route suffixes (e.g., the many application_vulnerabilities_* variants), and numerous descriptions are generic 'Retrieve records' or copy-pasted like 'Update schedule' for remove_schedule. This makes misselection highly likely despite technically unique names.

    Naming Consistency3/5

    Most tools follow a consistent {method}_{route} snake_case pattern with get_r_, post_w_, patch_w_, and delete_d_ prefixes. However, conventions are mixed: some routes drop the r_ prefix (get_report_queries_*), there are double verbs like get_r_user_get_users, and typos like suppres and unqouted break uniformity.

    Tool Count1/5

    359 tools is an extreme count for an MCP server and far beyond a well-scoped toolset; this is a raw REST API dump rather than a curated agent surface. Such a large tool list overwhelms context and makes reliable tool selection impractical.

    Completeness4/5

    The surface provides broad CRUD coverage for core entities such as companies, assets, credentials, integrations, and tags, plus scanning, patching, remediation, and extensive reporting queries. Minor gaps exist for some read-only subresources, but the API surface is comprehensive enough to avoid dead ends in most workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources