DMCA.com Cases
NPM · DMCA-CASES-MCP · 2 COMPONENTS
DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token.
Available components
Last scanned (17 hours ago)
Scores higher than 51% of npm servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1155 tokens (~115/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 Management73
- Stability observed for 22 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 10 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 · Analysed npm/dmca-cases-mcp@1.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~123
POST https://api.dmca.com/createCase — create a 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 ~201
POST https://api.dmca.com/createComplianceCase — create a 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 ~158
POST https://api.dmca.com/createDIYCase — create a 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 ~77
GET https://api.dmca.com/getCaseById?id= — fetch a single case owned by the API account.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Case ID returned by listCases / createCase (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 ~84
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 segment). |
| 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 ~80
GET https://api.dmca.com/listCases — list managed takedown cases for the account. Optional page (max 50 per page).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Optional page number for paging (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 ~79
GET https://api.dmca.com/listComplianceCases — list compliance cases for the account. Optional page (max 50 per page).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Optional page number for paging (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 ~91
GET https://api.dmca.com/listDIYCases — list DIY cases for the account. Optional page (max 50 per page). An empty account comes back as an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Optional page number for paging (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 ~82
POST https://api.dmca.com/login — authenticate with email/password (no Token header). Returns the DMCA API token; it is reused automatically for the rest of this session, or pass it as `token`. Password is 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 ~180
POST https://api.dmca.com/updateCase — update an existing 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 runs locally as an npm package, launched with npx -y dmca-cases-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dmca-cases-mcp
claude mcp add com-dmca-dmca-cases -- npx -y dmca-cases-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 npm package (dmca-cases-mcp).
Is the DMCA.com Cases MCP server safe to use?
DMCA.com Cases scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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: listCases, listDIYCases, listComplianceCases, getCaseById, login, and 5 more. Their descriptions and schemas cost roughly 1,155 tokens of context every time the server is loaded.
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 licence is the DMCA.com Cases MCP server under?
DMCA.com Cases declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the DMCA.com Cases MCP server?
VerifyMCP ran 16 checks on DMCA.com Cases, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.