# GitLumen MCP (remote · mcp-github-screen.gitlumen.com)

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

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp-github-screen.gitlumen.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/gitlumen-team-gitlumen-mcp/mcp-github-screen.md), [page](https://verifymcp.io/servers/gitlumen-team-gitlumen-mcp/mcp-github-screen)

## Channel facts

- Endpoint: `https://mcp-github-screen.gitlumen.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 328 tokens (~65/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http gitlumen-team-gitlumen-mcp https://mcp-github-screen.gitlumen.com/mcp
```

### Codex

```toml
[mcp_servers.gitlumen-team-gitlumen-mcp]
url = "https://mcp-github-screen.gitlumen.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gitlumen-team-gitlumen-mcp": {
      "type": "remote",
      "url": "https://mcp-github-screen.gitlumen.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gitlumen-team-gitlumen-mcp --url https://mcp-github-screen.gitlumen.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gitlumen-team-gitlumen-mcp:
    url: "https://mcp-github-screen.gitlumen.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "gitlumen-team-gitlumen-mcp": {
      "type": "http",
      "url": "https://mcp-github-screen.gitlumen.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (5)

### `screen_repository` (~147 tokens)

Screen a public GitHub repository or GitHub pull request URL and generate a GitLumen-style risk report. Supports repo URLs and /pull/<number> URLs.

Input parameters:

- `branch` (string): Optional branch/ref. Ignored for PR URLs unless GitHub needs fallback.
- `maxFiles` (integer): Optional hard cap for files downloaded and scanned.
- `output` (string): Response format returned to the MCP client.
- `repoUrl` (string, required): GitHub repository URL, for example https://github.com/owner/repo or https://github.com/owner/repo/pull/123
- `scope` (string): Screening depth. quick downloads fewer files; standard downloads more files.

### `get_review_report` (~55 tokens)

Get a previously generated GitLumen MCP report by reportId.

Input parameters:

- `output` (string)
- `reportId` (string, required): Report id returned by screen_repository, for example glr_abcd1234abcd1234

### `list_review_reports` (~27 tokens)

List previously generated GitLumen MCP reports stored locally.

Input parameters:

- `limit` (integer)

### `get_repository_structure` (~61 tokens)

Fetch public GitHub repository or PR structure without generating a full risk report.

Input parameters:

- `branch` (string): Optional branch/ref.
- `limit` (integer): Maximum tree entries to return.
- `repoUrl` (string, required): GitHub repository or pull request URL.

### `explain_gitlumen_mcp_flow` (~38 tokens)

Explain how this Path 1 MCP server fits into GitLumen and how it later connects to Base MCP Path 2.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gitlumen-team-gitlumen-mcp/mcp-github-screen#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 60
- 2026-07-29: 60
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 58

## Links

- Remote endpoint: https://mcp-github-screen.gitlumen.com/mcp
- Authorisation metadata: https://mcp-github-screen.gitlumen.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/gitlumen-team/gitlumen-mcp
- Changelog RSS feed: https://verifymcp.io/servers/gitlumen-team-gitlumen-mcp/mcp-github-screen/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/gitlumen-team-gitlumen-mcp/mcp-github-screen/changelog.json
- HTML version of this page: https://verifymcp.io/servers/gitlumen-team-gitlumen-mcp/mcp-github-screen