mcpbeat Sign in

GitLumen MCP Server

by gitlumen-team Your server? Claim it
answering

GitLumen MCP is answering right now. Last checked 8 min ago. It exposes 5 tools. Last commit 7 Jun 2026.

Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.

Uptime history 47 days of history · worst day 0%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
1508 ms
Response time
average over 24h
0
Stars
last commit 7 Jun 2026

GitLumen MCP missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add gitlumen-mcp --transport http https://mcp-github-screen.gitlumen.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gitlumen-mcp": {
      "url": "https://mcp-github-screen.gitlumen.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gitlumen-mcp]
url = "https://mcp-github-screen.gitlumen.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "gitlumen-mcp": {
      "url": "https://mcp-github-screen.gitlumen.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "gitlumen-mcp": {
      "url": "https://mcp-github-screen.gitlumen.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

review
get_review_report
Get a previously generated GitLumen MCP report by reportId.
list_review_reports
List previously generated GitLumen MCP reports stored locally.
explain
explain_gitlumen_mcp_flow
Explain how this Path 1 MCP server fits into GitLumen and how it later connects to Base MCP Path 2.
repository
get_repository_structure
Fetch public GitHub repository or PR structure without generating a full risk report.
screen
screen_repository
Screen a public GitHub repository or GitHub pull request URL and generate a GitLumen-style risk report. Supports repo URLs and /pull/<number> URLs.

Endpoints

URLTransportStateLatencyChecked
https://mcp-github-screen.gitlumen.com/mcp streamable-http answering 1225 ms 8 min ago

Alternatives to GitLumen MCP

same job, measured the same way
SlopScore
by slopscore

Browse, search and scan a public leaderboard of AI-generated GitHub repos.

10 tools answering
Gread
by nitrorcr

An MCP server that gives your AI access to the source code and docs of all public github repos

5 tools answering
Gk CLI
by gitkraken

The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.

12 113 installs/wk local only
Moxie Docs
by jackalope-dev

Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.

12 tools answering
AgencyAI Commerce MCP
by barnaby-coder

AgencyAI's public MCP for service discovery and AI-readiness assessment.

3 tools answering
Sphior Code MCP
by toraastrta

Deterministic SAST/SCA findings + fix guidance for your GitHub repos, handed to your AI agent.

28 installs/wk local only
GitHub to MCP Converter
by nirholas

Convert any GitHub repo to MCP server - automatic tool generation API wrap

local only
GitHub
by aifity

Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.

local only

GitLumen MCP — questions

Answers built from our own checks of this server.

What can GitLumen MCP do?
It exposes 5 tools, read directly from the server on our last check. Among them: explain_gitlumen_mcp_flow, get_repository_structure, get_review_report, list_review_reports, screen_repository. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is GitLumen MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1508 ms. The bar chart above shows every period we have measured.
How do I connect GitLumen MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does GitLumen MCP need an API key?
No. GitLumen MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is GitLumen MCP?
It answers our handshake in 1508 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is GitLumen MCP open source?
We cannot say either way: written in JavaScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.