dmca-cases
MCP server by DMCA Protection & Takedown Services · mcp
DMCA.com cases MCP. Tools: login, listCases, listDIYCases, listComplianceCases, getCaseById, createCase, updateCase, createDIYCase, createComplianceCase, getSiteReport. Callers can send their own DMCA.com API token on the MCP request as an Authorization: Bearer, X-DMCA-Token or Token header; otherwise call login with the user's DMCA.com email/password first: it returns a DMCA API token that is reused automatically for the rest of this MCP session, so cases are created under that user's account. Every other tool also takes an optional token argument (the token from login), which always takes priority; pass it explicitly if a call returns HTTP 401. There is no shared server token: without login or token, case tools fail with 'Not logged in'. updateCase keeps status and priority unchanged unless you pass them. getSiteReport uses upstream path /getSiteReport/{domain}.
Endpoint: https://mcp.dmca.com/runtime/webhooks/mcp
Verification: observed. Source: crawl.
Capabilities (10)
- createCase
- createComplianceCase
- createDIYCase
- getCaseById
- getSiteReport
- listCases
- listComplianceCases
- listDIYCases
- login
- updateCase