Developer · Remote MCP server

Content Sweep

Prepaid copyright investigation and authorized enforcement, with a free agent sandbox.

Visit Content Sweep's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
ai.contentsweep/agent-access
Version
1.0.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-21
Updated
2026-09-21
Publisher
ai.contentsweep
Namespace
Namespace verified by the MCP Registry via the domain contentsweep.ai · how
Website
contentsweep.ai/developers/agents
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://contentsweep.ai/api/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
Content Sweep 1.0.0 · protocol 2025-06-18
Tools discovered
35 - show namesfind_copies, investigate_url, capture_evidence, prepare_takedown, submit_takedown, check_status, monitor_case, enroll_agent, enroll_live, get_account, get_prices, get_balance, get_usage, create_quote, purchase_credits, set_spending_policy, create_rights_holder, create_work, delegate_authority, revoke_authority, get_operation, get_case, get_evidence, get_packet, get_monitor, pause_monitor, resume_monitor, exchange_token, rotate_credential, revoke_credential, create_webhook, revoke_webhook, get_events, get_webhook_deliveries, replay_event
Checked on
2026-10-05

How the live check works

How to connect Content Sweep

Content Sweep is a remote MCP server: there is nothing to install. Its endpoint is https://contentsweep.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Constraints RegistryPolicy-as-code guardrails for AI coding agents, validated via OPA, Conftest, Checkov & Semgrep.Local · stdioPyPI: constraints-registry
Contabo (VPS) MCP ServerContabo API (v1.0.0) as MCP tools for cloud provisioning, and management. Powered by HAPI MCP server.Remote · HTTPLive check: ✗ no handshakecontabo.run.mcp.com.ai
Container Host AIopsGoverned Docker + Portainer container-host ops: reads, RCA analyses, guarded writes. 38 tools.Local · stdioPyPI: container-host-aiops
Containerization AssistTypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support.Local · stdionpm: containerization-assist-mcp
ContentrainGit-native content governance for AI agents - 27 deterministic MCP tools over stdio and HTTP.Remote & Local · HTTP, stdiostudio.contentrain.io
Contest MCPLog amateur-radio QSOs to N3FJP logging software over its TCP API.Local · stdioPyPI: contest-mcp
Context - ctxt.ioShare text, markdown, code, or HTML as auto-expiring links.Remote · HTTPLive check: ✓ handshakectxt.io
Context AutopilotMines your Claude Code and Cursor sessions into evidence-based CLAUDE.md / AGENTS.md rules.Local · stdionpm: context-autopilot