DMCA.com MCP server
10 tools · Last check that passed 27 Oct 2026, 01:50 UTC
DMCA.com's own remote MCP server, in beta, gives an agent the copyright takedown cases of the DMCA.com account it signs in to, with tools to file and update cases and to fetch a site report for a domain. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 10 tools
| Tool | Counted as |
|---|---|
createCase | Changes things |
createComplianceCase | Changes things |
createDIYCase | Changes things |
login | Changes things |
updateCase | Changes things |
getCaseById | Said to only read |
getSiteReport | Said to only read |
listCases | Said to only read |
listComplianceCases | Said to only read |
listDIYCases | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
11 of the last 11 checks passed
A check passes when the server lists its tools. Checked at https://mcp.dmca.com/runtime/webhooks/mcp.
Recent changes
No change seen across the last 11 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when DMCA.com's tools change.
One email when DMCA.com's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- With a DMCA.com sign-in, its tools file new cases of several kinds, including managed and DIY takedowns, and update the status and details of a case. DMCA.com's MCP server page
- Its login tool signs in to the user's own DMCA.com account, and the token it returns is reused for the rest of the session, so later calls act as that account. DMCA.com's MCP server page
- DMCA.com lists DIY takedowns at $10 a month and managed takedowns from $199, and says managed cases are processed by its own case team. DMCA.com's MCP server page
- Case descriptions, infringing addresses and site reports come back to the agent as text, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With DMCA.com's own settings, as its documentation describes them. Stackduke has not tested them.
- DMCA.com says the token can come from its login method or from the API section of the DMCA.com website, so we recommend giving the agent a token rather than the account's password. DMCA.com's API documentation
- Keep a person approving each new case and each update, as OWASP advises for high-risk actions. OWASP, prompt injection
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.