nis2-compliance-mcp@1.3.11
VERIFIED· not startedPublisher claims: "NIS2 Directive (EU 2022/2555) compliance for AI agents. 10 Article 21 risk-management measures audit, Article 23 incident classification, Article 20 management-body accountability. For the 18 essential/important entity sectors. 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_VERIFY_TIMEOUT, MEOK_VERIFY_URL, X402_ASSET, X402_ENABLED, X402_FACILITATOR_URL, X402_NETWORK, X402_PAY_TO, X402_PRICE, X402_TIMEOUT- Where it talks to
- no vendor host named in the codeAlso stripe.com, meok.ai, proofof.ai, smithery.ai, x402.org, europa.eu — 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, meok.ai, proofof.ai, smithery.ai, x402.org, europa.eu 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-13 and scored it 90/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
"npm_setup": "npx meok-setup --pack governance"Fix: Pin versions and sources; vendor anything fetched at install time.mcp_server.run(transport="streamable-http")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.run: npm install -g @smithery/cli@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.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 nis2-compliance-mcp@1.3.11 as of 32 h ago. This is the package itself, not its dependencies.