# takedown

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/lawyerd999/dmca-takedown-mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/takedown-2

## Description
DMCA takedown & host reveal for AI agents: who hosts an infringing URL, even behind Cloudflare.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "takedown": {
    "command": "npx",
    "args": ["-y","takedown-2"]
  }
}
```

## Documentation & README

# DMCA Takedown MCP Server

> **The first DMCA takedown & host-reveal [MCP](https://modelcontextprotocol.io) server.**
> Connect it to Claude (or any MCP client) and your AI agent can answer:
> *“who really hosts this infringing site — even behind Cloudflare — where does
> the DMCA/abuse notice go, and how do I actually get it taken down?”*

Hosted and operated by [Lawyerd](https://lawyerd.net), a counsel-led content-removal
practice. This repository is the public home and documentation for the server;
it is a **remote, hosted MCP server** — there is nothing to install or run
yourself. Just point your agent at the endpoint.

- **Endpoint:** `https://mcp.lawyerd.net/takedown` (Streamable HTTP)
- **Alias:** `https://mcp.lawyerd.net/mcp`
- **Registry:** [`net.lawyerd/takedown`](https://registry.modelcontextprotocol.io/v0/servers?search=lawyerd) in the official MCP Registry
- **Cost:** free, no account, rate-limited
- **Discovery:** [`/.well-known/mcp.json`](https://mcp.lawyerd.net/.well-known/mcp.json)

---

## Quick start

Add the server to Claude Code / Claude Desktop:

```bash
claude mcp add --transport http lawyerd https://mcp.lawyerd.net/takedown
```

Or add it to any MCP client config (`mcpServers`):

```json
{
  "mcpServers": {
    "lawyerd": {
      "type": "http",
      "url": "https://mcp.lawyerd.net/takedown"
    }
  }
}
```

Then just ask your assistant, in your own words:

> *“Someone reposted my photo set and is selling prints at `https://example-infringer.com`.
> Who hosts it and how do I take it down?”*

The agent chains the three tools below and hands you a plain-language answer.

---

## Tools

### `resolve_host`
Look up who hosts a URL and where a DMCA/abuse notice would go. Identifies the
platform, the CDN/proxy in front (e.g. **Cloudflare**, DDoS-Guard), or the
direct hosting provider and its abuse contact. For domains whose real host has
already been revealed from behind a proxy, it returns that host immediately;
for a domain still hidden behind a proxy it says so honestly — revealing the
true host means initiating an abuse report. **Read-only; files nothing.**

### `assess_takedown`
The plan for a takedown of a specific URL: the route it would follow (host
abuse, platform form, or reveal-first), what the rights holder must supply
(proof of ownership and a one-time signed attestation), the step-by-step
process, and the legal caveats — including **17 U.S.C. §512(f)** and scope
limits. Read-only; it does not judge the merits of the claim.

### `start_takedown`
Returns a secure onboarding link to actually begin a takedown. A human opens
it once in a browser to identify themselves, sign the authorization (the one
step that legally requires a human), and provide proof of ownership. **Nothing
is filed by the agent.**

---

## Example

```jsonc
// tools/call → resolve_host  { "url": "https://example-infringer.com" }
{
  "domain": "example-infringer.com",
  "frontedBy": "cdn_proxy",
  "proxy": { "name": "Cloudflare" },
  "realHostHidden": true,
  "takedownRoute": "needs_reveal",
  "nextStep": "The site is behind Cloudflare — the real host is hidden. Revealing it requires initiating an abuse report; start a takedown to do that."
}
```

For a domain already revealed, `resolve_host` returns the real host and its
abuse email directly, with `revealSource: "cached_reveal"`.

---

## What this is — and is not

- ✅ A **lookup and planning** layer for DMCA / abuse takedowns, callable by AI agents.
- ✅ Honest about what it knows: it never invents an abuse contact, and it does
  not claim a synchronous “reveal behind Cloudflare” it cannot actually perform
  without filing.
- ❌ **Not** an auto-filing bot. A DMCA notice is signed by the rights holder
  under penalty of perjury; that signature is always made by a human.
- ❌ **Not** legal advice, and it does not guarantee removal.
- ❌ **Not** a tool for suppressing lawful content. Copyright, trademark and
  brand-impersonation matters only — lawful criticism, reviews and journalism
  are declined at intake.

The actual enforcement — revealing the real host, filing the notice, following
up, and confirming the content is genuinely gone — is done by Lawyerd under
qualified counsel. The MCP server is the front door; [lawyerd.net](https://lawyerd.net)
is the practice behind it.

---

## Keywords

DMCA takedown · MCP server · Model Context Protocol · AI agent · host reveal ·
find the real host behind Cloudflare · abuse contact lookup · copyright
takedown · brand protection · content removal · Claude · takedown automation.

## Links

- Website: <https://lawyerd.net>
- MCP endpoint: <https://mcp.lawyerd.net/takedown>
- Official MCP Registry entry: <https://registry.modelcontextprotocol.io/v0/servers?search=lawyerd>
- Model Context Protocol: <https://modelcontextprotocol.io>
- Contact: dmca@lawyerd.net

## License

Documentation in this repository is released under the [MIT License](https://github.com/lawyerd999/dmca-takedown-mcp/blob/HEAD/LICENSE).
The hosted service, its tool implementations and the underlying host-resolution
data are proprietary to Lawyerd and are **not** included here.

