Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

gitmanual

REMOTE · GITMANUAL.COM

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

Available components

+3 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 566 tokens (~113/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 0
    • Tool coverage: 80% → 73% ▼ functional
    • 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” functional
  • 7 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://gitmanual.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gitmanual.com CN=YR2,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 RSA 2048 SHA256-RSA 608be033f17102391cfe6366492a3841740
SANs: gitmanual.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gitmanual.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
gitmanual.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy frame-ancestors 'self'; base-uri 'self'; object-src 'none'; form-action 'self' https://checkout.stripe.com https://github.com; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gitmanual.com/mcp Verified 200
http (plaintext) http://gitmanual.com/mcp HTTPS enforced 308 https://gitmanual.com/mcp
MCP tools · 5 exposed · ~566 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_alternatives ~85

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.

NameTypeReqDescription
osstringyes–
repostringyesThe GitHub repo: "owner/repo" or a github.com link, e.g. "ollama/ollama".

No output schema declared.

No examples provided.

get_list ~77

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.

NameTypeReqDescription
slugstring–The list, e.g. "ai-tools-windows". Leave out to get all lists.

No output schema declared.

No examples provided.

get_setup_manual ~142

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.

NameTypeReqDescription
archstring–The user's CPU, for picking the right download (Apple Silicon is arm64).
osstring–Only this system. Leave out for all three.
repostringyesThe GitHub repo: "owner/repo" or a github.com link, e.g. "ollama/ollama".

No output schema declared.

No examples provided.

get_setup_script ~99

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.

NameTypeReqDescription
osstringyes–
repostringyesThe GitHub repo: "owner/repo" or a github.com link, e.g. "ollama/ollama".

No output schema declared.

No examples provided.

search_repos ~163

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.

NameTypeReqDescription
difficultystring––
languagestring–Main language, as GitHub names it, e.g. "Python".
osstring–Only repos that run on this system.
pageinteger––
querystring–Words to look for in the repo's name or description.
risingboolean–Only repos rising on GitHub this week.
sortstring–stars (default), recent, popular, or worked (most people got it running).

No output schema declared.

No examples provided.

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.

remote · gitmanual.com

# add to Claude Code
claude mcp add --transport http zainudinnoori-gitmanual 'https://gitmanual.com/mcp'
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.