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

    • PatrowlIntelMCP by Patrowl

      PatrowlIntelMCPofficial

      Patrowl
      A
      license
      A
      quality
      D
      maintenance
      Exposes PatrowlIntel vulnerability intelligence (CVEs, EPSS, CISA KEV, public exploits, trending attacks) via MCP tools like search_cves, get_cve, and list_trending_attacks.
      3
      2
      MIT
    • scanmalware-mcp by scanmalware

      scanmalware-mcpofficial

      scanmalware
      A
      license
      Not graded
      quality
      B
      maintenance
      Wraps the ScanMalware.com API to enable phishing triage, malware scanning, and certificate inspection through natural language, allowing users to submit scans, retrieve results, and analyze threats via MCP tools.
      Apache 2.0

    • WP-MCP

      LAPSrj
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with WordPress sites through the WordPress REST API, dynamically exposing all routes as MCP tools for content management and site configuration.
      -
    • everthread by PB-Digital-LLC

      everthreadofficial

      PB-Digital-LLC
      A
      license
      A
      quality
      B
      maintenance
      Enables plain-English website security checks from an MCP client, offering tools to assess site findings, explain individual issues, and list all available security checks.
      3
      480 npm
      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.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