DMCA.com Cases

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.