Regulatory Signals

io.github.rikocr8orh8Published by GitHub account rikocr8orh8v0.1.2Updated Oct 24, 2026

Audit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Audits GitHub repositories for security, compliance and EU AI Act exposure from an AI assistant such as Claude or Cursor.

What you can do
  • Audit GitHub repositories for security, compliance and EU AI Act exposure.
  • No tool list is published, so the exact operations are not documented; the server is described only as a repository audit service for assistants.
When to use it
Useful when you want an assistant to check a GitHub repository for security, compliance or EU AI Act concerns without leaving the chat client.
Requirements
Runs as a local stdio process installed from the npm package @regulatorysignals/mcp, so Node.js is needed. Requires a Regulatory Signals API key supplied through the REGULATORY_SIGNALS_API_KEY environment variable, obtained from the provider's dashboard. Desktop client only.
Before you install
The server needs an API key (REGULATORY_SIGNALS_API_KEY); keep it out of shared configs. It reads GitHub repositories and sends their contents to the provider's service for analysis, so consider whether that code may leave your machine. No tool list is published, so what it can change or write is unclear.

Installation

In SourceWeft

  1. Open Regulatory Signals 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 Signals integrations