OSSInsight MCP Server
Related Servers
Alternatives to OSSInsight MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides access to the OSS Insight Public API for GitHub repository analytics. It enables querying trending repositories, contributor statistics, and collection rankings through various tools.1810 npm3MIT
- FlicenseNot gradedqualityCmaintenanceA powerful, hosted Model Context Protocol (MCP) server that gives LLMs the ability to understand, navigate, and query any public GitHub repository.1-
- AlicenseBqualityDmaintenanceMCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.155 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to access tools through GitHub authentication and provides comprehensive analytics tracking of tool usage, performance, and user behavior.3-
- AlicenseDqualityDmaintenanceA lightweight MCP server for bringing GitHub repositories into context for large language models, enabling repository analysis, file access, and search without local cloning.46 npm6Apache 2.0
- AlicenseAqualityDmaintenanceAn enterprise-grade Model Context Protocol server that provides comprehensive GitHub repository analysis and AI-powered development assistance through 11 streamlined tools.112MIT
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of GitHub insights: collections listing, repo comparison, ranking within collections, repo metadata, trending repos, and search. There is no significant overlap in their primary functions, making them easy to distinguish.
All tools share the consistent 'ossinsight_' prefix, but the suffixes mix nouns (collections, ranking, repo, trending) with verbs (compare, search), creating an inconsistent pattern. A uniform verb_noun structure would improve predictability.
With six tools, the server is well-scoped for its purpose of providing GitHub repository insights. Each tool fills a necessary role without unnecessary bloat, falling comfortably within the ideal range.
The tool set covers core workflows: discovery (search/trending), metadata retrieval (repo), comparison (compare), and curated collections (collections/ranking). Minor gaps exist, such as a dedicated tool to view collection details directly, but these are workable through existing tools.