DMCA Protection & Takedown Services MCP server

• Registry namecom.dmca/dmca-casesverified in the MCP registry

The registry name sits under dmca.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-15
• Tools10
• Server calls itselfdmca-cases
• Server version1.2.1
• Protocol version2025-06-18

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 148 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score65 of 100answers 89 · definitions 83 · context 100 · use 21 · connects 100 · lowered by the warning signs below
• Use10 npm downloads a week
• Answered100% of days9 of 9 daily checks
• Median first answer2121 ms
• Space in an agent's context≈ 1,621 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 10 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• createCase

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

• createComplianceCase

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

• createDIYCase

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

• getCaseById

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

• getSiteReport

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

• listCases

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

• listComplianceCases

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

• listDIYCases

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

• login

  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.

• updateCase

  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.