DMCA.com Cases

com.dmcav1.2.1更新于 Oct 7, 2026

DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token.

已验证Streamable HTTP可网页运行Business & CommerceSecurity & Monitoring

概览

AI 生成的概览

让助手使用你自己的 DMCA.com API 令牌，列出、读取、创建和更新 DMCA.com 投诉与合规案件，并获取站点报告。

功能
将 DMCA.com 案件 API 封装为 MCP 工具：login、listCases、listDIYCases、listComplianceCases、getCaseById、createCase、createDIYCase、createComplianceCase、updateCase 和 getSiteReport。响应按上游 JSON 原样返回，不虚构数据结构。注册、徽章/受保护项目 API 以及 XARF 未开放。
适用场景
适合需要管理 DMCA.com 投诉、DIY 或合规案件，并希望助手在对话中查询、汇总或起草并提交新案件的人。若只需要一般版权信息，则无需安装。
运行要求
需要 DMCA.com 账号和 API 令牌：本地 npm 包 dmca-cases-mcp 通过环境变量 DMCA_API_TOKEN（或 DMCA_TOKEN）提供，远程端点通过 Authorization bearer 请求头提供。login 工具可生成令牌。需要访问 api.dmca.com 的网络连接。
安装前请注意
令牌属于凭据，请妥善保管 DMCA_API_TOKEN 和 Authorization 请求头的值。createCase、createDIYCase、createComplianceCase 和 updateCase 会写入你的 DMCA.com 账号，可能触发真实的删除或合规操作，并可能产生费用或法律后果。案件数据会发送至 DMCA.com 的 API。

安装

在 SourceWeft 中

  1. 打开 控制台中的 DMCA.com Cases，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

dmca-cases-public-mcp

Public MCP for DMCA.com cases (company of record: DMCA.com).

Maintained as DMCA MCP Cases.

Tools

ToolUpstream
loginPOST https://api.dmca.com/login
listCasesGET https://api.dmca.com/listCases
listDIYCasesGET https://api.dmca.com/listDIYCases
listComplianceCasesGET https://api.dmca.com/listComplianceCases
getCaseByIdGET https://api.dmca.com/getCaseById?id=
createCasePOST https://api.dmca.com/createCase
createDIYCasePOST https://api.dmca.com/createDIYCase
createComplianceCasePOST https://api.dmca.com/createComplianceCase
updateCasePOST https://api.dmca.com/updateCase
getSiteReportGET https://api.dmca.com/getSiteReport/{domain}

Not exposed: register, badge/protected-item APIs, XARF.

Auth: env DMCA_API_TOKEN (or DMCA_TOKEN) sent as HTTP header Token. login can mint a token. Never logged. Response bodies are returned as upstream JSON — no invented schemas or status enums.

createCase, createDIYCase, createComplianceCase, and updateCase require a valid Token (DMCA_API_TOKEN). getSiteReport also sends Token.

Canonical docs: www.dmca.com/api · OpenAPI 2.1.2 · host https://api.dmca.com.

A) npm / stdio (local clients)

bash
cd packages/mcp-stdionpm installnpm run buildDMCA_API_TOKEN=your_token node dist/index.js

Cursor / Claude Desktop:

json
{  "mcpServers": {    "dmca-cases": {      "command": "npx",      "args": ["-y", "dmca-cases-mcp"],      "env": { "DMCA_API_TOKEN": "YOUR_TOKEN" }    }  }}

Package name: dmca-cases-mcp · registry mcpName: com.dmca/dmca-cases.

B) Azure Functions (.NET Isolated)

Canonical public host:

https://mcp.dmca.com

Default Azure hostname (fallback, serves the same app):

https://dmca-cases-public-mcp-afdcard8bbdtd4e3.westus3-01.azurewebsites.net

Cover: / (root) and /cover (alias) · Project: azure/DmcaCasesMcp.Functions (.NET 8 Isolated, code deploy — not container).

  • MCP (Functions MCP extension): /runtime/webhooks/mcp (and SSE sibling /runtime/webhooks/mcp/sse). The protocol endpoint is fixed by the Microsoft MCP extension; / is the HTML cover, not the MCP endpoint. Requests need an x-functions-key header (the mcp_extension system key, issued by DMCA.com on request).
  • Info pointer: GET /api/mcp
  • HTTP mirrors: /api/listCases, /api/listDIYCases, /api/listComplianceCases, /api/getCaseById, /api/login, /api/createCase, /api/updateCase, /api/createDIYCase, /api/createComplianceCase, /api/getSiteReport?domain= (upstream path /getSiteReport/{domain})

App setting: DMCA_API_TOKEN.

Deploy (after dotnet + Azure Functions Core Tools are available):

bash
cd azure/DmcaCasesMcp.Functionsfunc azure functionapp publish dmca-cases-public-mcp --dotnet-isolated

(Use the exact Function App resource name in your subscription if it differs.)

Prefer Flex Consumption.

Registry metadata

See server.json for official MCP Registry (packages + Azure remotes).

Cursor plugin scaffolding

See mcp.json and .cursor-plugin/plugin.json for a future Marketplace submit.

Auto-deploy (GitHub Actions → Azure)

Workflow: .github/workflows/azure-functions-deploy.yml

On push to main (paths under azure/DmcaCasesMcp.Functions/**), GitHub Actions builds the .NET 8 Isolated project and deploys to Function App dmca-cases-public-mcp.

Required repo secret:

  1. Azure Portal → Function App dmca-cases-public-mcp → Get publish profile
  2. GitHub → Settings → Secrets and variables → Actions → AZURE_FUNCTIONAPP_PUBLISH_PROFILE

Also set Function App setting DMCA_API_TOKEN in Azure (not in GitHub) for live API calls.

来源：README.md，提交 9f0b786

工具

0
工具元数据尚未被收录。

版本历史

1
  1. v1.2.1最新Oct 7, 2026