Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

unflagdomain: website blacklist removal

REMOTE · UNFLAGDOMAIN.COM

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

Available components

0 this week 90 Trust /100

Last scanned (12 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1239 tokens (~309/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 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. DS published 19718 13 Verified
unflagdomain.com. DS published 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 301 https://unflagdomain.com/api/mcp
MCP tools · 4 exposed · ~649 tokens

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 →

Tool Tokens
get_removal_guide ~172

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 it after `scan_domain` to explain what the user has to do for each vendor that flagged them, or directly when the person already names the product that blocks them ("ESET blocks my site", "Bitdefender says dangerous page", "Norton flagged my website").

NameTypeReqDescription
vendor_idstringyesVendor 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 ~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 ~148

List the 136 security vendors this service can send removal requests to, optionally filtered by category or by how the vendor accepts requests. Use it when someone asks whether the antivirus, web filter or blocklist that blocks them is covered, or which vendors a removal effort has to reach and which of them can be handled automatically versus by hand.

NameTypeReqDescription
categorystring–Filter by vendor type: av (antivirus engines), web_blocklist (URL/domain blocklists), rbl (email reputation lists), search_engine (safe-browsing services).
channelstring–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 ~244

Find out which security vendors are listing a domain right now — antivirus engines, web filters, URL blocklists and safe-browsing services — with each source's own report page as proof. Call this when someone says their website is blocked or flagged and a domain is known, whatever words they use: an antivirus blocks their site (ESET "Access denied", Bitdefender "Dangerous page blocked", Norton, McAfee, Kaspersky), an internet provider or company firewall blocks it, a genuine login page is marked "phishing", a browser shows "Deceptive site ahead", ads were rejected over the landing page, or warnings persist after a cleanup. 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.

NameTypeReqDescription
domainstringyesBare domain name to check, e.g. example.com. Protocol, www prefix, and path are stripped automatically.

No output schema declared.

No examples provided.

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.

remote · unflagdomain.com

# add to Claude Code
claude mcp add --transport http com-unflagdomain-website-blacklist-removal 'https://unflagdomain.com/api/mcp'
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 90 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 649 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the unflagdomain: website blacklist removal MCP server?

VerifyMCP ran 13 checks on unflagdomain: website blacklist removal, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.