# GitHub MCP Server vs GitMCP (slim)

> GitHub scores 72.4 (BB) to GitMCP's 40.2 (E) for code repositories. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/github-mcp-server-vs-gitmcp.md (~4,800 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/compare/github-mcp-server-vs-gitmcp.json · canonical https://www.anchorterminal.com/compare/github-mcp-server-vs-gitmcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

GitHub MCP Server scores 72.4 (BB) on agent readiness against GitMCP's 40.2 (E), and leads in 6 of 7 scored categories. GitMCP leads on payments & pricing. Both do code repositories.

- GitHub MCP Server: BB 72.4, rank #128 of 1486 · https://www.anchorterminal.com/tools/github-mcp-server.min.md
- GitMCP: E 40.2, rank #1308 of 1486 · https://www.anchorterminal.com/tools/gitmcp.min.md
- GitHub MCP Server, good for Agents that read and change GitHub repositories, issues, pull requests and Actions, from triage bots to coding agents. Ahead on Reliability, 65 against 15; Schema & documentation, 83 against 56; Agent ergonomics, 78 against 58; Security & auth, 84 against 42; Maintenance & community, 93 against 8; Transparency & trust, 84 against 36. Also Agent-ready, a grade of BB or better; Runs on your own machine.
- GitMCP, good for Quick, keyless library docs for public GitHub projects in a coding agent. Ahead on Payments & pricing, 60 against 40. Also No key needed to call it.

| Category | GitHub MCP Server | GitMCP |
| --- | --- | --- |
| Reliability (16%) | 65 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 56 |
| Agent ergonomics (13%) | 78 | 58 |
| Security & auth (14%) | 84 | 42 |
| Payments & pricing (10%) | 40 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 93 | 8 |
| Transparency & trust (7%) | 84 | 36 |

| Fact (where they differ) | GitHub MCP Server | GitMCP |
| --- | --- | --- |
| Vendor | GitHub | Ido Salomon (GitMCP open-source project) |
| Hosted endpoint | `https://api.githubcopilot.com/mcp/` | `https://gitmcp.io/{owner}/{repo}` |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | None |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 92 | 4 |
| llms.txt | yes | no |
| MCP registry | `io.github.github/github-mcp-server` | not listed |
| Last release | 2026-10-21 | 2026-05-08 |
| Terms last updated | 2026-04-27 | no document linked |
| Privacy policy last updated | 2026-04-27 | no document linked |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 32k stars | 8.5k stars |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Maintenance & community, GitHub MCP Server +85: GitHub MCP Server 93 (v2.0.3 on 21 October 2026 (30). Thirteen releases since 3 August, from v1.9.0 on 10 August to v2.0.3, among them v2.0.0 on 7 October (20). 159 open issues and triage labels within days per the 1 October check, not re-read on 1 November (GitHub's pages answered 403). An AI triage workflow and an inactive-issue closer run. We couldn't read reply times (18). Listed in the official MCP registry as io.github.github/github-mcp-server at 2.0.3, marked latest and published on 21 October (15). Go CI, lint, code scanning, licence checks and a tool-diff check on pull requests (10).); GitMCP 8 (The last commit on main is 8 May 2026, 182 days before this check, and there are no tags or releases (0). Nothing in the last 90 days (0). Since May, outside issues and pull requests (#244 to #271, among them the security report #249 and fixes #256, #267 and #250) have gone without a maintainer reply or merge (3). Not found in the official MCP registry under any namespace (0). A run-tests workflow with vitest and a Playwright end-to-end workflow exist on push and pull request (5). 0 + 0 + 3 + 0 + 5 = 8.)
- Reliability, GitHub MCP Server +50: GitHub MCP Server 65 (Scored as a hosted MCP server, since the remote endpoint is the default install. githubstatus.com is a Statuspage with component history (20). In the 90 days from 3 August the history lists 64 incidents, most of them Copilot models, Actions, webhooks or billing. Two hit the API broadly for an hour or more. On 17 August, 13:28 to 21:15 UTC, web and API errors peaked at about 20 per cent across Issues, Pull Requests, APIs and Actions, most services recovering by 16:36. On 13 September, 08:43 to 10:44 UTC, about 28 services were degraded after a job overloaded the cluster holding permission data read on nearly every authenticated request. The rest are partial and read as minor, as this run reads partial incidents. The 23 September failures, read on 1 October as a roughly 19-hour API incident, were confined to the Azure Central US region with API errors mitigated by 10:58 UTC. The 7 October write outages lasted about 19 minutes in total, 6 October 6 minutes, 26 October REST latency 17:59 to 18:40 UTC, 30 October a burst from 14:21 to 14:30 UTC. Two majors (5). None names the MCP server. REST limits are published (5,000 an hour per user, 15,000 for Enterprise Cloud, 900 points a minute secondary) (15). 403 and 429 responses carry `retry-after` or `x-ratelimit-reset`, with advice to wait and back off (15). The SLA page couldn't be read on 1 October and github.com refused our reader on 1 November, so we score it absent (0). Versioned 2.x with no preview label on the README or remote-server docs (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.); GitMCP 15 (Scored as a hosted MCP server. No status page found (0) and so no readable incident history (5). The maintainer confirmed on issue #245 that gitmcp.io was throttled by Cloudflare for a few hours in May 2026, outside the 90-day window. No rate limits are documented (0) and nothing on 429 or retries (0). No SLA (0). The service is live with no beta or preview label (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.)
- Transparency & trust, GitHub MCP Server +48: GitHub MCP Server 84 (MIT, with third-party licences listed per platform (30). Data handling falls under GitHub's general privacy statement and DPA. There's no MCP-specific statement of what the remote server logs or keeps (20). Renamed tools keep working through aliases listed in docs/tool-renaming.md, but the table has no removal dates (12). The local server's metrics sink is a no-op. The hosted server records `fields` usage and payload sizes, which the source shows and the docs don't mention (15).); GitMCP 36 (Apache-2.0, with the whole service in the public repository (30). The README says the service stores no personal data or queries and keeps no repository content permanently, but there is no privacy policy or terms page (8). No deprecation policy or dated notices; SSE was removed on 8 May 2026 while the README still shows an SSE config for VS Code (0). The hosting stack (Cloudflare Workers, Workers AI, Vectorize, an Analytics Engine dataset) is visible in wrangler.jsonc but no processor is named for users, and invocation logs were turned off on 8 May (5). 30 + 8 + 0 + 5 = 43.)
- Security & auth, GitHub MCP Server +42: GitHub MCP Server 84 (OAuth with scopes is the remote default, with fine-grained PATs and GitHub App tokens for headless use, all in the `Authorization` header. v1.11.0 added per-call OAuth scope challenges (30). `--read-only`, `/readonly` URLs and `X-MCP-Readonly` drop write tools. `delete_repository` asks the user to type the full repository name through elicitation. `delete_file` and the other destructive tools run without a confirmation step (17). Lockdown mode filters public-repository content from authors without push access, and the README says plainly it's a best-effort filter, not a boundary. July 2026 commits made lockdown fail closed (13). MCP calls show in GitHub's audit log as ordinary API calls, and the governance doc says MCP-specific audit logs aren't available yet (8). SECURITY.md with coordinated disclosure, GitHub's bug bounty (open-source repositories are out of scope for rewards), two advisories published in public in 2026, and github.com's security.txt expired per the 30 September check (16).); GitMCP 42 (No credentials at all, so nothing to leak or scope (20). Every tool is a read of public content (15). Repository docs, code and fetched URLs reach the model unmarked, and fetch_generic_url_content fetches any absolute URL a document mentions, with no prompt-injection guidance in the README (2). No per-call visibility for the caller (0). SECURITY.md routes reports to a Google Form, but the server-side request forgery report in issue #249 (12 June 2026) and its proposed fix #256 have had no maintainer reply in almost five months. No certifications or bounty (5). 20 + 15 + 2 + 0 + 5 = 42.)
- Schema & documentation, GitHub MCP Server +27: GitHub MCP Server 83 (Every tool has a JSON Schema input, snapshotted in the repository for review (25). docs.github.com/llms.txt exists per the 30 September check, and the server docs are Markdown (10). Descriptions are short (median 82 characters) and mostly state purpose. Some say when to use them (`search_code` for exact symbols) or point elsewhere (`label_write` names `update_issue`), most don't (12). Enums for state, order and merge method, `perPage` bounded 1 to 100, required fields marked. Three tools take free-form objects (`create_repository_ruleset`, `actions_run_trigger`, `projects_write`) (12). The README lists every parameter per tool. Errors come back as tool results with GitHub's message, and the error-handling doc is aimed at contributors, not models (9). Semver releases with notes, and a tool-renaming doc with a table of 25 deprecated aliases that still resolve (15). Since v2.0.0 (7 October 2026) repository, issue, pull request, search and other tools also publish output schemas and typed `structuredContent` to clients that negotiate MCP protocol 2026-07-28 or newer, with older clients getting the earlier text results. Score unchanged.); GitMCP 56 (Every tool registers a zod input schema, so inputs are typed JSON Schema (25). There is no llms.txt for GitMCP itself; the README on GitHub is the only Markdown documentation (5). Descriptions are generated per repository and say what each tool reads and when it helps ("Useful for general questions. Always call this tool first if asked about owner/repo"), but not when to avoid one (12). Inputs are a query string and an optional page number, with no enums or constraints beyond types (9). The README has three worked examples and no documented error responses (5). No versioning, tags, releases or changelog (0). 25 + 5 + 12 + 9 + 5 + 0 = 56.)
- Agent ergonomics, GitHub MCP Server +20: GitHub MCP Server 78 (92 documented tools across 22 toolsets, about 121,000 characters or 30,000 tokens with everything on. The default five toolsets load 45 tools, about 13,600 tokens (5). Toolsets, per-tool selection, `/readonly` URLs, `X-MCP-Toolsets` headers and scope-based hiding of tools a PAT can't use add back 10. Page, cursor and `perPage` paging, plus a `fields` parameter on list and search tools to trim responses. Issue #3236 says `pull_request_read` `get_files` always returns full patches (18). Errors are tool results with GitHub's message, and OAuth calls get a scope challenge instead of a bare 403 (16). Every tool sets `readOnlyHint`, eight write tools set `destructiveHint: true`, but 27 of 35 write tools leave `destructiveHint` unset (open issue #3281) and no read tool sets `idempotentHint`. `merge_pull_request` takes an `expectedHeadSha` guard (14). Default toolsets, `owner` and `repo` as the usual required pair, and official Octokit SDKs in several languages (15).); GitMCP 58 (Four tools per repository endpoint and five on gitmcp.io/docs, each short (25). Code search pages 30 results with a page number, and documentation search returns matched chunks instead of the whole file, but there is no size control on the fetch tool (10). Errors come back as tool text with no documented codes (5). Every tool is a read and the source sets readOnlyHint, but issue #266 reports the annotations are passed in a position the MCP SDK ignores, and the fix #267 is unmerged (8). No parameters to set up and nothing to configure; there are no SDKs, which a keyless MCP endpoint doesn't need (10). 25 + 10 + 5 + 8 + 10 = 58.)