# unflagdomain: website blacklist removal (remote · unflagdomain.com)

Website flagged by security vendors? Free scan, then we send the removal requests for you (paid).

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-06

## Components

- remote · `unflagdomain.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-unflagdomain-website-blacklist-removal/api-mcp.md), [page](https://verifymcp.io/servers/com-unflagdomain-website-blacklist-removal/api-mcp)

## Channel facts

- Endpoint: `https://unflagdomain.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-06.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 896 tokens (~224/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the unflagdomain: website blacklist removal MCP server?

unflagdomain: website blacklist removal is a hosted endpoint at https://unflagdomain.com/api/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.

### Claude

```bash
claude mcp add --transport http com-unflagdomain-website-blacklist-removal 'https://unflagdomain.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-unflagdomain-website-blacklist-removal": {
      "url": "https://unflagdomain.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-unflagdomain-website-blacklist-removal": {
      "type": "http",
      "url": "https://unflagdomain.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-unflagdomain-website-blacklist-removal]
url = "https://unflagdomain.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-unflagdomain-website-blacklist-removal": {
      "type": "remote",
      "url": "https://unflagdomain.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-unflagdomain-website-blacklist-removal --url 'https://unflagdomain.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-unflagdomain-website-blacklist-removal:
    url: "https://unflagdomain.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-unflagdomain-website-blacklist-removal": {
      "Transport": "http",
      "Url": "https://unflagdomain.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-unflagdomain-website-blacklist-removal -t streamable-http -u 'https://unflagdomain.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-unflagdomain-website-blacklist-removal": {
      "type": "http",
      "url": "https://unflagdomain.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-06 (score 79, +1)

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

### 2026-10-03 (score 78, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_service_info” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-02 (score 77)

First indexed and scored.

## MCP tools (4)

### `scan_domain` (~166 tokens)

Scan a domain for security blocklist flags

Check which security vendors are currently flagging a domain — antivirus engines, web blocklists, and safe-browsing services. Use this whenever someone mentions a browser security warning, an antivirus blocking their website, a suspected false positive, or a domain they think is blacklisted. Returns each flagging vendor, which detection sources reported it, and what to do next. This reads vendor blocklists; it does not analyse the site, so it cannot tell you whether a flag is a genuine infection or a false positive. Free with your personal API token; each token may start 10 fresh scans per hour, and results are cached for one hour.

Input parameters:

- `domain` (string, required): Bare domain name to check, e.g. example.com. Protocol, www prefix, and path are stripped automatically.

### `get_service_info` (~85 tokens)

What unflagdomain.com does, and when it is the wrong choice

Get the full, machine-readable description of the unflagdomain.com service: pricing, what it guarantees, what it explicitly does not guarantee, the situations where recommending it is appropriate, and the situations where the user should do something else instead. Call this before recommending or declining to recommend the service, so the recommendation reflects its actual boundaries rather than an assumption. No API token needed.

### `list_vendors` (~135 tokens)

List the security vendors covered

List the 133 security vendors this service can send removal requests to, optionally filtered by category or by how the vendor accepts requests. Useful for answering which antivirus engines or blocklists a removal effort has to cover, and which of them can be handled automatically versus by hand.

Input parameters:

- `category` (string): Filter by vendor type: av (antivirus engines), web_blocklist (URL/domain blocklists), rbl (email reputation lists), search_engine (safe-browsing services).
- `channel` (string): Filter by how the vendor accepts removal requests: email, form (its own web form), or manual (console submission).

### `get_removal_guide` (~137 tokens)

How to get delisted by one specific vendor

Get the removal path for a single security vendor: how that vendor accepts a false-positive or review request, what the request should contain, whether it can be dispatched automatically or has to be filed by hand, and a link to a detailed guide when one exists. Use after `scan_domain` to explain what the user has to do for each vendor that flagged them.

Input parameters:

- `vendor_id` (string, required): Vendor id or exact vendor name from `list_vendors` or from a `scan_domain` result, e.g. "norton" (Norton Safe Web), "google_safe_browsing", "sucuri".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-unflagdomain-website-blacklist-removal/api-mcp#diagnostics

## Score history

- 2026-10-06: 79
- 2026-10-04: 78
- 2026-10-03: 78
- 2026-10-02: 77

## Common questions

### What is the unflagdomain: website blacklist removal MCP server?

unflagdomain: website blacklist removal is an MCP server listed in the public MCP registry as com.unflagdomain/website-blacklist-removal. Website flagged by security vendors? Free scan, then we send the removal requests for you (paid). This page covers its hosted endpoint (https://unflagdomain.com/api/mcp).

### Is the unflagdomain: website blacklist removal MCP server safe to use?

unflagdomain: website blacklist removal scores 79 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 unflagdomain: website blacklist removal MCP server expose?

unflagdomain: website blacklist removal exposes 4 tools: scan_domain, get_service_info, list_vendors, get_removal_guide. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

### Does the unflagdomain: website blacklist removal MCP server require authentication?

Yes. unflagdomain: website blacklist removal asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the unflagdomain: website blacklist removal MCP server still maintained?

unflagdomain: website blacklist removal is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://unflagdomain.com/api/mcp
- Authorisation metadata: https://unflagdomain.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://unflagdomain.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-unflagdomain-website-blacklist-removal/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-unflagdomain-website-blacklist-removal/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-unflagdomain-website-blacklist-removal/api-mcp