GitLumen MCP
Server Details
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Glama couldn't complete the latest health check. 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
- 58.9% over 54 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- gitlumen-team/gitlumen-mcp
- GitHub Stars
- 0
- Server Listing
- gitlumen-mcp
TDQS
Scored across 5 tools
Each tool serves a clearly distinct purpose: explaining the workflow, fetching repository structure, generating a report, and retrieving/listings existing reports. The overlap between fetching structure and screening is explicitly disambiguated by the 'without generating a full risk report' phrasing.
All tool names follow a consistent snake_case verb_noun pattern: explain_, get_, get_, list_, screen_. The verbs clearly map to their actions, and the objects are specific and readable.
Five tools is well-scoped for this server's purpose: generate, retrieve, list, inspect, and explain. Each tool earns its place without redundancy or bloat.
The core workflow of generating and retrieving risk reports is fully covered, with repository structure inspection as a useful supporting action. A delete/remove operation for locally stored reports is a minor missing feature but not a critical gap in the primary workflow.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
5 tool updates
- First observed
explain_gitlumen_mcp_flow - First observed
get_repository_structure - First observed
get_review_report - First observed
list_review_reports - First observed
screen_repository
Related MCP Connectors
Audit GitHub repos for malicious and supply-chain code before you depend on them.
Free deterministic security scan of public git repos: OSV.dev vulnerable deps, secrets, config lint.
Deep security scans of repos you own from your editor: dependency CVEs, SAST, git-history secrets.
Monitor third-party API changes in GitHub repos, map breaks to files, open reviewable auto-fix PRs.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceScans GitHub repositories for security vulnerabilities by cloning, performing static analysis, secret detection, build verification, and AI-powered OWASP-aligned code review, producing a scored SECURITY.md report.-
- AlicenseNot gradedqualityAmaintenanceDetect live website vulnerabilities and security flaws in GitHub repositories using automated DAST and SAST scanning. Safeguard applications by identifying exposed secrets, insecure dependencies, and common code patterns prone to exploitation. Receive structured fix plans with precise code remediation steps to resolve identified risks and improve security posture.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables maintainers to prioritize maintenance across GitHub repositories by converting repository, branch, CI, security, and release signals into deterministic, evidence-backed scores and ranked actions.MIT
- AlicenseNot gradedqualityAmaintenanceAn evidence-first integration decision service that assesses GitHub repositories and returns transparent scores, adoption recommendations, and verification gates.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.