# gitmanual (remote · gitmanual.com)

Setup manuals for any GitHub repo: will it run on macOS, Windows or Linux, and the exact steps.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gitmanual.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual.md), [page](https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual)

## Channel facts

- Endpoint: `https://gitmanual.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 566 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the gitmanual MCP server?

gitmanual is a hosted endpoint at https://gitmanual.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http zainudinnoori-gitmanual 'https://gitmanual.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "zainudinnoori-gitmanual": {
      "url": "https://gitmanual.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zainudinnoori-gitmanual": {
      "type": "http",
      "url": "https://gitmanual.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.zainudinnoori-gitmanual]
url = "https://gitmanual.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zainudinnoori-gitmanual": {
      "type": "remote",
      "url": "https://gitmanual.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zainudinnoori-gitmanual --url 'https://gitmanual.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  zainudinnoori-gitmanual:
    url: "https://gitmanual.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "zainudinnoori-gitmanual": {
      "Transport": "http",
      "Url": "https://gitmanual.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add zainudinnoori-gitmanual -t streamable-http -u 'https://gitmanual.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "zainudinnoori-gitmanual": {
      "type": "http",
      "url": "https://gitmanual.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-11-21 (score 80, +1)

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

### 2026-11-19 (score 79, +1)

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

### 2026-11-17 (score 78, +1)

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

### 2026-11-14 (score 77, +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-11-12 (score 76, +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-11-10 (score 75, +1)

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

### 2026-11-08 (score 74, 0)

- [functional regression] Tool coverage: 80% → 73%
- [functional regression] Schema quality: 241 → 566
- [functional] Schema quality: excellent → good
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “find_alternatives”
- [functional] New tool “get_list”
- [functional] New tool “search_repos”

### 2026-11-07 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `get_setup_manual` (~142 tokens)

Get a repo's setup manual

How to install or run a GitHub repository: whether it works on macOS, Windows or Linux (with reasons), ready-made downloads, install commands from the README, the parts it needs, and step-by-step commands to set it up from source. Facts come from the repo's own files, not guesses.

Input parameters:

- `arch` (string): The user's CPU, for picking the right download (Apple Silicon is arm64).
- `os` (string): Only this system. Leave out for all three.
- `repo` (string, required): The GitHub repo: "owner/repo" or a github.com link, e.g. "ollama/ollama".

### `get_setup_script` (~99 tokens)

Get a repo's setup script

One script that sets the repo up on the given system: bash for macOS and Linux, PowerShell for Windows. It stops at the first error, skips what's already installed and never starts servers. Show it to the user to read before running it.

Input parameters:

- `os` (string, required)
- `repo` (string, required): The GitHub repo: "owner/repo" or a github.com link, e.g. "ollama/ollama".

### `search_repos` (~163 tokens)

Search repos with setup manuals

Find open-source GitHub repos on gitmanual's shelf: by words in the name or description, by the system they run on, language or difficulty, or only those rising on GitHub this week. Each result links to its setup manual.

Input parameters:

- `difficulty` (string)
- `language` (string): Main language, as GitHub names it, e.g. "Python".
- `os` (string): Only repos that run on this system.
- `page` (integer)
- `query` (string): Words to look for in the repo's name or description.
- `rising` (boolean): Only repos rising on GitHub this week.
- `sort` (string): stars (default), recent, popular, or worked (most people got it running).

### `get_list` (~77 tokens)

Get a curated list of repos

gitmanual's lists group repos by what they do and where they run, e.g. self-hosted apps for Linux, AI tools for Windows, MCP servers for macOS. Leave out slug to see every list.

Input parameters:

- `slug` (string): The list, e.g. "ai-tools-windows". Leave out to get all lists.

### `find_alternatives` (~85 tokens)

Find alternatives that run on a system

When a repo doesn't run (or only partly runs) on the user's system: whether it does, and up to five similar repos that do, judged by shared GitHub topics.

Input parameters:

- `os` (string, required)
- `repo` (string, required): The GitHub repo: "owner/repo" or a github.com link, e.g. "ollama/ollama".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 74
- 2026-11-08: 74
- 2026-11-07: 74
- 2026-11-06: 74

## Common questions

### What is the gitmanual MCP server?

gitmanual is an MCP server listed in the public MCP registry as io.github.zainudinnoori/gitmanual. Setup manuals for any GitHub repo: will it run on macOS, Windows or Linux, and the exact steps. This page covers its hosted endpoint (https://gitmanual.com/mcp).

### Is the gitmanual MCP server safe to use?

gitmanual scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the gitmanual MCP server expose?

gitmanual exposes 5 tools: get_setup_manual, get_setup_script, search_repos, get_list, find_alternatives. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.

### Does the gitmanual MCP server require authentication?

No. We connected to gitmanual without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the gitmanual MCP server still maintained?

gitmanual is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the gitmanual MCP server?

VerifyMCP ran 13 checks on gitmanual, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://gitmanual.com/mcp
- Repository: https://github.com/zainudinnoori/gitmanual
- Website: https://gitmanual.com/
- Changelog RSS feed: https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual.xml
- Changelog JSON feed: https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual.json
- HTML version of this page: https://verifymcp.io/servers/zainudinnoori-gitmanual/gitmanual
