_ registry / mcp streamable-http · checked 1h ago

wardzo

https://wardzo.com

Registry code: 021de89c61a8a885

api record

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…

endpoint
https://wardzo.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is wardzo live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is wardzo free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does wardzo have?
11 tools: explain_issue, add_site, list_endpoints, remove_endpoint, scan_site, get_site_status, list_issues, recheck_site, ….
Is wardzo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
362ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
1 auth-required 10 never probed 1 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_sites auth-required 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • explain_issue unknown 1h ago

    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.

    mcp-tool

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

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

    mcp-tool

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

    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.

    mcp-tool

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

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "endpoint_id"
  ],
  "properties": {
    "endpoint_id": {
      "type": "integer",
      "description": "endpoint_id from list_endpoints",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • scan_site unknown never probed

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

    mcp-tool

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

    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.

    mcp-tool

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

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

    mcp-tool

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

    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.

    mcp-tool

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

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "site",
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "Full URL on that site, or a path like \"/api/health\""
    },
    "site": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "Site id, domain or URL of one of your monitored sites"
    },
    "max_ms": {
      "type": "integer",
      "maximum": 30000,
      "minimum": 100,
      "description": "Fail if the response takes longer than this many milliseconds"
    },
    "method": {
      "enum": [
        "GET",
        "HEAD"
      ],
      "type": "string",
      "description": "HTTP method (default GET)"
    },
    "expect_status": {
      "type": "integer",
      "maximum": 599,
      "minimum": 100,
      "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)"
    }
  },
  "additionalProperties": false
}
    arguments 48 lines
  • get_report unknown 1h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 6,
      "description": "Scan id or report URL"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 021de89c61a8a885.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/021de89c61a8a885/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/021de89c61a8a885/badge.svg)](https://brick.blue/agent/021de89c61a8a885?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.