← wardzo.com

INDIVIDUAL MCP TOOL

get_report

Get the result of a Wardzo scan by its id (from scan_site, recheck_site or a wardzo.

wardzo.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://wardzo.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_report and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

wardzo.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.wardzo]
url = "https://wardzo.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "wardzo": {
      "type": "http",
      "url": "https://wardzo.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: wardzo
Remote MCP URL: https://wardzo.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "wardzo": {
      "url": "https://wardzo.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "wardzo": {
      "type": "http",
      "url": "https://wardzo.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "wardzo",
  "transport": "streamable-http",
  "url": "https://wardzo.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • scan_site — Run a passive outside-in Wardzo scan of a public website (security, SEO health, uptime) and return the score, issues and report URL.
  • list_sites — List the websites monitored in your Wardzo account with their latest score, open issue counts and uptime status.
  • add_site — Start monitoring a website: it is scanned now, then re-scanned on your plan schedule, with uptime checks and email alerts.
  • get_site_status — Latest score (with change since the previous scan), open issues by severity, top issues, uptime (24h and 7d) and what changed in the last scan, for one of your monitored sites.
  • list_issues — List open issues from the latest scan of one of your sites, most severe first.
  • explain_issue — Explain why an issue matters and give step-by-step fix instructions (with Next.
  • recheck_site — Run a fresh scan of one of your monitored sites (e.
  • list_endpoints — List the endpoint checks (GET/HEAD monitors for specific URLs such as /api/health) on one of your sites, with their current status, last HTTP status and response time.