Skip to content

takedown MCP server

net.lawyerd/takedownlawyerd.netstreamable-httpv0.2.2Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 4
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the takedown MCP server can do

The takedown MCP server is published by lawyerd.net, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: assess_takedown and start_takedown), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (resolve_host, assess_takedown and preserve_evidence); 4 tools can send data out of your system (resolve_host, assess_takedown, start_takedown and 1 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.2.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • assess_takedownAssess 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 o…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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. The hosting answer alone is what resolve_host returns. The url is the site to look up, not an API endpoint: the lookup runs on Lawyerd's own host-resolution API (documentation: https://mcp.lawyerd.net/).

    Annotations the server declares

    • title: Assess a takedown
    • readOnlyHint: true
    • openWorldHint: true
  • start_takedownGet the link to Lawyerd's intake form — the way to actually start a takedown.Can send data out1 finding

    Why it is in this group

    • The name "start_takedown" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "start_takedown" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "start_takedown" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get the link to Lawyerd's intake form — the way to actually start a takedown. Read-only: returns the link plus what to prepare and what happens next; it creates nothing and files nothing. The content owner opens the link in a browser and sends the request; before any notice is filed, Lawyerd checks ownership and the owner signs a one-time authorization (the one step that legally requires a human). Requests targeting lawful criticism, reviews or journalism are declined at intake. Documentation: https://mcp.lawyerd.net/.

    Annotations the server declares

    • title: Start a takedown (intake link)
    • readOnlyHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • preserve_evidenceGet the link to Lawyerd's free evidence-capture form for a public web page the user wants preserved before it disappears.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "web": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Get the link to Lawyerd's free evidence-capture form for a public web page the user wants preserved before it disappears. Read-only: this tool captures nothing and sends nothing — it returns the form link (https://lawyerd.net/evidence/) and what the capture package contains. The user starts the capture there with their own email after a quick human check (free: 3/day, 10/month per email); the package — full-page screenshot, raw and rendered HTML, HTTP headers, hosting/registrar context, SHA-256 hashes of every artifact, an OpenTimestamps anchor and an Internet Archive snapshot — is emailed to them. Use when the user wants to "save proof" or a "screenshot for court" of a scam or infringing page before a takedown. Public pages only (no logins/paywalls). Not notarization.

    Annotations the server declares

    • title: Preserve a page as evidence (capture link)
    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true
  • resolve_hostLook up who hosts a URL and where an abuse/takedown notice would go.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "resolve_host" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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. The url is the site to look up, not an API endpoint: the lookup runs on Lawyerd's own host-resolution API (documentation: https://mcp.lawyerd.net/).

    Annotations the server declares

    • title: Resolve host & abuse contact
    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.lawyerd.net/takedown: tools/list returned 4 tools to an anonymous client, including assess_takedown (write), start_takedown (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 3 to 2

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "start_takedown" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "start_takedown" says "start": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 2.View diff
    • Tools that change things, listed without credentials: 3 to 2

Install

Pinned to version 0.2.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__takedown__resolve_host",
      "mcp__takedown__assess_takedown",
      "mcp__takedown__start_takedown",
      "mcp__takedown__preserve_evidence"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as takedown. Review it before you use it.

Capability tags behind 4 rules
  • mcp__takedown__resolve_host untrusted-input, outbound
  • mcp__takedown__assess_takedown untrusted-input, outbound
  • mcp__takedown__start_takedown outbound
  • mcp__takedown__preserve_evidence untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.lawyerd/takedown/verify?hash=c0db9a943e55240e17c84c628201691877bcee704bc1b19f154f22d0de126057" | jq -e '.changed == false'

Pinned hash c0db9a943e55, from Nov 18, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.lawyerd/takedown/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.lawyerd/takedown
[![Anlyon Radar](https://radar.anlyon.com/badge/net.lawyerd/takedown.svg)](https://radar.anlyon.com/servers/net.lawyerd/takedown)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

takedown MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the takedown MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the takedown MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the takedown MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the takedown MCP server have?

4 tools: 2 write, 2 read. assess_takedown, start_takedown, resolve_host and preserve_evidence.

Does the takedown MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the takedown MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resolve_host, assess_takedown, start_takedown and preserve_evidence.

Has the takedown MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.