Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Whitemarmot/copyright01

REMOTE · WWW.COPYRIGHT01.COM · SCANNED SEP 20

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

+2 this week 25 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the io.github.Whitemarmot/copyright01 MCP server?

io.github.Whitemarmot/copyright01 is a hosted endpoint at https://www.copyright01.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.copyright01.com

# add to Claude Code
claude mcp add --transport http whitemarmot-copyright01 'https://www.copyright01.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "whitemarmot-copyright01": {
      "url": "https://www.copyright01.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "whitemarmot-copyright01": {
      "type": "http",
      "url": "https://www.copyright01.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.whitemarmot-copyright01]
url = "https://www.copyright01.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "whitemarmot-copyright01": {
      "type": "remote",
      "url": "https://www.copyright01.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add whitemarmot-copyright01 --url 'https://www.copyright01.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  whitemarmot-copyright01:
    url: "https://www.copyright01.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "whitemarmot-copyright01": {
      "Transport": "http",
      "Url": "https://www.copyright01.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add whitemarmot-copyright01 -t streamable-http -u 'https://www.copyright01.com/mcp'
// mcp.json
{
  "mcpServers": {
    "whitemarmot-copyright01": {
      "type": "http",
      "url": "https://www.copyright01.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Sept 26 +2
    • HSTS header: fail → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.60 → unverified security
    • Authorization: fail → unverified security
    • Transport: pass → fail security
    • HSTS header: pass → fail security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://www.copyright01.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=copyright01.com CN=YE2,O=Let's Encrypt,C=US 14 Aug 2026 12 Nov 2026 ECDSA 256 ECDSA-SHA384 622abe04f930eecc226532de28f06e78f17
SANs: *.copyright01.com, copyright01.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.copyright01.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
copyright01.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 301
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.copyright01.com/mcp Redirected 301 https://copyright01.com/mcp
http (plaintext) http://www.copyright01.com/mcp HTTPS enforced 301 https://www.copyright01.com/mcp
MCP tools · 6 exposed · ~446 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create-deposit-tool ~168

Create a new copyright deposit. Supported types: text, website, youtube, social, github. For text deposits, provide content_text. For other types, provide website_url. Returns the deposit details with certificate verification code.

NameTypeReqDescription
content_textstringText content to protect (required for type=text, min 10 characters)
descriptionstringOptional description (max 2000 characters)
is_publicbooleanWhether the deposit is publicly visible (default: true)
titlestringTitle for the deposit (3-255 characters)
typestringDeposit type: text, website, youtube, social, or github
website_urlstringURL to protect (required for website/youtube/social/github types)

No output schema declared.

No examples provided.

get-deposit-tool ~48

Get details of a specific deposit by its ID. Only returns deposits owned by the authenticated user (IDOR-protected).

NameTypeReqDescription
idintegerThe deposit ID to retrieve

No output schema declared.

No examples provided.

get-profile-tool ~28

Get your profile information including plan, credits remaining, storage usage, and deposit count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list-deposits-tool ~89

List your copyright deposits with optional filtering and pagination. Returns up to 20 deposits per page.

NameTypeReqDescription
pageintegerPage number (default: 1, 20 results per page)
statusstringFilter by status: pending, certified, failed
typestringFilter by deposit type: text, website, youtube, social, github

No output schema declared.

No examples provided.

verify-certificate-tool ~58

Verify a certificate by its verification code. Returns the associated deposit details if found. Works for public deposits and your own private deposits.

NameTypeReqDescription
codestringCertificate verification code (e.g. XXXX-XXXX-XXXX)

No output schema declared.

No examples provided.

verify-hash-tool ~55

Verify a SHA-256 hash against all deposits. Checks your own deposits and public deposits. Returns the matching deposit if found.

NameTypeReqDescription
hashstringSHA-256 hash to verify (64 hex characters)

No output schema declared.

No examples provided.

Common questions

What is the io.github.Whitemarmot/copyright01 MCP server?

io.github.Whitemarmot/copyright01 is an MCP server listed in the public MCP registry as io.github.Whitemarmot/copyright01. Copyright deposit API, protect code, text, and websites with Berne Convention proof. This page covers its hosted endpoint (https://www.copyright01.com/mcp).

Is the io.github.Whitemarmot/copyright01 MCP server safe to use?

io.github.Whitemarmot/copyright01 scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Whitemarmot/copyright01 MCP server expose?

io.github.Whitemarmot/copyright01 exposes 6 tools: create-deposit-tool, list-deposits-tool, get-deposit-tool, verify-hash-tool, verify-certificate-tool, get-profile-tool. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.

Does the io.github.Whitemarmot/copyright01 MCP server require authentication?

No. We connected to io.github.Whitemarmot/copyright01 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Whitemarmot/copyright01 MCP server still maintained?

io.github.Whitemarmot/copyright01 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.