Hosted MCP server/Other

DMCA Cases MCP server

Hosted at mcp.dmca.com·Streamable HTTP

DMCA Cases exposes DMCA.com case operations over MCP. Read-only tools are login, listCases, listDIYCases, listComplianceCases, getCaseById, and getSiteReport. Write tools are createCase, createDIYCase, createComplianceCase, and updateCase. Two credentials are involved: the gateway requires an x-functions-key using the mcp_extension system key issued by DMCA.com on request, and write calls also require a DMCA_API_TOKEN sent in the Token header.

mcp.dmca.com Streamable HTTP Gateway x-functions-key (mcp_extension, request from DMCA.com) plus DMCA_API_TOKEN in a Token header for writes Server not checked yet Reviewed 2026-11-16
About

Where it fits

Brand-protection and legal operations teams that manage DMCA.com cases and want read or write access with explicit credentials.

  • List DIY or compliance cases read-only.
  • Read one case or a site report by ID.
  • Create or update a case with a DMCA API token.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds DMCA Cases as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http dmca-cases https://mcp.dmca.com/runtime/webhooks/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://mcp.dmca.com/runtime/webhooks/mcp
Host
mcp.dmca.com · /runtime/webhooks/mcp
Transport
Streamable HTTP
Authentication
Gateway x-functions-key (mcp_extension, request from DMCA.com) plus DMCA_API_TOKEN in a Token header for writes
Server name
dmca-cases
Listing type
Community or directory listing

The installer uses the server name dmca-cases. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that dmca-cases appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List DIY or compliance cases read-only. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

DMCA Cases repositoryhttps://github.com/NetroDev/dmca-cases-public-mcp