mcpbeat

GitLumen MCP Server

io.github.gitlumen-team/gitlumen-mcp
answering

GitLumen MCP is answering right now. Last checked 13 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 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
1445 ms
Response time
average over 24h
0
Stars
last commit 7 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 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 1147 ms 13 min ago

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 1445 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 1445 ms on average, which is faster than 2% 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?
Yes — written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.