meok-watermark-attest-mcp@1.3.13
VERIFIED· not startedPublisher claims: "EU AI Act Article 50 watermarking + transparency compliance MCP. Built for the 2 August 2026 cliff. Article 50 transparency obligations apply from 2 Aug 2026; pre-existing systems have until 2 Dec 2026. Classify Art 50 obligations (chatbot disclosure, GPAI synthetic-content marking per C2PA-2.0, deepfake disclosure, emotion/biometric transparency), generate compliant disclosure text, audit content pipelines, emit HMAC-signed attestations. By MEOK AI Labs." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MEOK_API_KEYConfiguration, not credentials: MEOK_ATTEST_KEY, MEOK_ATTESTATION_API, MEOK_PAYG_KEY, MEOK_VERIFY_TIMEOUT, MEOK_VERIFY_URL- Where it talks to
- no vendor host named in the codeAlso stripe.com, proofof.ai, meok.ai, csoai.org, c2pa.org, iptc.org — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names stripe.com, proofof.ai, meok.ai, csoai.org, c2pa.org, iptc.org as well as its own vendor. The guard injects MEOK_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 95/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 2,027 lines in 25 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for meok-watermark-attest-mcp@1.3.13 as of 3d ago. This is the package itself, not its dependencies.