mcp-github-organization-signal-scanner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_github_organization_signalsA | Resolve a company domain to its GitHub organization and return 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. Returns one flat Clay ready row. 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. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.