net.lawyerd/takedown
REMOTE · MCP.LAWYERD.NET · SCANNED SEP 20
DMCA takedown & host reveal for AI agents: who hosts an infringing URL, even behind Cloudflare.
Available components
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 → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the net.lawyerd/takedown MCP server?
net.lawyerd/takedown is a hosted endpoint at https://mcp.lawyerd.net/takedown, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.lawyerd.net
claude mcp add --transport http net-lawyerd-takedown 'https://mcp.lawyerd.net/takedown'
{
"mcpServers": {
"net-lawyerd-takedown": {
"url": "https://mcp.lawyerd.net/takedown"
}
}
} {
"servers": {
"net-lawyerd-takedown": {
"type": "http",
"url": "https://mcp.lawyerd.net/takedown"
}
}
} [mcp_servers.net-lawyerd-takedown] url = "https://mcp.lawyerd.net/takedown"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-lawyerd-takedown": {
"type": "remote",
"url": "https://mcp.lawyerd.net/takedown",
"enabled": true
}
}
} openclaw mcp add net-lawyerd-takedown --url 'https://mcp.lawyerd.net/takedown' --transport streamable-http
mcp_servers:
net-lawyerd-takedown:
url: "https://mcp.lawyerd.net/takedown" {
"McpServers": {
"net-lawyerd-takedown": {
"Transport": "http",
"Url": "https://mcp.lawyerd.net/takedown"
}
}
} assistant mcp add net-lawyerd-takedown -t streamable-http -u 'https://mcp.lawyerd.net/takedown'
{
"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.
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.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 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 0
First indexed and scored.
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 20 Sept 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 | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5dba7bc04896a75b51e94ce0ed47b5aa392 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_takedown Assess a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| fileable | boolean | yes | – |
| legalNotes | array | yes | – |
| nextStep | string | yes | – |
| process | array | yes | – |
| requiredFromYou | array | yes | – |
| route | string | yes | – |
| target | string | yes | – |
| url | string | yes | – |
No examples provided.
preserve_evidence Preserve a page as 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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company or the work being protected |
| string | yes | The USER'S OWN email — the evidence package is delivered there | |
| name | string | – | Requester's name (appears in the capture record) |
| url | string | yes | The public page URL to preserve |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
| alreadyCaptured | boolean | yes | – |
| captureId | string|null | yes | – |
| deliveredTo | string|null | yes | – |
| errorCode | string|null | yes | – |
| nextStep | string | yes | – |
| url | string | yes | – |
| verificationUrl | string|null | yes | – |
| whatHappensNext | array | yes | – |
No examples provided.
resolve_host Resolve host & abuse contact ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The infringing URL or bare domain |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| frontedBy | string | yes | – |
| host | – | yes | – |
| nextStep | string | yes | – |
| platform | – | yes | – |
| proxy | – | yes | – |
| realHostHidden | boolean | yes | – |
| revealSource | – | yes | – |
| takedownRoute | string | yes | – |
| url | string | yes | – |
No examples provided.
start_takedown Start a takedown (onboarding link) ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The infringing URL or bare domain |
| Name | Type | Req | Description |
|---|---|---|---|
| humanNote | string | yes | – |
| nextStep | string | yes | – |
| onboardingUrl | string | yes | – |
| url | string | yes | – |
| whatHappensNext | array | yes | – |
| whatToPrepare | array | yes | – |
No examples provided.
What is the net.lawyerd/takedown MCP server?
net.lawyerd/takedown is an MCP server listed in the public MCP registry as net.lawyerd/takedown. DMCA takedown & host reveal for AI agents: who hosts an infringing URL, even behind Cloudflare. This page covers its hosted endpoint (https://mcp.lawyerd.net/takedown).
Is the net.lawyerd/takedown MCP server safe to use?
net.lawyerd/takedown scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the net.lawyerd/takedown MCP server expose?
net.lawyerd/takedown exposes 4 tools: resolve_host, assess_takedown, start_takedown, preserve_evidence. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.
Does the net.lawyerd/takedown MCP server require authentication?
No. We connected to net.lawyerd/takedown without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the net.lawyerd/takedown MCP server still maintained?
net.lawyerd/takedown is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.