# DMCA.com Cases (remote · mcp.dmca.com)

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

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

## Components

- remote · `mcp.dmca.com`: 75/100 (this document), [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, [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

- Endpoint: `https://mcp.dmca.com/runtime/webhooks/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http com-dmca-dmca-cases 'https://mcp.dmca.com/runtime/webhooks/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dmca-dmca-cases": {
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dmca-dmca-cases": {
      "type": "http",
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dmca-dmca-cases]
url = "https://mcp.dmca.com/runtime/webhooks/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dmca-dmca-cases": {
      "type": "remote",
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dmca-dmca-cases --url 'https://mcp.dmca.com/runtime/webhooks/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dmca-dmca-cases:
    url: "https://mcp.dmca.com/runtime/webhooks/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dmca-dmca-cases": {
      "Transport": "http",
      "Url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dmca-dmca-cases -t streamable-http -u 'https://mcp.dmca.com/runtime/webhooks/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dmca-dmca-cases": {
      "type": "http",
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-04 (score 75, +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.

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

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

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

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

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

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

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

## MCP tools (10)

### `createCase` (~122 tokens)

POST https://api.dmca.com/createCase — create 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.

### `createComplianceCase` (~200 tokens)

POST https://api.dmca.com/createComplianceCase — create 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.

### `createDIYCase` (~157 tokens)

POST https://api.dmca.com/createDIYCase — create 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.

### `getCaseById` (~70 tokens)

GET https://api.dmca.com/getCaseById?id= — fetch one case by id.

Input parameters:

- `id` (string, required): Case ID returned by listCases (or equivalent).
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.

### `getSiteReport` (~90 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 /getSiteReport/{domain}).
- `token` (string): DMCA API token from the login tool; optional if the server/session already has one.

### `listCases` (~69 tokens)

GET https://api.dmca.com/listCases — list managed takedown cases. Optional page.

Input parameters:

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

### `listComplianceCases` (~68 tokens)

GET https://api.dmca.com/listComplianceCases — list compliance cases. Optional page.

Input parameters:

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

### `listDIYCases` (~80 tokens)

GET https://api.dmca.com/listDIYCases — list DIY cases. Optional page. An empty account comes back as an empty list.

Input parameters:

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

### `login` (~80 tokens)

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.

Input parameters:

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

### `updateCase` (~178 tokens)

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.

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dmca-dmca-cases/runtime-webhooks-mcp#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 68
- 2026-10-20: 68
- 2026-10-19: 67
- 2026-10-18: 67
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 65
- 2026-10-13: 65
- 2026-10-12: 64
- 2026-10-10: 63
- 2026-10-07: 62

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

## Links

- Remote endpoint: https://mcp.dmca.com/runtime/webhooks/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/runtime-webhooks-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dmca-dmca-cases/runtime-webhooks-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-dmca-dmca-cases/runtime-webhooks-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-dmca-dmca-cases/runtime-webhooks-mcp