mcp-github-organization-signal-scanner
com.mambabuilt · Updated
Resolve a company domain to its GitHub organization with repo, language and activity signals.
At a glance
mcp-github-organization-signal-scanner is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y @mambalabsdev/mcp-github-organization-signal-scanner`, and needs APIFY_TOKEN. It scores B (79/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install mcp-github-organization-signal-scanner in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install mcp-github-organization-signal-scanner in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add mcp-github-organization-signal-scanner -e 'APIFY_TOKEN=<APIFY_TOKEN>' -- npx -y @mambalabsdev/mcp-github-organization-signal-scannerFill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
Verify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install mcp-github-organization-signal-scanner in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "mcp-github-organization-signal-scanner": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-github-organization-signal-scanner" ], "env": { "APIFY_TOKEN": "<APIFY_TOKEN>" } } } }Fill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install mcp-github-organization-signal-scanner in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "mcp-github-organization-signal-scanner": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-github-organization-signal-scanner" ], "env": { "APIFY_TOKEN": "<APIFY_TOKEN>" } } } }Fill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install mcp-github-organization-signal-scanner in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.mcp-github-organization-signal-scanner] command = "npx" args = ["-y", "@mambalabsdev/mcp-github-organization-signal-scanner"] env = { APIFY_TOKEN = "<APIFY_TOKEN>" }Fill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install mcp-github-organization-signal-scanner in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "mcp-github-organization-signal-scanner": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-github-organization-signal-scanner" ], "env": { "APIFY_TOKEN": "<APIFY_TOKEN>" } } } }Fill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install mcp-github-organization-signal-scanner in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "mcp-github-organization-signal-scanner": { "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-github-organization-signal-scanner" ], "env": { "APIFY_TOKEN": "<APIFY_TOKEN>" } } } }Fill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
How to install mcp-github-organization-signal-scanner in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "mcp-github-organization-signal-scanner": { "type": "stdio", "command": "npx", "args": [ "-y", "@mambalabsdev/mcp-github-organization-signal-scanner" ], "env": { "APIFY_TOKEN": "<APIFY_TOKEN>" } } } }Fill in your credentials
Replace <APIFY_TOKEN> with your real value. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What does mcp-github-organization-signal-scanner need from you?
API key — Apify API token from https://console.apify.com/account/integrations
APIFY_TOKENrequiredsecretEnvironment variableApify API token from https://console.apify.com/account/integrations
Pass secrets through your shell environment rather than committing them into a config file.
What tools does mcp-github-organization-signal-scanner expose?
This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.
What the code can do
Read from the published package source — never executed. Parsed 1 of 1 source file.
This server can read and write files, make network requests and read your environment variables.
How it was published
- No provenance attestation — there is nothing linking this published artifact to a specific source commit.
- 1 npm maintainer — a single point of compromise · last published by mambalabsdev.
Maintainer of this package and think something here is wrong? Tell us and we'll correct it.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
- Downloads at launch — The package is fetched from its registry each run unless you pin a version.
- Last commit 2 days ago — Actively maintained.
- Repository created 2 months ago — Very new project with little track record yet.
- 0 GitHub stars — Very little community usage so far.
- 60 weekly downloads — Very few installs — you would be an early user.
Client compatibility
Health score
B · 79Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%100%
Last commit 2 days ago.
- Adoption20%21%
0 stars, 60 weekly downloads.
- Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
- Provenance15%100%
Package and registry entry point at the same repository.
- Packaging15%100%
Publishes a pinned version (1.2.0).
Documentation
Full READMEGitHub Organization Signal Scanner MCP Server
An MCP server that resolves a company domain to its GitHub organization with repo, language and activity signals. It wraps the Mamba Labs GitHub Organization Signal Scanner actor on Apify and returns a Clay-ready flat JSON row to any MCP client.
What's Inside
- What it does
- Quick start
- Prerequisites
- Example prompts
- Inputs
- Output
- Example output
- Features
- Full actor documentation
- Mamba Labs GTM Suite
- License
What it does
Give it a company domain and it finds that company's GitHub organization and returns repository count, followers, creation date, top languages, total stars, the most recent push, how many repositories are actively worked on, and whether the company ships a public SDK. One flat row per company, read through GitHub's own documented REST API.
Forks and archived repositories are excluded from the language and star derivations, and the exclusion is counted on the row. A rate limited request reports not_extractable and never a zero, because a zero is a number a buyer would filter on. A login that resolves to a personal user account rather than an organization is reported as identity_mismatch. It reads organization and repository metadata only: it does not clone repositories, read source, scan for secrets or assess code quality.
All of the scanning runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.
Quick start
You need Node.js 18 or newer and an Apify account with an API token.
Add this to your Claude Desktop config:
{
"mcpServers": {
"mamba-github-organization-signal-scanner": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-github-organization-signal-scanner"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The scan_github_organization_signals tool will be available.
Prerequisites
Excerpt — the full document is on GitHub.
Alternatives to mcp-github-organization-signal-scanner
- Gitleaks Cloud - GitHub API Key Hunter & Secret ScannerB · 74Gitleaks Cloud - GitHub API Key Hunter & Secret Scanner
- Betterleaks Cloud - GitHub, Git, S3, Dir Secret ScannerB · 71Betterleaks Cloud - GitHub, Git, S3, Dir Secret Scanner
- pare-githubA · 88Pare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.
- githubA · 88MCP server for GitHub operations (PRs, issues, actions) with structured, token-efficient output
Maintain mcp-github-organization-signal-scanner? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/com-mambabuilt-mcp-github-organization-signal-scanner)Catalog data refreshed . Something wrong? Report it.