# DMCA.com Cases [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/NetroDev/dmca-cases-public-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dmca-com-cases

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

## Tools
Capabilities this server exposes over MCP:

- **login** — POST https://api.dmca.com/login
- **listCases** — GET https://api.dmca.com/listCases
- **listDIYCases** — GET https://api.dmca.com/listDIYCases
- **listComplianceCases** — GET https://api.dmca.com/listComplianceCases
- **getCaseById** — GET https://api.dmca.com/getCaseById?id=
- **createCase** — POST https://api.dmca.com/createCase
- **createDIYCase** — POST https://api.dmca.com/createDIYCase
- **createComplianceCase** — POST https://api.dmca.com/createComplianceCase
- **updateCase** — POST https://api.dmca.com/updateCase
- **getSiteReport** — GET https://api.dmca.com/getSiteReport/{domain}

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `DMCA_API_TOKEN`, `DMCA_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the DMCA.com Cases MCP server does

The DMCA.com Cases MCP server exposes selected DMCA.com API operations as MCP tools. It can authenticate with the upstream service, retrieve case collections, fetch an individual case, submit several case types, modify an existing case, and request a report for a domain.

The available case categories include general cases, DIY cases, and compliance cases. The server returns response bodies from DMCA.com as upstream JSON rather than imposing its own response schema or status enumeration. This makes it suitable for clients that can interpret the API responses directly.

## How it works

For local use, the project runs as a Node-based stdio MCP process. MCP clients start the process and communicate with it over standard input and output. The server then forwards supported operations to the DMCA.com API at `https://api.dmca.com`.

A hosted option is also provided through Azure Functions. Its public host is `https://mcp.dmca.com`, and the MCP protocol is available through the Microsoft MCP extension endpoint at `/runtime/webhooks/mcp`; an SSE sibling is also available. The root URL is a cover page, not the MCP protocol endpoint. Hosted requests require the `x-functions-key` associated with the MCP extension.

## Setup and configuration

The npm package is named `dmca-cases-mcp`. A local build can be installed from `packages/mcp-stdio` with `npm install`, built with `npm run build`, and started with `DMCA_API_TOKEN=your_token node dist/index.js`. Client configuration can instead invoke `npx -y dmca-cases-mcp` and pass the token in the client environment.

The server accepts `DMCA_API_TOKEN`; the README also documents `DMCA_TOKEN` as an alternative. The token is sent to the upstream API in the `Token` header and is not logged. The `login` tool can obtain a token, while case creation and updates require a valid token. Azure deployments use `DMCA_API_TOKEN` as an application setting.

## Tools and capabilities

The DMCA.com Cases MCP server provides these operations:

- `login` sends credentials to the DMCA.com login endpoint.
- `listCases`, `listDIYCases`, and `listComplianceCases` retrieve case lists.
- `getCaseById` retrieves a case using its ID.
- `createCase`, `createDIYCase`, and `createComplianceCase` submit new cases.
- `updateCase` sends changes for an existing case.
- `getSiteReport` retrieves a report for a supplied domain.

The repository also defines HTTP mirror routes under `/api` for the hosted Azure deployment.

## Limitations and notes

The exposed surface does not include registration, badge or protected-item APIs, or XARF operations. The upstream API remains the source of response structure and behavior. Hosted deployment additionally depends on the Azure Functions MCP extension key, while local clients need a valid API token for authenticated operations.

_Full upstream README: https://allmcps.com/mcp/dmca-com-cases/readme_