Ybe Check

io.github.AddyCuberPublished by GitHub account AddyCuberv0.1.1Updated Oct 27, 2026

Ybe Check – security and compliance orchestrator for AI-generated repositories.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Ybe Check is a local MCP server described as a security and compliance orchestrator for AI-generated repositories.

What you can do
  • The registry entry only calls it a security and compliance orchestrator for AI-generated repositories.
  • No tools, instructions or README are published, so the specific checks it can run and the results it returns are not documented here.
  • It runs as a local process over stdio, so any capability it offers would be exposed to the assistant as tools at connect time.
When to use it
Consider it if you generate code with AI and want an assistant-side check of that repository for security and compliance concerns. Because no tool list or documentation is available, confirm what it actually does before relying on it.
Requirements
A local Python runtime able to install the ybe-check package from PyPI; it runs as a stdio process on the user's machine. No authentication, environment variables or headers are declared. Desktop-only; not available as a web executable.
Before you install
The server is undocumented: no tool list, instructions or README, so what it reads, sends or changes cannot be verified from this entry. It is intended to inspect repositories, so review its code and network behavior before pointing it at private source code.

Installation

In SourceWeft

  1. Open Ybe Check 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.1LatestSep 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 Check integrations