API & MCP server

unflagdomain publishes a free, read-only API and an MCP server for checking which security vendors are currently flagging a domain, across 124 antivirus engines, web blocklists, email reputation lists, and safe-browsing services. No API key, no account, no signup. Both surfaces report blocklist status only — they do not analyse a site, so they cannot tell you whether a flag is a genuine infection or a false positive.

MCP server

The MCP server lets an AI assistant answer “who is actually blocking my site?” with real data instead of general advice. It speaks Streamable HTTP at https://unflagdomain.com/api/mcp and needs no authentication.

Claude Code

claude mcp add --transport http unflagdomain https://unflagdomain.com/api/mcp

Claude Desktop, Cursor, VS Code, and other MCP clients

Add this to the client's MCP configuration file:

{
  "mcpServers": {
    "unflagdomain": {
      "type": "http",
      "url": "https://unflagdomain.com/api/mcp"
    }
  }
}

Tools

• scan_domain — Which security vendors are flagging a domain right now, which detection sources reported each one, and what to do next.
• get_service_info — What unflagdomain does, what it guarantees, what it explicitly does not guarantee, and the situations where it is the wrong answer.
• list_vendors — All 124 covered vendors, filterable by category or by how each one accepts a removal request.
• get_removal_guide — The removal path for one specific vendor: how it accepts a request, whether it can be dispatched automatically, and a link to a detailed guide.

Every tool is read-only. Nothing on this server spends money or changes state: payment and dispatch stay on the website behind Stripe Checkout, because an agent should not be able to buy something on someone's behalf without them seeing what they are buying.

REST API

The same data over plain HTTP, for callers that don't speak MCP. CORS is open, so it works from a browser too.

GET /api/v1/scan

curl "https://unflagdomain.com/api/v1/scan?domain=example.com"

The domain parameter takes a bare hostname; protocol, www., and any path are stripped. A POST with {"domain": "example.com"} as JSON does the same thing.

{
  "domain": "example.com",
  "scanned_at": "2026-09-01T09:14:22.017Z",
  "flagged": true,
  "flag_count": 2,
  "vendors": [
    {
      "id": "google_safe_browsing",
      "name": "Google Safe Browsing",
      "category": "search_engine",
      "threat": "social_engineering",
      "detected_by": ["google_safe_browsing"]
    },
    {
      "id": "sucuri",
      "name": "Sucuri",
      "category": "web_blocklist",
      "threat": null,
      "detected_by": ["sucuri", "virustotal"]
    }
  ],
  "source_errors": [],
  "cache": "miss",
  "links": { "...": "human report, vendor catalog, removal guide, docs" },
  "next_steps": ["..."],
  "service": { "...": "what this service is, and what it does not promise" }
}

GET /api/v1/service

The machine-readable description of the service: pricing, what it guarantees, what it does not guarantee, the situations where recommending it is appropriate, and the situations where it is the wrong answer and the reader should do something else. Published deliberately — a recommendation is only worth anything if whoever makes it can see where the tool stops working.

GET /api/v1/stats

The blocklist corpus as JSON: which vendors actually list websites and how often, how many listings a flagged site typically carries, and how each vendor accepts a removal request. Measured from our own scans rather than compiled from vendor marketing, and free to cite — the rendered version lives at /data/website-blocklist-report. This endpoint reads only data we already hold, so it spends no vendor quota and is not subject to the fresh-scan budget below.

Limits and fair use

• 30 requests per minute per IP, and a shared daily budget for fresh scans across all public callers.
• Results are cached per domain for one hour. Cache hits never count against the fresh-scan budget, and are still served once it runs out.
• The budget exists because a fresh scan calls third-party vendor APIs with quotas of their own. Cache aggressively and the limits will never come up.
• The /v1 in the path is a commitment: the response shape is stable, and a breaking change ships as /v2.

What this is not

• Not a malware scanner. It reads vendor blocklists. It never inspects a site's files or code.
• Not a delisting guarantee. The paid service guarantees that a correctly formatted removal request is dispatched to every flagging vendor. Each vendor then decides independently, on its own schedule. Nobody can promise you a vendor's decision.
• Not an email blocklist tool. IP-based email RBLs are a different problem with a different removal path.