Public Domain Check
REMOTE · PUBLIC-DOMAIN-CHECK-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Is a book, film or song public domain in the US, UK, EU, Canada or Japan? Pay per call via x402.
Last scanned (14 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 787 tokens (~157/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 68
First indexed and scored.
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 21 Nov 2026 · Probed https://public-domain-check-production.up.railway.app/copyright/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| 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 public-domain-check-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://public-domain-check-production.up.railway.app/copyright/mcp | Verified | 200 | |
| http (plaintext) | http://public-domain-check-production.up.railway.app/copyright/mcp | HTTPS enforced | 301 | https://public-domain-check-production.up.railway.app/copyright/mcp |
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 →
check_public_domain Check US public-domain status ~357
Check whether a specific book, film, song, recording or artwork is in the US public domain, and the date it enters it. Use this instead of answering from memory when the work was published 1929–1963 (its status depends on a copyright renewal that models usually don't know), when the work is obscure, or when you need a citable answer before quoting, reprinting, adapting, selling or training on it. Looks up 2.38M US Copyright Office registrations and 434k renewals; a title is usually enough for 1923–1977 books. Returns status, date, confidence, a one-line reason and record IDs, plus a second opinion from HathiTrust's human copyright reviewers and a free-copy link when there is one. Add countries=uk,eu,canada,australia,japan,china,india (or all) to get the answer for those countries in the same call. Not charged if it can't answer. Costs $0.01 (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Author, composer or creator (improves matching) |
| author_death_year | integer | – | For works published 1978 or later |
| countries | string | – | Also answer for other countries: comma-separated uk, eu, canada, australia, japan, china, india, or all. Same price. |
| origin | string | – | Country of first publication |
| title | string | yes | Title of the work |
| type | string | – | Kind of work (default book) |
| work_for_hire | boolean | – | – |
| year | integer | – | Year of first publication; inferred for 1923–1977 books when omitted |
No output schema declared.
No examples provided.
check_public_domain_full Check US public-domain status (full detail) ~204
Same check as check_public_domain, but with the complete reasoning, every matching registration and renewal record, and all caveats. Use when you must show your work, cite sources in detail, or audit the decision. Costs $0.02 (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Author, composer or creator (improves matching) |
| author_death_year | integer | – | For works published 1978 or later |
| countries | string | – | Also answer for other countries: comma-separated uk, eu, canada, australia, japan, china, india, or all. Same price. |
| origin | string | – | Country of first publication |
| title | string | yes | Title of the work |
| type | string | – | Kind of work (default book) |
| work_for_hire | boolean | – | – |
| year | integer | – | Year of first publication; inferred for 1923–1977 books when omitted |
No output schema declared.
No examples provided.
copyright_rules_for_year US copyright rule for a publication year (free) ~93
Free. Given a publication year (and type of work), say which US copyright rule applies and whether a records lookup is needed. Call this first when you only know the year: many years are settled by the rules alone.
| Name | Type | Req | Description |
|---|---|---|---|
| author_death_year | integer | – | – |
| type | string | – | – |
| work_for_hire | boolean | – | – |
| year | integer | yes | Year of first publication |
No output schema declared.
No examples provided.
public_domain_day Public Domain Day (free) ~37
Free. What enters the US public domain on January 1 of a given year.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Defaults to next January |
No output schema declared.
No examples provided.
search_copyright_renewals Search US copyright renewal records ~96
Find who renewed a 1929–1963 work's US copyright and when: usually the current rightsholder or their estate. Use when you need to know whom to ask for permission or a license. Costs $0.01 (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | – |
| limit | integer | – | – |
| title | string | – | – |
| year | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Public Domain Check MCP server?
Public Domain Check is a hosted endpoint at https://public-domain-check-production.up.railway.app/copyright/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 · public-domain-check-production.up.railway.app
claude mcp add --transport http chomkaevan-public-domain-check 'https://public-domain-check-production.up.railway.app/copyright/mcp'
What is the Public Domain Check MCP server?
Public Domain Check is an MCP server listed in the public MCP registry as io.github.chomkaevan/public-domain-check. Is a book, film or song public domain in the US, UK, EU, Canada or Japan? Pay per call via x402. This page covers its hosted endpoint (https://public-domain-check-production.up.railway.app/copyright/mcp).
Is the Public Domain Check MCP server safe to use?
Public Domain Check scores 71 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 Public Domain Check MCP server expose?
Public Domain Check exposes 5 tools: check_public_domain, check_public_domain_full, search_copyright_renewals, copyright_rules_for_year, public_domain_day. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.
Does the Public Domain Check MCP server require authentication?
No. We connected to Public Domain Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Public Domain Check MCP server still maintained?
Public Domain Check is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Public Domain Check MCP server?
VerifyMCP ran 13 checks on Public Domain Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.