Wardzo

com.wardzo/wardzoVersion 1.1.0

Scan and monitor websites for leaked keys, exposed files, security headers, SEO issues and uptime.

Status

Responds37 msNov 14, 2026, 14:23 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:23 UTC
Latency: 37 ms
Remotes responding: 2 of 2
Sign-in: OAuth sign-in, No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://wardzo.com/mcpResponds164 msNov 14, 2026, 14:22 UTC

No sign-in

Claude Code

claude mcp add --transport http wardzo https://wardzo.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: wardzo
Remote MCP server URL: https://wardzo.com/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"wardzo","type":"http","url":"https://wardzo.com/mcp"}'

Streamable HTTP

https://wardzo.com/mcp/accountSign-in required37 msNov 14, 2026, 14:23 UTC

OAuth sign-in

Claude Code

This server asks for sign-in. Your client opens the sign-in when it connects.

claude mcp add --transport http wardzo https://wardzo.com/mcp/account

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: wardzo
Remote MCP server URL: https://wardzo.com/mcp/account

Cursor

{
  "mcpServers": {
    "wardzo": {
      "url": "https://wardzo.com/mcp/account"
    }
  }
}

VS Code

code --add-mcp '{"name":"wardzo","type":"http","url":"https://wardzo.com/mcp/account"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

12 tools

Tools of Wardzo
	Description		Read-only	Idempotent	Open world
`add_endpoint`Monitor a specific URL on one of your verified sites (for example an API health route, login or checkout page) with a GET or HEAD request on a schedule. The domain must be verified first, and the URL must not include a query string. 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.	Monitor a specific URL on one of your verified sites (for example an API health route, login or checkout page) with a GET or HEAD request on a schedule. The domain must be verified first, and the URL must not include a query string. 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.	No	No	No	Yes
`add_site`Start monitoring a website: it is scanned now, then re-scanned on your plan schedule, with uptime checks and email alerts.	Start monitoring a website: it is scanned now, then re-scanned on your plan schedule, with uptime checks and email alerts.	No	No	Yes	Yes
`explain_issue`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.	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.	Not declared	Yes	Not declared	Not declared
`get_new_findings`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.	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.	No	No	No	No
`get_report`Get the result of a Wardzo scan by its id (from scan_site, recheck_site or a wardzo.com/r/<id> link).	Get the result of a Wardzo scan by its id (from scan_site, recheck_site or a wardzo.com/r/<id> link).	Not declared	Yes	Not declared	Not declared
`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.	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.	Not declared	Yes	Not declared	Not declared
`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.	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.	Not declared	Yes	Not declared	Not declared
`list_issues`List open issues from the latest scan of one of your sites, most severe first. Each issue has an issue_id for explain_issue.	List open issues from the latest scan of one of your sites, most severe first. Each issue has an issue_id for explain_issue.	Not declared	Yes	Not declared	Not declared
`list_sites`List the websites monitored in your Wardzo account with their latest score, open issue counts and uptime status.	List the websites monitored in your Wardzo account with their latest score, open issue counts and uptime status.	Not declared	Yes	Not declared	Not declared
`recheck_site`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.	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.	No	No	Not declared	Yes
`remove_endpoint`Stop monitoring one endpoint check and delete its history. Use list_endpoints to find the endpoint_id.	Stop monitoring one endpoint check and delete its history. Use list_endpoints to find the endpoint_id.	Yes	No	Yes	No
`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. Waits up to ~45 seconds for the result. Works without an API key (rate limited).	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).	Not declared	Yes	Not declared	Yes

Details

Registry status: Active
Published: Oct 27, 2026
Updated: Oct 27, 2026
Website: https://wardzo.com/mcp-server⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing