Open Source Intelligence MCP
Server Details
GitHub project health, package dependency risk, trending repos, license & package comparison.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 67 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Server Listing
- oss-intel-mcp
TDQS
Scored across 8 tools
Each tool serves a distinct function: briefs, package comparison, dependency risk, license checks, project health, trending repos, and network info. Overlap is minimal, and where overlap exists (brief_summary vs daily_brief), descriptions explicitly differentiate them.
All names use lowercase snake_case with two-word compounds, creating a uniform style. However, the pattern isn't strictly verb_noun (e.g., dependency_risk, project_health are noun_noun), so there are minor deviations from an ideal consistent convention.
The 8-tool set is well-scoped, covering high-level briefs, granular package/repo analysis, and network info without unnecessary redundancy or overwhelming the user.
The tools cover discovery (trending_repos, daily_brief), evaluation (project_health, dependency_risk, license_check, compare_packages), and action support (brief_summary, mint_info). The surface is comprehensive for open-source intelligence, with no obvious dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
6 tool updates
- Changed
brief_summary1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
compare_packages1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
daily_brief1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402 (x402 rail)."New value: +"payment transaction signature, when re-calling after a 402 (pay-per-query rail)."
- Changed
dependency_risk1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
project_health1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
trending_repos1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
1 tool update
- Added
brief_summary
1 tool update
- Changed
daily_brief2 fields changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"Solana tx signature, when re-calling after a 402 (x402 rail)." - added
Input schema / properties / stripe_tokenAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header." +}
7 tool updates
- First observed
compare_packages - First observed
daily_brief - First observed
dependency_risk - First observed
license_check - First observed
mint_info - First observed
project_health - First observed
trending_repos
Related MCP Connectors
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and security.
GitHub repo analytics: stars, trending, code search, contributor maps for project research.
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and supply-c.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI agents and developers to score npm packages, PyPI packages, and GitHub repositories for maintenance health, producing A–F grades, per-signal details, and plain-language risk lists before adoption. It supports checking individual packages, scanning manifests or lock files for transitive dependencies, and comparing alternatives.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides GitHub open-source intelligence via MCP tools for discovering trends, evaluating repository health, comparing projects, and analyzing users, issues, and releases. It includes a CLI and can be used with AI assistants like Claude or Cursor.MIT
- AlicenseNot gradedqualityBmaintenanceEnables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.1,348 npmMIT
- AlicenseBqualityDmaintenanceAnalyze GitHub repositories with health scores, issue triage, and action items through MCP tools.4MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.