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