Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 12 tools

Disambiguation4/5

Most tools have clearly distinct resource+action targets (add_site, list_sites, add_endpoint, remove_endpoint, explain_issue). There is mild overlap between scan_site/recheck_site and between get_site_status/list_issues/get_new_findings, but the descriptions explicitly differentiate them (public one-off scan vs re-scan of a monitored site; summary vs detailed issues vs delta since last check).

Naming Consistency5/5

All twelve tools follow a strict verb_noun snake_case convention (add_site, list_endpoints, get_report, recheck_site, remove_endpoint). No camelCase or vague bare verbs are present.

Tool Count5/5

Twelve tools sit comfortably in the ideal range and each maps to a concrete operation: site CRUD-ish operations, endpoint monitoring lifecycle, scanning, and issue retrieval/explanation. Nothing appears redundant or padded.

Completeness3/5

Endpoint monitoring has a full lifecycle (add/list/remove), but sites only have add and list — there is no remove_site or update_site, leaving a dead end for stopping or reconfiguring monitoring. There is also no way to dismiss/ignore or mark a finding resolved, so lifecycle coverage is notably partial.

Available Tools

12 tools
add_endpointAdd an endpoint checkAInspect

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.

Inputs: url (required), site (required), max_ms, method, +2 more.

add_siteAdd a site to monitoringA
Idempotent
Inspect

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

Inputs: url (required).

explain_issueExplain an issue and how to fix itA
Read-only
Inspect

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.

Inputs: issue_id (required).

get_new_findingsGet new findings since last checkAInspect

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.

Inputs: site, limit, since, mark_seen.

get_reportGet a scan reportA
Read-only
Inspect

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

Inputs: id (required).

get_site_statusGet site statusA
Read-only
Inspect

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.

Inputs: site (required).

list_endpointsList endpoint checksA
Read-only
Inspect

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.

Inputs: site (required).

list_issuesList open issuesA
Read-only
Inspect

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

Inputs: site (required), severity.

list_sitesList monitored sitesA
Read-only
Inspect

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

Inputs: no named parameters.

recheck_siteRe-scan one of your sitesAInspect

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.

Inputs: site (required).

remove_endpointRemove an endpoint checkA
DestructiveIdempotent
Inspect

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

Inputs: endpoint_id (required).

scan_siteScan a websiteA
Read-only
Inspect

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

Inputs: url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources