Developer · Remote MCP server
GitLumen MCP
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.gitlumen-team/gitlumen-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-07
- Updated
- 2026-06-07
- Publisher
- gitlumen-team (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/gitlumen-team) · how
- Listed under
- GitHub MCP servers, Maps MCP servers
- Repository
- github.com/gitlumen-team/gitlumen-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp-github-screen.gitlumen.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 502)
- Handshake
- HTTP 502
- Checked on
- 2026-10-05
How to connect GitLumen MCP
GitLumen MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp-github-screen.gitlumen.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Gitlab MCPPublic GitLab projects and users. No key required. | Local · stdio |
| Gitlab MCPGitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more. | Local · stdio |
| GitLab MCP ServerGo MCP server for GitLab: 2 dynamic tools reach 1000+ REST/GraphQL actions. Free/CE, no paid tier. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Gitlab PublicGitLab Public MCP - wraps the GitLab REST API v4 (public endpoints, no auth) | Remote · HTTPLive check: ✓ handshake |
| GitmemPersistent institutional memory for AI coding agents. Memory that compounds. | Local · stdio |
| GitPinProve and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. | Local · stdio |
| GitResumeValidate, build, and publish the resume you keep as YAML in your own GitHub repository. | Remote · HTTPLive check: sign-in required |
| GitstandupGenerate daily standup notes from git commits across multiple repositories with AI summaries. | Local · stdio |