takedown
Server Details
DMCA takedown & host reveal for AI agents: who hosts an infringing URL, even behind Cloudflare.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
3 toolsassess_takedownAssess a takedownRead-onlyInspect
Assess how a takedown for this URL would proceed: where the notice goes (host, platform, or a hidden host that must be revealed first), what documents and attestation the content owner must supply, the step-by-step process, and the legal caveats (§512(f), scope limits). Read-only; does not judge the merits of the claim and files nothing. Use resolve_host first if you only need the hosting answer.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The infringing URL or bare domain | |
| what | No | One line on what was copied (e.g. "my photo set", "my course videos") — echoed into the plan, not judged |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| route | Yes | |
| domain | Yes | |
| target | Yes | |
| process | Yes | |
| fileable | Yes | |
| nextStep | Yes | |
| legalNotes | Yes | |
| requiredFromYou | Yes |
resolve_hostResolve host & abuse contactRead-onlyInspect
Look up who hosts a URL and where an abuse/takedown notice would go. Identifies the CDN/proxy in front (e.g. Cloudflare), the platform, or the direct host and its abuse contact. For direct hosts and previously-revealed domains it returns the real host immediately; for a domain hidden behind a proxy it explains that revealing the true host requires initiating an abuse report. Read-only; files nothing. A lookup, not legal advice; it does not guarantee removal.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The infringing URL or bare domain |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| host | Yes | |
| proxy | Yes | |
| domain | Yes | |
| nextStep | Yes | |
| platform | Yes | |
| frontedBy | Yes | |
| revealSource | Yes | |
| takedownRoute | Yes | |
| realHostHidden | Yes |
start_takedownStart a takedown (onboarding link)Read-onlyInspect
Get the secure onboarding link to actually start a takedown. The content owner opens it once in a browser to identify themselves, sign the standing authorization (the one step that legally requires a human), and provide proof of ownership. Returns the link plus what to prepare and what happens next. Creates nothing by itself; filings targeting lawful criticism, reviews or journalism are declined at intake.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The infringing URL or bare domain |
Output Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | |
| nextStep | Yes | |
| humanNote | Yes | |
| onboardingUrl | Yes | |
| whatToPrepare | Yes | |
| whatHappensNext | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!