Wardzo

Run a passive outside-in Wardzo scan of a public website (security, SEO health, uptime) and return the score, issues and report URL. Waits up to ~45 seconds for the result. Works without an API key (rate limited).

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "minLength": 3,
      "maxLength": 300,
      "description": "Website URL or domain, e.g. example.com"
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Get the result of a Wardzo scan by its id (from scan_site, recheck_site or a wardzo.com/r/<id> link).

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 6,
      "maxLength": 80,
      "description": "Scan id or report URL"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

List the websites monitored in your Wardzo account with their latest score, open issue counts and uptime status.

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Start monitoring a website: it is scanned now, then re-scanned on your plan schedule, with uptime checks and email alerts.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "minLength": 3,
      "maxLength": 300,
      "description": "Website URL or domain"
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Site id, domain or URL"
    }
  },
  "required": [
    "site"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

List open issues from the latest scan of one of your sites, most severe first. Each issue has an issue_id for explain_issue.

{
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Site id, domain or URL"
    },
    "severity": {
      "type": "string",
      "enum": [
        "critical",
        "high",
        "medium",
        "low",
        "info"
      ],
      "description": "Minimum severity to include (default: low)"
    }
  },
  "required": [
    "site"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Get the findings Wardzo detected on your monitored sites since this connection last checked (background re-scans, re-checks and new sites), newest last, and mark them as seen for this connection. A finding that stays open across scans is reported once, not every scan. The first call on a new connection returns every open finding. Each item has an issue_id for explain_issue, a status (open, or resolved if it was already fixed by the next scan) and evidence (secrets masked). Use mark_seen=false to peek without marking, or since (ISO timestamp) to list findings first seen after a time (does not move the marker). Filtering by site is also a peek.

{
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Only this site (id, domain or URL). Peek only: does not mark anything as seen."
    },
    "since": {
      "type": "string",
      "minLength": 10,
      "maxLength": 40,
      "description": "ISO 8601 timestamp, e.g. 2026-10-27T08:00:00Z. Returns findings first seen after it, ignoring and not moving the last-seen marker."
    },
    "mark_seen": {
      "type": "boolean",
      "description": "Mark the returned findings as seen for this connection (default true)"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Maximum findings to return (default 50). If more are waiting, call again."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Explain why an issue matters and give step-by-step fix instructions (with Next.js, Vercel, Netlify, Nginx, Apache, Cloudflare and WordPress snippets where relevant) that an AI coding agent can apply, plus how to verify.

{
  "type": "object",
  "properties": {
    "issue_id": {
      "type": "string",
      "minLength": 3,
      "maxLength": 120,
      "description": "issue_id from list_issues/scan_site (e.g. \"AbC123xyz:hsts_missing\") or a check name (e.g. \"exposed_env\")"
    }
  },
  "required": [
    "issue_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Run a fresh scan of one of your monitored sites (e.g. after deploying a fix) and report what changed. Waits up to ~45 seconds.

{
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Site id, domain or URL"
    }
  },
  "required": [
    "site"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

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.

{
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Site id, domain or URL"
    }
  },
  "required": [
    "site"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Monitor a specific URL on one of your sites (for example an API health route, login or checkout page) with a GET or HEAD request on a schedule. Optionally require an exact HTTP status, a text snippet in the response, and a maximum response time. You get an email alert when it fails twice in a row and when it recovers. Wardzo never submits forms or sends request bodies.

{
  "type": "object",
  "properties": {
    "site": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Site id, domain or URL of one of your monitored sites"
    },
    "url": {
      "type": "string",
      "minLength": 1,
      "maxLength": 500,
      "description": "Full URL on that site, or a path like \"/api/health\""
    },
    "method": {
      "type": "string",
      "enum": [
        "GET",
        "HEAD"
      ],
      "description": "HTTP method (default GET)"
    },
    "expect_status": {
      "type": "integer",
      "minimum": 100,
      "maximum": 599,
      "description": "Exact expected HTTP status (default: any 2xx or 3xx)"
    },
    "expect_keyword": {
      "type": "string",
      "maxLength": 100,
      "description": "Text that must appear in the response body (GET only)"
    },
    "max_ms": {
      "type": "integer",
      "minimum": 100,
      "maximum": 30000,
      "description": "Fail if the response takes longer than this many milliseconds"
    }
  },
  "required": [
    "site",
    "url"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Stop monitoring one endpoint check and delete its history. Use list_endpoints to find the endpoint_id.

{
  "type": "object",
  "properties": {
    "endpoint_id": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "endpoint_id from list_endpoints"
    }
  },
  "required": [
    "endpoint_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}