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

net.lawyerd/takedown

REMOTE · MCP.LAWYERD.NET · SCANNED AUG 3

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

Available components

+2 this week 66 Trust /100
Trust breakdown (6 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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.lawyerd.net

# add to Claude Code
claude mcp add --transport http net-lawyerd-takedown https://mcp.lawyerd.net/takedown
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add net-lawyerd-takedown --url https://mcp.lawyerd.net/takedown --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-lawyerd-takedown:
    url: "https://mcp.lawyerd.net/takedown"
// mcp.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 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.

  • 2 Aug 26 +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.

  • 31 Jul 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
  • 30 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +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.

  • 28 Jul 26 +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.

  • 27 Jul 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
  • 26 Jul 26 64

    First indexed and scored.

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 3 Aug 2026 · Probed https://mcp.lawyerd.net/takedown

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.lawyerd.net CN=YE2,O=Let's Encrypt,C=US 2 Jul 2026 30 Sept 2026 ECDSA 256 ECDSA-SHA384 5f4dfcba7fdc20d8e7ed4332644cd5448d7
SANs: mcp.lawyerd.net
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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
DNSSEC insecure

Validation of mcp.lawyerd.net. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
lawyerd.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.lawyerd.net/takedown Verified 200
http (plaintext) http://mcp.lawyerd.net/takedown HTTPS enforced 301 https://mcp.lawyerd.net/takedown
MCP tools — 4 exposed · ~588 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.

Tool Tokens
assess_takedown ~146

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.

NameTypeReqDescription
urlstringyesThe infringing URL or bare domain
whatstringOne line on what was copied (e.g. "my photo set", "my course videos") — echoed into the plan, not judged
NameTypeReqDescription
domainstringyes
fileablebooleanyes
legalNotesarrayyes
nextStepstringyes
processarrayyes
requiredFromYouarrayyes
routestringyes
targetstringyes
urlstringyes

No examples provided.

preserve_evidence ~221

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.

NameTypeReqDescription
companystringCompany or the work being protected
emailstringyesThe USER'S OWN email — the evidence package is delivered there
namestringRequester's name (appears in the capture record)
urlstringyesThe public page URL to preserve
NameTypeReqDescription
acceptedbooleanyes
alreadyCapturedbooleanyes
captureIdstring|nullyes
deliveredTostring|nullyes
errorCodestring|nullyes
nextStepstringyes
urlstringyes
verificationUrlstring|nullyes
whatHappensNextarrayyes

No examples provided.

resolve_host ~121

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.

NameTypeReqDescription
urlstringyesThe infringing URL or bare domain
NameTypeReqDescription
domainstringyes
frontedBystringyes
hostyes
nextStepstringyes
platformyes
proxyyes
realHostHiddenbooleanyes
revealSourceyes
takedownRoutestringyes
urlstringyes

No examples provided.

start_takedown ~100

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.

NameTypeReqDescription
urlstringyesThe infringing URL or bare domain
NameTypeReqDescription
humanNotestringyes
nextStepstringyes
onboardingUrlstringyes
urlstringyes
whatHappensNextarrayyes
whatToPreparearrayyes

No examples provided.