DMCA.com Cases
REMOTE · MCP.DMCA.COM · 2 COMPONENTS
DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token.
Available components
Last scanned (12 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 10 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1313 tokens (~131/item across 10 items; 10 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 Management97
- Stability observed for 29 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://mcp.dmca.com/runtime/webhooks/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.dmca.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 7 Oct 2026 | 7 Apr 2027 | RSA 2048 | SHA256-RSA | 2f7b9eadf7ee2b59b1872fb9c238455 |
| SANs: mcp.dmca.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.dmca.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| dmca.com. | No DS | 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.dmca.com/runtime/webhooks/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.dmca.com/runtime/webhooks/mcp | HTTPS enforced | 301 | https://mcp.dmca.com/runtime/webhooks/mcp |
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 →
createCase ~122
POST https://api.dmca.com/createCase — create managed takedown case. Uses the session/`token` DMCA API token.
| Name | Type | Req | Description |
|---|---|---|---|
| copiedFromUrl | string | – | Optional original / copied-from URL. |
| description | string | yes | Case description. |
| infringingSiteIp | string | – | Optional infringing site IP. |
| infringingUrl | string | – | Optional infringing URL. |
| subject | string | yes | Case subject. |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
createComplianceCase ~200
POST https://api.dmca.com/createComplianceCase — create compliance case. siteId site owner must have feature enabled. Uses the session/`token` DMCA API token.
| Name | Type | Req | Description |
|---|---|---|---|
| copiedFromUrl | string | – | Optional original / copied-from URL. |
| description | string | yes | Case description. |
| infringingSiteIp | string | – | Optional infringing site IP. |
| infringingUrl | string | – | Optional infringing URL. |
| siteId | string | yes | Id of the site the case is submitted to (site owner must have feature enabled). |
| submitterCompanyName | string | – | Optional submitter company name. |
| submitterEmail | string | yes | Submitter email. |
| submitterFirstName | string | yes | Submitter first name. |
| submitterLastName | string | yes | Submitter last name. |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
createDIYCase ~157
POST https://api.dmca.com/createDIYCase — create DIY case. Uses the session/`token` DMCA API token.
| Name | Type | Req | Description |
|---|---|---|---|
| copiedFromUrl | string | – | Optional original / copied-from URL. |
| description | string | yes | Case description. |
| infringingSiteIp | string | – | Optional infringing site IP. |
| infringingUrl | string | – | Optional infringing URL. |
| subject | string | yes | Case subject. |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
| type | string | yes | DIY case type: Business - General | Personal - General | Toolkit Business Request CAN|EU|India | Toolkit Personal Request CAN|EU|India. |
No output schema declared.
No examples provided.
getCaseById ~70
GET https://api.dmca.com/getCaseById?id= — fetch one case by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Case ID returned by listCases (or equivalent). |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
getSiteReport ~90
GET https://api.dmca.com/getSiteReport/{domain} — site report for a fully qualified domain name. Uses the session/`token` DMCA API token.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Fully qualified domain name (upstream path /getSiteReport/{domain}). |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
listCases ~69
GET https://api.dmca.com/listCases — list managed takedown cases. Optional page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional page number (max 50 results per page). |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
listComplianceCases ~68
GET https://api.dmca.com/listComplianceCases — list compliance cases. Optional page.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional page number (max 50 results per page). |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
listDIYCases ~80
GET https://api.dmca.com/listDIYCases — list DIY cases. Optional page. An empty account comes back as an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Optional page number (max 50 results per page). |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
login ~80
POST https://api.dmca.com/login — email/password, no Token header. Returns the DMCA API token; it is reused automatically for the rest of this MCP session, or pass it as `token`. Password never logged.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | DMCA.com account email. | |
| password | string | yes | DMCA.com account password. Never logged. |
No output schema declared.
No examples provided.
updateCase ~178
POST https://api.dmca.com/updateCase — update managed takedown case. Status and priority are kept as they are unless you pass them. Uses the session/`token` DMCA API token.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | Case ID to update. |
| copiedFromUrl | string | – | Optional original / copied-from URL. |
| description | string | yes | Case description. |
| infringingSiteIp | string | – | Optional infringing site IP. |
| infringingUrl | string | – | Optional infringing URL. |
| priority | string | – | Optional new priority. Left unchanged when omitted. |
| status | string | – | Optional new case status. Left unchanged when omitted. |
| subject | string | yes | Case subject. |
| token | string | – | DMCA API token from the login tool; optional if the server/session already has one. |
No output schema declared.
No examples provided.
How do I install the DMCA.com Cases MCP server?
DMCA.com Cases is a hosted endpoint at https://mcp.dmca.com/runtime/webhooks/mcp, 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.dmca.com
claude mcp add --transport http com-dmca-dmca-cases 'https://mcp.dmca.com/runtime/webhooks/mcp'
What is the DMCA.com Cases MCP server?
DMCA.com Cases is an MCP server listed in the public MCP registry as com.dmca/dmca-cases. DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token. This page covers its hosted endpoint (https://mcp.dmca.com/runtime/webhooks/mcp).
Is the DMCA.com Cases MCP server safe to use?
DMCA.com Cases scores 75 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 DMCA.com Cases MCP server expose?
DMCA.com Cases exposes 10 tools: createCase, createComplianceCase, createDIYCase, getCaseById, getSiteReport, and 5 more. Their descriptions and schemas cost roughly 1,114 tokens of context every time the server is loaded.
Does the DMCA.com Cases MCP server require authentication?
No. We connected to DMCA.com Cases without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DMCA.com Cases MCP server still maintained?
DMCA.com Cases is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the DMCA.com Cases MCP server?
VerifyMCP ran 12 checks on DMCA.com Cases, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about DMCA.com Cases: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.