GitMCP (official, remote)
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance5/25
- Docs15/15
- License10/10
Tested GitMCP's generic endpoint https://gitmcp.io/docs (server GitMCP 1.1.0; source idosal/git-mcp, Apache-2.0, 8,513 GitHub stars when checked; last push 2026-05-08). Initialize and tools/list worked with no account (5 tools). Of 3 real calls only match_common_libs_owner_repo_mapping passed (zod -> colinhacks/zod). fetch_generic_documentation for colinhacks/zod returned just a file path (22 chars), and search_generic_documentation answered that no documentation was found yet (being indexed); an earlier try on modelcontextprotocol/typescript-sdk also found nothing. Core docs tools not tested successfully.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): partial. 1 of 3 read calls passed anonymously; the docs fetch and search returned no documentation. Evidence: live endpoint probe, Nov 11, 2026.
Transport (tested 2026-11-11): Streamable HTTP
Token cost (estimate): approx. 588 tokens, cl100k estimate (5 tools, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 4 read, 0 write (state-changing), 1 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
fetch_generic_documentation— readfetch_generic_url_content— readmatch_common_libs_owner_repo_mapping— unclassifiedsearch_generic_code— readsearch_generic_documentation— read
remote handshake listed tools without credentials; no recorded key or OAuth
Score 80/100 · Tools 5 · Token cost approx. 588 tokens · Compare · Last tested 2026-11-11 · Server version 1.1.0 · Remote endpoint https://gitmcp.io/docs (streamable-http) · Repo idosal/git-mcp
Summary: GitMCP (official, remote) completed an MCP handshake without credentials and exposed 5 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 5
- Context cost
- approx. 588 tokens, cl100k estimate (5 tools, measured 2026-11-11; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-11
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://gitmcp.io/docs reachable over streamable-http (HTTP 200) in 20.7s; no install step for remote servers. |
| handshake | pass | 30 | MCP initialize (protocol 2025-03-26, server GitMCP 1.1.0) + tools/list over streamable-http succeeded with no credentials; 5 tools listed in 20.7s. Tool calls may still need a key. |
| maintenance | partial | 5 | Repo pushed 186 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (vendor repo README (github.com/idosal/git-mcp)). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 588 tokens, cl100k estimate for 5 tools · about 7% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-11
- Install from the registry (remote endpoint: connection only)
- We connected with no credentials and asked for its tool list: it listed 5 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not checked (remote-only): hosted endpoint, version unknown.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-11 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
29860def437c: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "gitmcp-remote",
"version": null,
"registry": "remote",
"status": "working",
"tested": "2026-11-11",
"tools_count": 5,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"Endpoint https://gitmcp.io/docs reachable over streamable-http (HTTP 200) in 20.7s; no install step for remote servers."
],
"handshake": [
"pass",
30,
"MCP `initialize` (protocol 2025-03-26, server GitMCP 1.1.0) + `tools/list` over streamable-http succeeded with no credentials; 5 tools listed in 20.7s. Tool calls may still need a key."
],
"maintenance": [
"partial",
5,
"Repo pushed 186 days before test."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (vendor repo README (github.com/idosal/git-mcp))."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
https://gitmcp.io/docs
Tools listed
fetch_generic_documentation, fetch_generic_url_content, match_common_libs_owner_repo_mapping, search_generic_code, search_generic_documentation
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"gitmcp-remote": {
"type": "http",
"url": "https://gitmcp.io/docs"
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. No install step: it is a remote server at https://gitmcp.io/docs.
- Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (5 in our test).
{
"mcpServers": {
"gitmcp-remote": {
"type": "http",
"url": "https://gitmcp.io/docs"
}
}
}Test history
- 2026-11-11: New
Related: Best docs MCP servers · Troubleshooting: Protocol version mismatch (HTTP 400)
FAQ
Is GitMCP deprecated?
No. gitmcp-remote was not deprecated or archived when we last tested it on 2026-11-11.
What replaces GitMCP?
Nothing; GitMCP (official, remote) is not deprecated as of 2026-11-11.
Does GitMCP need an API key?
No. It completed an MCP handshake with no credentials and listed 5 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.