Security & Testing
wardzo.com
Wardzo is an MCP server for scanning and monitoring websites, providing security, SEO health, uptime scores, issue reports, and alerts.
ENDPOINT 1
https://wardzo.com/mcp/account
Known tools 0
No tool metadata was available in the registry cache.
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-com]
url = "https://wardzo.com/mcp/account"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"wardzo-com": {
"type": "http",
"url": "https://wardzo.com/mcp/account",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: wardzo-com
Remote MCP URL: https://wardzo.com/mcp/account
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"wardzo-com": {
"url": "https://wardzo.com/mcp/account",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"wardzo-com": {
"type": "http",
"url": "https://wardzo.com/mcp/account",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "wardzo-com bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "wardzo-com",
"transport": "streamable-http",
"url": "https://wardzo.com/mcp/account",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://wardzo.com/mcp
MCP server metadata
- Name
- wardzo
- Version
- 1.1.0
Wardzo monitors live websites from the outside for security (leaked API keys, exposed .env/.git files, security headers, TLS, SEO spam/cloaking), SEO health (noindex, robots.txt, sitemaps, titles, broken pages) and uptime. Use scan_site for a quick passive scan of any public URL (works without an API key, but then returns a summary only: score, counts by severity and the top finding). With an API key: list_sites, add_site, get_site_status, list_issues, explain_issue, recheck_site, plus endpoint checks (list_endpoints, add_endpoint, remove_endpoint) that watch specific URLs on your sites with GET/HEAD. Typical fix loop for a coding agent: list_issues -> explain_issue(issue_id) -> apply the fix in the codebase or hosting config -> deploy -> recheck_site. Scans are passive and read-only; Wardzo never attacks a site. Secrets in evidence are masked; any exposed key must be rotated.
Known tools 11
scan_siteRun a passive outside-in Wardzo scan of a public website (security, SEO health, uptime) and return the score, issues and report URL.
Inferred read-onlyget_reportGet the result of a Wardzo scan by its id (from scan_site, recheck_site or a wardzo.
Inferred read-onlylist_sitesList the websites monitored in your Wardzo account with their latest score, open issue counts and uptime status.
Inferred read-onlyadd_siteStart monitoring a website: it is scanned now, then re-scanned on your plan schedule, with uptime checks and email alerts.
Potential side effectsget_site_statusLatest 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.
Inferred read-onlylist_issuesList open issues from the latest scan of one of your sites, most severe first.
Inferred read-onlyexplain_issueExplain why an issue matters and give step-by-step fix instructions (with Next.
Inferred read-onlylist_endpointsList 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.
Inferred read-onlyadd_endpointMonitor 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.
Inferred read-onlyCONNECT 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.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.