# net.lawyerd/takedown (remote · mcp.lawyerd.net)

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

- Trust score: 66/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.lawyerd.net`: 66/100 (this document), [markdown](https://verifymcp.io/servers/net-lawyerd-takedown/takedown.md), [page](https://verifymcp.io/servers/net-lawyerd-takedown/takedown)

## Channel facts

- Endpoint: `https://mcp.lawyerd.net/takedown`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.2`

## 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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 588 tokens (~147/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**: 27/100
  - Stability observed for 8 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.net-lawyerd-takedown]
url = "https://mcp.lawyerd.net/takedown"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-lawyerd-takedown": {
      "type": "remote",
      "url": "https://mcp.lawyerd.net/takedown",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-lawyerd-takedown --url https://mcp.lawyerd.net/takedown --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-lawyerd-takedown:
    url: "https://mcp.lawyerd.net/takedown"
```

### Other

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

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-08-02 (score 66, +1)

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

### 2026-07-31 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

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

### 2026-07-28 (score 65, +1)

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

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (4)

### `resolve_host` (~121 tokens)

Resolve host & abuse contact

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.

Input parameters:

- `url` (string, required): The infringing URL or bare domain

Output parameters:

- `domain` (string)
- `frontedBy` (string)
- `host`
- `nextStep` (string)
- `platform`
- `proxy`
- `realHostHidden` (boolean)
- `revealSource`
- `takedownRoute` (string)
- `url` (string)

### `assess_takedown` (~146 tokens)

Assess a takedown

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.

Input parameters:

- `url` (string, required): The infringing URL or bare domain
- `what` (string): One line on what was copied (e.g. "my photo set", "my course videos") — echoed into the plan, not judged

Output parameters:

- `domain` (string)
- `fileable` (boolean)
- `legalNotes` (array)
- `nextStep` (string)
- `process` (array)
- `requiredFromYou` (array)
- `route` (string)
- `target` (string)
- `url` (string)

### `start_takedown` (~100 tokens)

Start a takedown (onboarding link)

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.

Input parameters:

- `url` (string, required): The infringing URL or bare domain

Output parameters:

- `humanNote` (string)
- `nextStep` (string)
- `onboardingUrl` (string)
- `url` (string)
- `whatHappensNext` (array)
- `whatToPrepare` (array)

### `preserve_evidence` (~221 tokens)

Preserve a page as evidence

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.

Input parameters:

- `company` (string): Company or the work being protected
- `email` (string, required): The USER'S OWN email — the evidence package is delivered there
- `name` (string): Requester's name (appears in the capture record)
- `url` (string, required): The public page URL to preserve

Output parameters:

- `accepted` (boolean)
- `alreadyCaptured` (boolean)
- `captureId` (string|null)
- `deliveredTo` (string|null)
- `errorCode` (string|null)
- `nextStep` (string)
- `url` (string)
- `verificationUrl` (string|null)
- `whatHappensNext` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-lawyerd-takedown/takedown#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 65
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://mcp.lawyerd.net/takedown
- Repository: https://github.com/lawyerd999/dmca-takedown-mcp
- Changelog RSS feed: https://verifymcp.io/servers/net-lawyerd-takedown/takedown/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-lawyerd-takedown/takedown/changelog.json
- HTML version of this page: https://verifymcp.io/servers/net-lawyerd-takedown/takedown