_ registry / mcp streamable-http · checked 2h ago

Copyright01

https://www.copyright01.com

Registry code: 4ef2a83c3fbe1998

api record

Copyright01 is a SaaS for online copyright deposit with timestamped proof of authorship,

valid in 181 countries under the Berne Convention.

endpoint
https://copyright01.com/mcp
door code
3373b1a9c281bfaa
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Copyright01 live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is Copyright01 free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Copyright01 have?
6 tools: get-deposit-tool, create-deposit-tool, verify-certificate-tool, verify-hash-tool, list-deposits-tool, get-profile-tool.
Is Copyright01 safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99%· all time 98.4%

latency
167ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 863 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
government & legal legal
used for
  • register a copyright deposit with timestamp
  • verify a copyright certificate
  • verify a hash against deposits
  • list copyright deposits
takes → gives
text, web pages → data, documents
tools
5 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 auth-required 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get-profile-tool reads auth-required 10h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get-deposit-tool reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "description": "The deposit ID to retrieve"
    }
  }
}
    arguments 9 lines
  • create-deposit-tool changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "description": "Deposit type: text, website, youtube, social, or github"
    },
    "title": {
      "type": "string",
      "description": "Title for the deposit (3-255 characters)"
    },
    "is_public": {
      "type": "boolean",
      "description": "Whether the deposit is publicly visible (default: true)"
    },
    "description": {
      "type": "string",
      "description": "Optional description (max 2000 characters)"
    },
    "website_url": {
      "type": "string",
      "description": "URL to protect (required for website/youtube/social/github types)"
    },
    "content_text": {
      "type": "string",
      "description": "Text content to protect (required for type=text, min 10 characters)"
    }
  }
}
    arguments 29 lines
  • verify-certificate-tool reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "description": "Certificate verification code (e.g. XXXX-XXXX-XXXX)"
    }
  }
}
    arguments 9 lines
  • verify-hash-tool reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "hash": {
      "type": "string",
      "description": "SHA-256 hash to verify (64 hex characters)"
    }
  }
}
    arguments 9 lines
  • list-deposits-tool reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "description": "Page number (default: 1, 20 results per page)"
    },
    "type": {
      "type": "string",
      "description": "Filter by deposit type: text, website, youtube, social, github"
    },
    "status": {
      "type": "string",
      "description": "Filter by status: pending, certified, failed"
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4ef2a83c3fbe1998.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4ef2a83c3fbe1998/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4ef2a83c3fbe1998/badge.svg)](https://brick.blue/agent/4ef2a83c3fbe1998?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.