com.mambabuilt/mcp-github-organization-signal-scanner
NPM · @MAMBALABSDEV/MCP-GITHUB-ORGANIZATION-SIGNAL-SCANNER · SCANNED SEP 20
Resolve a company domain to its GitHub organization with repo, language and activity signals.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 685 tokens (~685/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.mambabuilt/mcp-github-organization-signal-scanner server?
com.mambabuilt/mcp-github-organization-signal-scanner runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-github-organization-signal-scanner. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-github-organization-signal-scanner
claude mcp add com-mambabuilt-mcp-github-organization-signal-sc -- npx -y @mambalabsdev/mcp-github-organization-signal-scanner
{
"mcpServers": {
"com-mambabuilt-mcp-github-organization-signal-sc": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-github-organization-signal-scanner"
]
}
}
} {
"servers": {
"com-mambabuilt-mcp-github-organization-signal-sc": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-github-organization-signal-scanner"
]
}
}
} codex mcp add com-mambabuilt-mcp-github-organization-signal-sc -- npx -y @mambalabsdev/mcp-github-organization-signal-scanner
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-github-organization-signal-sc": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-github-organization-signal-scanner"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-github-organization-signal-sc --command npx --arg -y --arg @mambalabsdev/mcp-github-organization-signal-scanner
mcp_servers:
com-mambabuilt-mcp-github-organization-signal-sc:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-github-organization-signal-scanner"] {
"McpServers": {
"com-mambabuilt-mcp-github-organization-signal-sc": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mambalabsdev/mcp-github-organization-signal-scanner"
]
}
}
} assistant mcp add com-mambabuilt-mcp-github-organization-signal-sc -t stdio -c npx -a -y @mambalabsdev/mcp-github-organization-signal-scanner
{
"mcpServers": {
"com-mambabuilt-mcp-github-organization-signal-sc": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-github-organization-signal-scanner"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@mambalabsdev/mcp-github-organization-signal-scanner@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
scan_github_organization_signals Scan GitHub Organization Signals ~685
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activeWindowDays | string | – | How recently a repository must have been pushed to count as active. 90 days by default. This changes what "active" means on the row, so pick the window your own definition of an engaged engineering t… |
| company_domain | string | – | Bare company domain, for example stripe.com. This is the only required input and it is the join key for every other actor in the fleet. |
| company_name | string | – | Optional but strongly recommended. It is what the identity gate checks a discovered record against, so supplying it is the single cheapest way to reduce wrong matches. |
| githubToken | string | – | YOUR OWN GitHub personal access token, free to create at github.com/settings/tokens with no scopes at all for public data. OPTIONAL: without it the actor runs at GitHub 60 requests per hour, which is… |
| github_org | string | – | Optional. If you already know the organization login, for example "stripe", put it here and the actor skips discovery entirely and goes straight to the API, which is faster and spends fewer of your r… |
| includeContributorEstimate | boolean | – | When "true" the actor spends one extra request to read the contributor count of the organization most starred repository, as a floor on the size of its public engineering surface. Default "false", be… |
| includeRepoDetail | boolean | – | When "true" (default) the organization repositories are read and the language, star, activity and SDK signals are derived from them. Set "false" to return the organization record only, which is one r… |
| repoPageBudget | string | – | How many pages of 100 repositories to read for a large organization. This is a cost and completeness dial, not a change of answer: the row always reports how many repositories were actually sampled a… |
| skipCache | boolean | – | When "false" (default) a successful lookup is cached for seven days and reused, which costs you nothing on a repeated run. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility. |
No output schema declared.
No examples provided.
What is the com.mambabuilt/mcp-github-organization-signal-scanner server?
com.mambabuilt/mcp-github-organization-signal-scanner is listed in the public MCP registry as com.mambabuilt/mcp-github-organization-signal-scanner. Resolve a company domain to its GitHub organization with repo, language and activity signals. This page covers its npm package (@mambalabsdev/mcp-github-organization-signal-scanner).
Is the com.mambabuilt/mcp-github-organization-signal-scanner server safe to use?
com.mambabuilt/mcp-github-organization-signal-scanner scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-github-organization-signal-scanner server expose?
com.mambabuilt/mcp-github-organization-signal-scanner exposes 1 tool: scan_github_organization_signals. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-github-organization-signal-scanner server still maintained?
com.mambabuilt/mcp-github-organization-signal-scanner is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-github-organization-signal-scanner server under?
com.mambabuilt/mcp-github-organization-signal-scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.