Meok Enterprise Compliance Suite

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.0.6Updated Oct 24, 2026

MEOK Enterprise Compliance Suite — End-to-end EU AI Act, GDPR, NIS2, DORA, ISO, SOC2, HIPAA, PCI

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server advertised as an end-to-end compliance suite covering EU AI Act, GDPR, NIS2, DORA, ISO, SOC2, HIPAA and PCI.

What you can do
The registry description presents this server as an end-to-end compliance suite spanning EU AI Act, GDPR, NIS2, DORA, ISO, SOC2, HIPAA and PCI. No tools are listed in the manifest and no README is available, so the concrete capabilities cannot be confirmed from the supplied material. It runs locally over stdio rather than as a remote endpoint.
When to use it
Consider it only if you want an assistant to help with regulatory compliance work across the frameworks named in the description, such as EU AI Act, GDPR, NIS2, DORA, ISO, SOC2, HIPAA or PCI. Because no tools or documentation are provided, verify what it actually exposes before relying on it for any real compliance task. It is not suitable for browser or remote use, since it is desktop-only and stdio-based.
Requirements
Runs as a local process over stdio, installed from PyPI as meok-enterprise-compliance-suite and started with python. Desktop only; no web executable. No authentication, environment variables or headers are declared.
Before you install
The registry description names several regulatory frameworks but gives no detail on what the server does with data, whether it writes or changes anything, or whether it contacts third parties. No credentials are declared, but the manifest lists no tools, so the actual behavior cannot be verified before installation. Treat the compliance coverage claims as unverified marketing until you inspect the package yourself.

Installation

In SourceWeft

  1. Open Meok Enterprise Compliance Suite in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.6LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.