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.

GitHub

NPM · @ABHISHEKMCP/GITHUB · SCANNED SEP 20

GitHub via MCP: search, repos, issues, PRs, files, notifications. OAuth device flow or token.

Available components

0 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 116 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Abhishekkumar2021/mcp-suite). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 83 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 664 tokens (~41/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 54% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the GitHub MCP server?

GitHub runs locally as an npm package, launched with npx -y @abhishekmcp/github. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @abhishekmcp/github

# add to Claude Code
claude mcp add abhishekkumar2021-github -- npx -y @abhishekmcp/github
// .cursor/mcp.json
{
  "mcpServers": {
    "abhishekkumar2021-github": {
      "command": "npx",
      "args": [
        "-y",
        "@abhishekmcp/github"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "abhishekkumar2021-github": {
      "command": "npx",
      "args": [
        "-y",
        "@abhishekmcp/github"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add abhishekkumar2021-github -- npx -y @abhishekmcp/github
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "abhishekkumar2021-github": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@abhishekmcp/github"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add abhishekkumar2021-github --command npx --arg -y --arg @abhishekmcp/github
# ~/.hermes/config.yaml
mcp_servers:
  abhishekkumar2021-github:
    command: "npx"
    args: ["-y", "@abhishekmcp/github"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "abhishekkumar2021-github": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@abhishekmcp/github"
      ]
    }
  }
}
# add to Vellum
assistant mcp add abhishekkumar2021-github -t stdio -c npx -a -y @abhishekmcp/github
// mcp.json
{
  "mcpServers": {
    "abhishekkumar2021-github": {
      "command": "npx",
      "args": [
        "-y",
        "@abhishekmcp/github"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@abhishekmcp/github@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Abhishekkumar2021/mcp-suite
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Abhishekkumar2021/mcp-suite/.github/workflows/publish.yml@refs/tags/github-v0.2.0
Rekor log index 1993230895
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:3b354388a53cd1d775f48c05a6a99280fbbc3813aafeaad218660b88f05ce29ffc40ea77d229705d395719ae59f1420f7bc630e7e016aeb4941a3341a

Background: How many MCP packages publish verified provenance →

Dependencies 116 packages
Packages resolved 116
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~664 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
add_issue_comment ~55

Add a comment to an issue or pull request.

NameTypeReqDescription
bodystringyes
numberintegeryes
ownerstringyesRepository owner (user or org)
repostringyesRepository name

No output schema declared.

No examples provided.

create_issue ~52

Open a new issue in a repository.

NameTypeReqDescription
bodystring
ownerstringyesRepository owner (user or org)
repostringyesRepository name
titlestringyes

No output schema declared.

No examples provided.

get_file_contents ~71

Read a file (decoded) or list a directory in a repo, at an optional ref.

NameTypeReqDescription
ownerstringyesRepository owner (user or org)
pathstringyes
refstringBranch, tag, or commit SHA
repostringyesRepository name

No output schema declared.

No examples provided.

get_issue ~46

An issue's details plus its first comments.

NameTypeReqDescription
numberintegeryes
ownerstringyesRepository owner (user or org)
repostringyesRepository name

No output schema declared.

No examples provided.

get_pull_request ~51

A PR's details (diff stats, merged state, body).

NameTypeReqDescription
numberintegeryes
ownerstringyesRepository owner (user or org)
repostringyesRepository name

No output schema declared.

No examples provided.

get_repo ~42

Repository metadata (stars, language, default branch, license).

NameTypeReqDescription
ownerstringyesRepository owner (user or org)
repostringyesRepository name

No output schema declared.

No examples provided.

github_login ~44

Authenticate via GitHub OAuth device flow. First call returns a code + URL to open; run it again after authorizing to finish. (Or set GITHUB_TOKEN to skip.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

github_logout ~15

Clear the cached GitHub token.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_issues ~62

List a repo's issues (excludes PRs).

NameTypeReqDescription
limitinteger
ownerstringyesRepository owner (user or org)
repostringyesRepository name
statestringFilter by state (default open)

No output schema declared.

No examples provided.

list_notifications ~21

Your unread GitHub notifications.

NameTypeReqDescription
limitinteger

No output schema declared.

No examples provided.

list_pull_requests ~58

List a repo's pull requests.

NameTypeReqDescription
limitinteger
ownerstringyesRepository owner (user or org)
repostringyesRepository name
statestringFilter by state (default open)

No output schema declared.

No examples provided.

rate_limit ~18

Your remaining GitHub API requests and reset time.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_code ~40

Search code across GitHub (e.g. 'addEventListener repo:owner/name').

NameTypeReqDescription
limitinteger
querystringyes

No output schema declared.

No examples provided.

search_issues ~34

Search issues and pull requests (GitHub search syntax).

NameTypeReqDescription
limitinteger
querystringyes

No output schema declared.

No examples provided.

search_repos ~33

Search GitHub repositories (GitHub search syntax).

NameTypeReqDescription
limitinteger
querystringyes

No output schema declared.

No examples provided.

whoami ~22

Show the authenticated GitHub user (and how the token was obtained).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the GitHub MCP server?

GitHub is an MCP server listed in the public MCP registry as io.github.Abhishekkumar2021/github. GitHub via MCP: search, repos, issues, PRs, files, notifications. OAuth device flow or token. This page covers its npm package (@abhishekmcp/github).

Is the GitHub MCP server safe to use?

GitHub scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 GitHub MCP server expose?

GitHub exposes 16 tools: github_login, github_logout, whoami, search_repos, search_code, and 11 more. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.

Is the GitHub MCP server still maintained?

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

What licence is the GitHub MCP server under?

GitHub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.