Skip to main content
Glama
AranSeshita

yamory MCP Server

by AranSeshita
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to yamory MCP Server

No user-submitted related servers found.

    Related Servers

    • vuln-intel-mcp

      rohanrajnist
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides CVE lookup, search, and exploit intelligence from public vulnerability sources (NVD, CISA KEV, EPSS) for AI agents to produce remediation guidance without consuming LLM tokens for data fetching.
      1
      MIT

    • Exploit Intel Platform MCP

      OyaAIProd
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search and analyze vulnerabilities and exploits from multiple intelligence sources, including NVD, CISA KEV, ExploitDB, Metasploit, and more, with tools for CVE research, exploit analysis, and report generation.
      17
      MIT

    • ScanRook MCP Server

      devinshawntripp
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform vulnerability scanning on Docker/OCI images, check CVE details, analyze licenses, and compare scan results via ScanRook.
      8
      8 npm
      MIT

    • Security Intel MCP

      datakoot
      A
      license
      Not graded
      quality
      B
      maintenance
      Vulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.
      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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each search tool targets a distinct vulnerability type (app, container, asset, host) with a general-purpose fallback. Overlap exists between the general search and specific ones, but descriptions clarify use cases.

    Naming Consistency4/5

    All tools follow the 'search_<target>_vulns' pattern consistently except the general 'search_vulns' which lacks a target specifier. This minor deviation is acceptable.

    Tool Count5/5

    With 5 tools covering general and specific vulnerability searches, the count is well-scoped for the domain. Each tool has a clear purpose and no redundancy.

    Completeness4/5

    The toolset covers the main resource types for vulnerability search. While missing advanced features like vulnerability updates or detailed lookups, the surface is complete for a search-focused MCP server.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources