What it does
The Easy2257 MCP connector gives AI assistants read-only access to the 18 U.S.C. 2257 compliance records that Easy2257 keeps for adult content producers. It reports productions, scenes, per-participant verification and paperwork status, expiring documents, certificates, archive hashes, account plan details and a summary of removal requests. It cannot create, change, sign or attest to records, and it cannot trigger payments. Names, dates of birth, ID numbers, images, addresses and document contents are not returned.
It suits questions such as which scenes still need compliance work, which documents expire within a chosen window, or whether a certificate is current, superseded or revoked. The server is hosted by Easy2257 and reached over Streamable HTTP, so there is no server code to run locally. Clients that can only start a local command over stdio can use a Docker Hub image that bridges to the hosted server.
To connect, add a custom connector and sign in with OAuth, which grants the read-only mcp:read scope. Clients that accept a connection header can instead use an MCP key created under Account, then MCP Keys. Keys begin with ez_mcp_, are shown once and are stored as a hash, and up to ten can be held at a time. Every connected assistant appears on the settings screen, where access can be revoked immediately.
Limitations and requirements
Requires an Easy2257 account. Header-based clients and the Docker bridge need an MCP key, shown only once, with a limit of ten keys per account. The Docker container exits without a key. The two content log tools are available only on the solo creator plan and refuse on other plans. The connector grants read-only access and cannot create, change, sign or pay for anything.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Easy2257
Read your 18 U.S.C. 2257 compliance records: what is outstanding, expiring, or certified.
v1.0.0As shown on registry.modelcontextprotocol.io when we last read it