Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Wardzo

REMOTE · WARDZO.COM · 2 COMPONENTS

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

+3 this week 78 Trust /100

Last scanned (16 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1435 tokens (~119/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 0
    • Tool “get_new_findings” rewrote its description, which is the text the model reads security
    • “explain_issue” reworded the description of “issue_id” cosmetic
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://wardzo.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wardzo.com CN=YE2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 58316441e0216f8b51771729777bf2ac85a
SANs: wardzo.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of wardzo.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
wardzo.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'nonce-MmIyNTE5MzEtNzc5Ny00YjY4LTg1NjQtMDkyZThiNGE1YzBh' 'strict-dynamic'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wardzo.com/mcp Verified 200
http (plaintext) http://wardzo.com/mcp HTTPS enforced 308 https://wardzo.com/mcp
MCP tools · 12 exposed · ~1,070 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_endpoint ~219

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.

NameTypeReqDescription
expect_keywordstring–Text that must appear in the response body (GET only)
expect_statusinteger–Exact expected HTTP status (default: any 2xx or 3xx)
max_msinteger–Fail if the response takes longer than this many milliseconds
methodstring–HTTP method (default GET)
sitestringyesSite id, domain or URL of one of your monitored sites
urlstringyesFull URL on that site, or a path like "/api/health"

No output schema declared.

No examples provided.

add_site ~45

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

NameTypeReqDescription
urlstringyesWebsite URL or domain

No output schema declared.

No examples provided.

explain_issue ~102

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.

NameTypeReqDescription
issue_idstringyesissue_id from list_issues/scan_site (e.g. "AbC123xyz:hsts_missing") or a check name (e.g. "hsts_missing")

No output schema declared.

No examples provided.

get_new_findings ~267

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 (sensitive values redacted). 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.

NameTypeReqDescription
limitinteger–Maximum findings to return (default 50). If more are waiting, call again.
mark_seenboolean–Mark the returned findings as seen for this connection (default true)
sincestring–ISO 8601 timestamp, e.g. 2026-10-27T08:00:00Z. Returns findings first seen after it, ignoring and not moving the last-seen marker.
sitestring–Only this site (id, domain or URL). Peek only: does not mark anything as seen.

No output schema declared.

No examples provided.

get_report ~50

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

NameTypeReqDescription
idstringyesScan id or report URL

No output schema declared.

No examples provided.

get_site_status ~64

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.

NameTypeReqDescription
sitestringyesSite id, domain or URL

No output schema declared.

No examples provided.

list_endpoints ~59

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.

NameTypeReqDescription
sitestringyesSite id, domain or URL

No output schema declared.

No examples provided.

list_issues ~64

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

NameTypeReqDescription
severitystring–Minimum severity to include (default: low)
sitestringyesSite id, domain or URL

No output schema declared.

No examples provided.

list_sites ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recheck_site ~54

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.

NameTypeReqDescription
sitestringyesSite id, domain or URL

No output schema declared.

No examples provided.

remove_endpoint ~42

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

NameTypeReqDescription
endpoint_idintegeryesendpoint_id from list_endpoints

No output schema declared.

No examples provided.

scan_site ~75

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).

NameTypeReqDescription
urlstringyesWebsite URL or domain, e.g. example.com

No output schema declared.

No examples provided.

Install

How do I install the Wardzo MCP server?

Wardzo is a hosted endpoint at https://wardzo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · wardzo.com

# add to Claude Code
claude mcp add --transport http com-wardzo-wardzo 'https://wardzo.com/mcp'
Common questions

What is the Wardzo MCP server?

Wardzo is an MCP server listed in the public MCP registry as com.wardzo/wardzo. Scan and monitor websites for leaked keys, exposed files, security headers, SEO issues and uptime. This page covers its hosted endpoint (https://wardzo.com/mcp).

Is the Wardzo MCP server safe to use?

Wardzo scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Wardzo MCP server expose?

Wardzo exposes 12 tools: scan_site, get_report, list_sites, add_site, get_site_status, and 7 more. Their descriptions and schemas cost roughly 1,070 tokens of context every time the server is loaded.

Does the Wardzo MCP server require authentication?

No. We connected to Wardzo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Wardzo MCP server still maintained?

Wardzo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Wardzo MCP server?

VerifyMCP ran 13 checks on Wardzo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.