mcp-github-organization-signal-scanner
Related Servers
Alternatives to mcp-github-organization-signal-scanner
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Bluesky Brand Presence Mapper actor on Apify. Resolve a company domain to its Bluesky account with exact follower, following and post counts.1108 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs X Twitter Brand Presence Mapper actor on Apify. Resolve a company domain to its X handle, profile URL and follower metrics.1106 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Trustpilot Reputation Enricher actor on Apify. Resolve a company domain to its Trustpilot rating, review count and claimed status.199 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs People Finder & Email Verifier actor on Apify. Give it a company domain, name or LinkedIn URL and it returns the people at that company who match your role, seniority and department filters, each as a structured contact record with an optional verified business email.1220 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Company Contact Details Extractor actor on Apify. Find a company contact page and extract role emails, a phone number and a postal address.1103 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Ecommerce Platform Profiler actor on Apify. Detect the ecommerce platform, payment providers and catalogue size behind a storefront.195 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purposes. An agent will always pick the correct (and only) tool for this server's scope.
The single name, scan_github_organization_signals, follows a clear verb_noun snake_case convention that is self-consistent. There is no mixed style or ambiguity in the naming.
The server is intentionally a single-purpose scanner returning one flat row, so one tool is defensible and nothing is redundant. However, one tool is thin: there is no batch or multi-domain entry point, so scope flexibility is limited.
For a read-only signal scanner, the surface is quite complete: it aggregates org resolution, repo counts, languages, stars, activity, SDK presence, exclusion counts, and error states into one row. Minor gaps exist (no bulk/batch scanning of multiple domains and no follow-up detail drill-down), but core use cases are covered.