Developer · Remote MCP server
Copyright01
Copyright deposit API - protect code, text, and websites with Berne Convention proof.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Whitemarmot/copyright01- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-03-03
- Updated
- 2026-03-03
- Publisher
- Whitemarmot (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Whitemarmot) · how
- Repository
- github.com/Whitemarmot/copyright01-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.copyright01.com/mcp | Authorization |
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 301)
- Handshake
- HTTP 301
- Checked on
- 2026-10-05
How to connect Copyright01
Copyright01 is a remote MCP server: there is nothing to install. Its endpoint is https://www.copyright01.com/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 URL contains placeholders to fill in before connecting: {api_key}.
The registry entry declares an HTTP header for the connection: Authorization. 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 from Whitemarmot (GitHub)
More developer servers
| Server | Runs |
|---|---|
| Copilot DatagatePolicy-driven, read-only MCP server for safe database access from AI tools. | Local · stdio |
| Copilot Memory MCPPersistent semantic memory for AI agents using local ChromaDB vector search. No cloud required. | Local · SSE |
| Copilot Studio MCPBuild, test, ship and maintain Microsoft Copilot Studio agents from the editor. | Local · stdio |
| Copilotcliswitchgate MCPRemote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid. | Remote · HTTPLive check: ✗ no handshake |
| Coralquery MCPA paid remote MCP for AI SDK data query MCP, built to return verdicts, receipts, usage logs, and aud. | Remote · HTTPLive check: ✗ no handshake |
| Cordon for MCPCordon for MCP. Security gateway with policy enforcement, audit log, and HITL approvals. | Local · stdio |
| CoReason Ecosystem - Federated MCP GatewayCoReason Tripartite Architecture Governance Plane. Stateless zero-trust federated MCP gateway. | Local · stdio |
| CoredashReal User Monitoring for Core Web Vitals. Query LCP, INP, CLS field data from real visitors. | Remote · HTTPLive check: ✓ handshake |