Unverified50% confidenceDecision RuleExact time
Installing GitHub via the default MCP server method requires creating a GitHub personal access token (PAT); classic tokens are recommended, with all Repo functions enabled, User optionally enabled, but deletion of Repo permissions is not recommended.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/21/2026
First Seen
Valid until: 1/19/2027
Sources
Related Entities
Related Claims
UnverifiedGitHub push protection covers command-line pushes, commits created in the GitHub UI, file uploads, REST API requests, and GitHub MCP server interactions limited to public repositories.76% similarUnverifiedWhen GitHub MCP is called, it can return MCP-native UI, such as displaying a GitHub user card directly instead of plain text.70% similarUnverifiedGitHub Actions and fine-grained personal access tokens (PATs) can accomplish multi-environment deployment and automated workflows without sharing accounts.69% similarUnverifiedBy default, anyone with write access to a repository can bypass GitHub push protection by specifying a bypass reason.69% similarUnverifiedThe GitHub team shipped support for the new MCP specification to GitHub MCP Server approximately three weeks before the latest MCP spec was officially released.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1080046API
curl https://kongchang.com/api/v1/knowledge/claims/1080046MCP
get_claim(id=1080046)