meok-ai-psych-vuln-audit-mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.2Updated Oct 27, 2026

EU AI Act Article 5(1)(f) gambling-vertical compliance audit MCP. Detects AI systems that exploit ps

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Local MCP server that audits AI systems in the gambling sector against EU AI Act Article 5(1)(f) compliance.

What you can do
  • Runs an EU AI Act Article 5(1)(f) compliance audit aimed at the gambling vertical.
  • Detects AI systems that exploit psychological vulnerabilities, per the registry description.
  • No tool list, README or server instructions are published, so the exact operations and outputs are not documented.
When to use it
Worth considering when you need to check whether an AI system used in gambling or betting contexts falls under the EU AI Act's prohibition on exploiting vulnerabilities, and want that check available to an assistant.
Requirements
Runs as a local process on the user's machine via uvx from the PyPI package meok-ai-psych-vuln-audit-mcp; a Python/uv environment is needed. Desktop only, no web execution. No authentication, environment variables or headers are declared.
Before you install
The description is truncated and no tools, README or instructions are provided, so scope and behavior cannot be verified before installing. Treat any audit output as advisory rather than legal advice.

Installation

In SourceWeft

  1. Open meok-ai-psych-vuln-audit-mcp 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.2LatestSep 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.

Other Audit integrations