dmca-takedown-mcp

Assess how a takedown for this URL would proceed: where the notice goes (host, platform, or a hidden host that must be revealed first), what documents and attestation the content owner must supply, the step-by-step process, and the legal caveats (§512(f), scope limits). Read-only; does not judge the merits of the claim and files nothing. Use resolve_host first if you only need the hosting answer.

Preserve a public web page as evidence BEFORE it disappears: a forensic-grade package — full-page screenshot, raw and rendered HTML, HTTP headers, hosting/registrar context, SHA-256 hashes of every artifact, an OpenTimestamps Bitcoin anchor and an Internet Archive snapshot — delivered to the USER'S OWN email in ~2 minutes (free: 3/day, 10/month per email). Use when the user wants to "save proof", "screenshot for court" or fix a scam/infringing page before takedown. Sends one email to the address given; captures only public pages (no logins/paywalls); lawful preservation only. Not notarization — Lawyerd counsel can add a signed declaration of the capture procedure on request.

Look up who hosts a URL and where an abuse/takedown notice would go. Identifies the CDN/proxy in front (e.g. Cloudflare), the platform, or the direct host and its abuse contact. For direct hosts and previously-revealed domains it returns the real host immediately; for a domain hidden behind a proxy it explains that revealing the true host requires initiating an abuse report. Read-only; files nothing. A lookup, not legal advice; it does not guarantee removal.

Get the secure onboarding link to actually start a takedown. The content owner opens it once in a browser to identify themselves, sign the standing authorization (the one step that legally requires a human), and provide proof of ownership. Returns the link plus what to prepare and what happens next. Creates nothing by itself; filings targeting lawful criticism, reviews or journalism are declined at intake.