API Tools

dmca.com

An MCP server that exposes createCase and getCaseById tools for creating and retrieving cases through API endpoints.

1 endpoint10 known toolsFirst detected October 7, 2026Last detected October 7, 2026

ENDPOINT 1

https://mcp.dmca.com/runtime/webhooks/mcp

No auth detected

MCP server metadata

Name: dmca-cases
Version: 1.2.1

Capabilities

loggingtools

Server instructions

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}.

Known tools 10

createCase

POST https://api.

Potential side effects

createComplianceCase

POST https://api.

Potential side effects

createDIYCase

POST https://api.

Potential side effects

getCaseById

GET https://api.

Inferred read-only

getSiteReport

GET https://api.

Inferred read-only

listCases

GET https://api.

Inferred read-only

listComplianceCases

GET https://api.

Inferred read-only

listDIYCases

GET https://api.

Inferred read-only

login

POST https://api.

Potential side effects

updateCase

POST https://api.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dmca-cases]
url = "https://mcp.dmca.com/runtime/webhooks/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dmca-cases": {
      "type": "http",
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dmca-cases
Remote MCP URL: https://mcp.dmca.com/runtime/webhooks/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dmca-cases": {
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dmca-cases": {
      "type": "http",
      "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dmca-cases",
  "transport": "streamable-http",
  "url": "https://mcp.dmca.com/runtime/webhooks/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for dmca.com was fetched 2026-10-12T20:53:31.792Z.

Trust status Trusted

dmca.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.