unflagdomain: website blacklist removal
REMOTE · UNFLAGDOMAIN.COM · SCANNED OCT 6
Website flagged by security vendors? Free scan, then we send the removal requests for you (paid).
Available components
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. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · unflagdomain.com
claude mcp add --transport http com-unflagdomain-website-blacklist-removal 'https://unflagdomain.com/api/mcp'
{
"mcpServers": {
"com-unflagdomain-website-blacklist-removal": {
"url": "https://unflagdomain.com/api/mcp"
}
}
} {
"servers": {
"com-unflagdomain-website-blacklist-removal": {
"type": "http",
"url": "https://unflagdomain.com/api/mcp"
}
}
} [mcp_servers.com-unflagdomain-website-blacklist-removal] url = "https://unflagdomain.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-unflagdomain-website-blacklist-removal": {
"type": "remote",
"url": "https://unflagdomain.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-unflagdomain-website-blacklist-removal --url 'https://unflagdomain.com/api/mcp' --transport streamable-http
mcp_servers:
com-unflagdomain-website-blacklist-removal:
url: "https://unflagdomain.com/api/mcp" {
"McpServers": {
"com-unflagdomain-website-blacklist-removal": {
"Transport": "http",
"Url": "https://unflagdomain.com/api/mcp"
}
}
} assistant mcp add com-unflagdomain-website-blacklist-removal -t streamable-http -u 'https://unflagdomain.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Oct 26 +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.
- 3 Oct 26 +1
- 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 security
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://unflagdomain.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=unflagdomain.com | CN=YE1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6a304231958af0dcdce5421cd0f3b371f61 |
| SANs: *.unflagdomain.com, unflagdomain.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of unflagdomain.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| unflagdomain.com. | present | 2371 | 13 | Verified |
| unflagdomain.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="unflagdomain", error="invalid_token", error_description="missing"
Bearer realm="unflagdomain", error="invalid_token", error_description="missing"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://*.posthog.com https://www.googletagmanager.com https://c.oa.dev.hubtech.sk; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.google-analytics.com https://www.googletagmanager.com; font-src 'self'; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://*.posthog.com https://*.google-analytics.com https://www.google-analytics.com https://www.googletagmanager.com https://c.oa.dev.hubtech.sk http://127.0.0.1:54321 ws://127.0.0.1:54321; frame-src https://js.stripe.com https://hooks.stripe.com; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://unflagdomain.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://unflagdomain.com/api/mcp | HTTPS enforced | 302 | https://unflagdomain.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_removal_guide How to get delisted by one specific vendor ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor_id | string | yes | 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". |
No output schema declared.
No examples provided.
get_service_info What unflagdomain.com does, and when it is the wrong choice ~85
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_vendors List the security vendors covered ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
scan_domain Scan a domain for security blocklist flags ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain name to check, e.g. example.com. Protocol, www prefix, and path are stripped automatically. |
No output schema declared.
No examples provided.
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.