Copyright01 MCP Server

Copyright deposit API — protect code, text, and websites with Berne Convention proof

Local serverstdio

What is the Copyright01 MCP server?

Copyright deposit API — protect code, text, and websites with Berne Convention proof. That is what the copyright01 mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Copyright01.com creates legally binding, timestamped proof of authorship under the Berne Convention (recognized in 181 countries). Use this MCP server to protect original code, text, websites, social media content, and GitHub repositories directly from any AI agent.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 6 tools. What each one is for:

  • create_deposit — Create a timestamped copyright deposit with legal proof of authorship
  • list_deposits — List all deposits with optional filters by type and status
  • get_deposit — Get deposit details including certificate and verification URL
  • verify_hash — Verify a SHA-256 hash against registered deposits
  • verify_certificate — Verify a certificate by its code (public, no auth required)
  • get_profile — Check plan, credits remaining, and storage usage

What it needs from you

Configuration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Copyright01's toolset — create_deposit, list_deposits, get_deposit and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Whitemarmot; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
create_depositCreate a timestamped copyright deposit with legal proof of authorship
list_depositsList all deposits with optional filters by type and status
get_depositGet deposit details including certificate and verification URL
verify_hashVerify a SHA-256 hash against registered deposits
verify_certificateVerify a certificate by its code (public, no auth required)
get_profileCheck plan, credits remaining, and storage usage

How to install the Copyright01 MCP server

{
  "mcpServers": {
    "copyright01": {
      "url": "https://www.copyright01.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Copyright01 to create deposit.
  • Use Copyright01 to list deposits.
  • Use Copyright01 to get deposit.

Frequently asked questions

It connects Copyright01 to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (create_deposit, list_deposits, get_deposit, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Copyright01 directly.