MCP Github Organization Signal Scanner

What mcp-github-organization-signal-scanner does

mcp-github-organization-signal-scanner connects an MCP client to an Apify actor that identifies a company’s GitHub organization and summarizes its public activity. The main tool, scan_github_organization_signals, returns one flat JSON row with 32 snake_case fields.

Results can include the organization login and URL, account type, repository count, followers, creation date, location, top languages, total stars, most-starred repository, latest push time, and the number of repositories active within a selected time window. The row also reports whether a public SDK was detected. Discovery details, rejected identity candidates, repository sampling, completeness, excluded repositories, rate-limit state, coverage, fetch status, and run date are included as operational fields.

How it works

The package is a thin client: scanning runs on Apify, and the actor reads organization and repository metadata from GitHub’s documented REST API. It does not clone repositories, inspect source code, scan for secrets, or evaluate code quality.

Provide company_domain to start discovery. company_name can help the identity check reject an incorrect organization match. If the GitHub login is already known, github_org bypasses discovery and proceeds directly to GitHub.

Repository-derived signals are optional. With includeRepoDetail enabled, the actor calculates languages, stars, activity, and SDK status from repositories. Forks and archived repositories are left out of those calculations, and the excluded count is recorded in the result. The default activity window is 90 days, with supported alternatives of 30, 180, or 365 days.

Setup and configuration

The documented setup requires Node.js 18 or newer, an Apify account, and an Apify API token. Install and run the package through npx in an MCP client configuration. A Claude Desktop entry uses the package command npx -y @mambalabsdev/mcp-github-organization-signal-scanner and passes APIFY_TOKEN through the environment. After adding the entry, restart Claude Desktop so the scan tool becomes available.

An optional GitHub personal access token can raise the GitHub limit from 60 requests per hour for unauthenticated access to 5,000 requests per hour. The token can be created without scopes for public data.

Tools and capabilities

• Resolve a company domain to a GitHub organization.
• Scan a known GitHub organization without discovery.
• Return repository, follower, star, language, creation-date, and push-activity signals.
• Detect whether the organization appears to ship a public SDK.
• Set the active-repository window and repository page budget.
• Request contributor counts for the most-starred repository.
• Reuse successful results from a seven-day cache or force a fresh fetch.
• Set an Apify run cost cap with max_charge_usd.

Limitations and notes

repoPageBudget controls how many pages of up to 100 repositories are read. The output identifies how many repositories were sampled and whether the sample is complete, so large organizations may have partial coverage.

includeContributorEstimate adds a request for the contributor count of the most-starred repository and is disabled by default. includeRepoDetail: false returns the organization record only and uses one request instead of the repository-derived scan.

Rate-limited requests are reported as not_extractable, rather than being represented as zero values. If discovery resolves to a personal GitHub account instead of an organization, the result reports identity_mismatch. Unauthenticated GitHub access is intended for only a handful of companies; larger lists benefit from a personal access token.