Skip to main content
Glama
Space-C0wboy

Vicarius vRx MCP Server

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Vicarius vRx MCP Server

No user-submitted related servers found.

    Related Servers

    • connectsecure-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for ConnectSecure vulnerability management, exposing 285 read-only tools to query assets, vulnerabilities, Active Directory, and more via natural language.
      -

    • offsec-mcp

      nadirzhon
      A
      license
      A
      quality
      B
      maintenance
      MCP server for offensive-security tooling, enabling AI agents to run reconnaissance, CVE intelligence, JavaScript analysis, HTTP probing, and port scanning against authorized targets.
      10
      MIT

    • OpenAPI MCP Bridge

      samuellawrence
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP server that converts any OpenAPI/Swagger specification into MCP tools, enabling AI assistants to search, explore, and execute REST APIs.
      MIT

    • VulnMCP

      vulnerability-lookup
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for vulnerability management that provides tools for automated severity and CWE classification using NLP models. It enables AI agents to query the Vulnerability Lookup API for detailed CVE information and search for security vulnerabilities across various sources.
      16
      42
      AGPL 3.0

    • Integrations MCP

      Shriram-Vasudevan
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server providing over 390 tools across 66 providers, including major SaaS platforms like GitHub, Slack, and Stripe. It enables AI assistants to interact directly with a wide array of public APIs and utility services through a single interface.
      -
    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

    D1.9/5.0

    Scored across 89 tools

    Disambiguation2/5

    Multiple tools have nearly identical descriptions (e.g., 'Groups objects by stuff'), and many share the same actions (count, search, filter) across different entities with little distinction. The presence of GET and POST variants for count tools and numbered suffixes (e.g., _1, _2) adds confusion.

    Naming Consistency2/5

    Tool names mix inconsistent patterns: long underscore-separated paths, version numbers (e.g., automations_automations_1), and generic verbs (search, count, filter) without a clear consistent structure. Some names include HTTP methods or API details, making them unwieldy.

    Tool Count1/5

    89 tools is excessive for a single MCP server. This suggests an overly fine-grained API surface that would overwhelm agents. Many tools are redundant or too narrow, and the count far exceeds typical well-scoped servers (3-15 tools).

    Completeness2/5

    While many entities are covered, there are significant gaps: limited create/update/delete operations for core resources, and the inclusion of a generic 'vrx_request' tool indicates the set is incomplete. Descriptions like 'Get object by connection' are vague, and many CRUD operations are missing.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources