repocritics-mcp-server
OfficialRelated Servers
Alternatives to repocritics-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceProvides read-only, provenance-first repository navigation for agents and humans, with ranked lexical retrieval, exact query, document handles, symbol context, and change impact analysis.42 npmApache 2.0- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query previously analyzed GitHub repositories for architecture analysis, code review findings, and single-turn code Q&A with verifiable file and line references.MIT
- FlicenseBqualityDmaintenanceEnables analysis and querying of Git repository content (both public and private) through a unified tool that provides repository summaries, file structures, and full content optimized for LLM consumption.1-
- AlicenseBqualityCmaintenanceEnables read-only search over a curated, provenance-preserving corpus of EVM smart-contract security knowledge, providing tools for retrieving audit findings, document context, and source information.5MIT
- AlicenseBqualityBmaintenanceProvides read-only hybrid RAG search and discovery over a local-first AI knowledge corpus, enabling semantic and keyword search, browse, digest, and status tools.4PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.1Apache 2.0
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: search, repo metadata, wiki, reviews, categories, tags, and AI reports. There is no ambiguity between tools; even search_repos and get_repo are clearly differentiated by scope.
All tool names follow a consistent verb_noun pattern using snake_case (search_repos, get_repo, get_wiki, list_reviews, list_categories, list_tags, get_ai_report). The naming style is uniform and predictable.
With 7 tools, the server is well-scoped for a repository information service. Each tool earns its place, covering search, individual fetching, lists, and premium content without redundancy.
The tool set covers the main read-only operations for the RepoCritics corpus: searching repos, fetching metadata, wiki, reviews, categories, tags, and AI reports. Minor gaps exist, such as no way to fetch a single review or filter repos by category directly, but these are not critical for the core workflow.