# DMCA.com Cases (npm · dmca-cases-mcp)

DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.dmca.com`: 75/100, [markdown](https://verifymcp.io/servers/com-dmca-dmca-cases/runtime-webhooks-mcp.md), [page](https://verifymcp.io/servers/com-dmca-dmca-cases/runtime-webhooks-mcp)
- npm · `dmca-cases-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp.md), [page](https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp)

## Channel facts

- Registry: `npm`
- Package: `dmca-cases-mcp`
- Version: `1.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-dmca-dmca-cases -- npx -y dmca-cases-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-dmca-dmca-cases": {
      "command": "npx",
      "args": [
        "-y",
        "dmca-cases-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dmca-dmca-cases": {
      "command": "npx",
      "args": [
        "-y",
        "dmca-cases-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-dmca-dmca-cases -- npx -y dmca-cases-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dmca-dmca-cases": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dmca-cases-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dmca-dmca-cases --command npx --arg -y --arg dmca-cases-mcp
```

### Hermes

```yaml
mcp_servers:
  com-dmca-dmca-cases:
    command: "npx"
    args: ["-y", "dmca-cases-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-dmca-dmca-cases": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dmca-cases-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dmca-dmca-cases -t stdio -c npx -a -y dmca-cases-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-dmca-dmca-cases": {
      "command": "npx",
      "args": [
        "-y",
        "dmca-cases-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 75, +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.

### 2026-11-03 (score 74, +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.

### 2026-11-01 (score 73, +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.

### 2026-10-30 (score 72, +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.

### 2026-10-28 (score 71, +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.

### 2026-10-25 (score 70, +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.

### 2026-10-24 (score 69, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 74, +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.

## MCP tools (10)

### `listCases` (~80 tokens)

GET https://api.dmca.com/listCases — list managed takedown cases for the account. Optional page (max 50 per page).

Input parameters:

- `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.

### `listDIYCases` (~91 tokens)

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.

Input parameters:

- `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.

### `listComplianceCases` (~79 tokens)

GET https://api.dmca.com/listComplianceCases — list compliance cases for the account. Optional page (max 50 per page).

Input parameters:

- `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.

### `getCaseById` (~77 tokens)

GET https://api.dmca.com/getCaseById?id= — fetch a single case owned by the API account.

Input parameters:

- `id` (string, required): 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.

### `login` (~82 tokens)

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.

Input parameters:

- `email` (string, required): DMCA.com account email.
- `password` (string, required): DMCA.com account password. Never logged.

### `createCase` (~123 tokens)

POST https://api.dmca.com/createCase — create a managed takedown case. Uses the session/`token` DMCA API token.

Input parameters:

- `copiedFromUrl` (string): Optional original / copied-from URL.
- `description` (string, required): Case description.
- `infringingSiteIp` (string): Optional infringing site IP.
- `infringingUrl` (string): Optional infringing URL.
- `subject` (string, required): Case subject.
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.

### `updateCase` (~180 tokens)

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.

Input parameters:

- `case_id` (string, required): Case ID to update.
- `copiedFromUrl` (string): Optional original / copied-from URL.
- `description` (string, required): 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, required): Case subject.
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.

### `createDIYCase` (~158 tokens)

POST https://api.dmca.com/createDIYCase — create a DIY case. Uses the session/`token` DMCA API token.

Input parameters:

- `copiedFromUrl` (string): Optional original / copied-from URL.
- `description` (string, required): Case description.
- `infringingSiteIp` (string): Optional infringing site IP.
- `infringingUrl` (string): Optional infringing URL.
- `subject` (string, required): Case subject.
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.
- `type` (string, required): DIY case type: Business - General | Personal - General | Toolkit Business Request CAN|EU|India | Toolkit Personal Request CAN|EU|India.

### `createComplianceCase` (~201 tokens)

POST https://api.dmca.com/createComplianceCase — create a compliance case. siteId site owner must have feature enabled. Uses the session/`token` DMCA API token.

Input parameters:

- `copiedFromUrl` (string): Optional original / copied-from URL.
- `description` (string, required): Case description.
- `infringingSiteIp` (string): Optional infringing site IP.
- `infringingUrl` (string): Optional infringing URL.
- `siteId` (string, required): Id of the site the case is submitted to (site owner must have feature enabled).
- `submitterCompanyName` (string): Optional submitter company name.
- `submitterEmail` (string, required): Submitter email.
- `submitterFirstName` (string, required): Submitter first name.
- `submitterLastName` (string, required): Submitter last name.
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.

### `getSiteReport` (~84 tokens)

GET https://api.dmca.com/getSiteReport/{domain} — site report for a fully qualified domain name. Uses the session/`token` DMCA API token.

Input parameters:

- `domain` (string, required): Fully qualified domain name (upstream path segment).
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 69
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-11: 38
- 2026-10-09: 38

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/dmca-cases-mcp
- Socket report: https://socket.dev/npm/package/dmca-cases-mcp
- Repository: https://github.com/NetroDev/dmca-cases-public-mcp
- Website: https://mcp.dmca.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-dmca-dmca-cases/dmca-cases-mcp