Audit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor.
Connect Runs on your machine
claude mcp add regulatory-signals -e REGULATORY_SIGNALS_API_KEY=<REGULATORY_SIGNALS_API_KEY> -- npx -y @regulatorysignals/[email protected]{
"mcpServers": {
"regulatory-signals": {
"command": "npx",
"args": [
"-y",
"@regulatorysignals/[email protected]"
],
"env": {
"REGULATORY_SIGNALS_API_KEY": "<REGULATORY_SIGNALS_API_KEY>"
}
}
}
}{
"mcpServers": {
"regulatory-signals": {
"command": "npx",
"args": [
"-y",
"@regulatorysignals/[email protected]"
],
"env": {
"REGULATORY_SIGNALS_API_KEY": "<REGULATORY_SIGNALS_API_KEY>"
}
}
}
}{
"servers": {
"regulatory-signals": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@regulatorysignals/[email protected]"
],
"env": {
"REGULATORY_SIGNALS_API_KEY": "<REGULATORY_SIGNALS_API_KEY>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
REGULATORY_SIGNALS_API_KEYOptional, secret | Your Regulatory Signals API key — get one at regulatorysignals.com/dashboard |
Details
| Package | @regulatorysignals/[email protected] (NPM, stdio) |
| First published | 10 Jun 2026 |
| Last updated | 10 Jun 2026 |
| Registry name | io.github.rikocr8orh8/regulatory-signals |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.