Skip to main content
Glama
sjinks

wpscan-mcp

by sjinks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to wpscan-mcp

No user-submitted related servers found.

    Related Servers

    • CVE-Search MCP Server

      NancyLawson80689
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables querying the CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, fetch the latest CVEs with CAPEC/CWE/CPE details, and check database update status via MCP tools.
      -

    • CVE-Search MCP Server

      Joans07
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables querying the CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, fetch the latest updated CVEs with CAPEC/CWE/CPE expansions, and check current database information. It provides these capabilities through MCP tools for use in compatible clients.
      -

    • CVE-Search MCP Server

      Chavez36040
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables querying the CVE-Search API to retrieve vendors, products, product-specific vulnerabilities, specific CVE IDs, recently updated CVEs with CAPEC/CWE/CPE expansions, and database update information. It supports natural-language access to CVE data through MCP clients.
      -

    • CVE-Search MCP Server

      Camille54359
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables querying the CVE-Search API to browse vendors, list products for a vendor, retrieve vulnerabilities for a vendor and product, fetch individual CVE records, get the latest CVEs with CAPEC/CWE/CPE expansions, and inspect current database version information. This gives MCP clients direct, structured access to public vulnerability data.
      -
    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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct resource: core WordPress vulnerabilities, specific vulnerability by ID, plugin vulnerabilities, and theme vulnerabilities. There is no overlap, and agents can easily distinguish which tool to use.

    Naming Consistency4/5

    All tools share the 'wpscan_' prefix, but the naming patterns vary slightly: three use object_lookup (core, plugin, theme) while one uses lookup_vuln. This is a minor inconsistency but still readable and understandable.

    Tool Count5/5

    With only 4 tools, the server is well-scoped for querying WordPress vulnerabilities. Each tool covers a key area (core, plugins, themes, individual vulnerabilities), and the count is appropriate for the domain without unnecessary bloat.

    Completeness4/5

    The tools cover the main vulnerability lookup operations for WordPress. However, a search or list-all tool is missing, which could limit agents needing to browse vulnerabilities without a specific ID or slug. This is a minor gap.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources