8 minTime to key
NoNo-human path
3Human gates
7/10Onboarding score
CAPTCHAEmail verificationMandatory 2FA
Fastest path to a key
- CAPTCHAhuman signs up at github.com/signup: email, password, username, visual/audio captcha puzzle, email 'launch code' verification
- `gh auth login` (web device flow: one-time code entered at github.com/login/device)
- `gh auth token` prints an OAuth token usable as an API key (scopes repo, read:org, gist); or Settings > Developer settings > fine-grained PAT
- MCP: `claude mcp add-json github '{"type":"http","url":"https://api.githubcopilot.com/mcp","headers":{"Authorization":"Bearer <PAT>"}}'` (PAT required for Claude Code). OAuth only works in hosts with a pre-registered …
- Working API key
Biggest gap
Remote MCP OAuth only works for hosts with a pre-registered GitHub App (no DCR), so most CLI agents fall back to copying a PAT by hand
Worth copying
Docs Article/Search APIs that return markdown, documented in llms.txt as the preferred LLM access path
Sources (6) · checked 2026-10-11
- https://docs.github.com/llms.txt
- https://docs.github.com/api/article/body?pathname=/en/rest/quickstart
- https://raw.githubusercontent.com/github/github-mcp-server/main/README.md
- https://raw.githubusercontent.com/github/github-mcp-server/main/docs/installation-guides/install-claude.md
- https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp
- https://github.com/signup
56Readiness score / 100
L2 Agent-documentedBeats 76% of 1,846 companies
Access20/20
Context18/20
Interfaces8/32
Onboarding8/19
Trust2/9
llms.txt · root
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- PASSllms-full.txt exists3
- PASSDocs available as markdown6
- FAILSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- PASSSelf-serve API keys5
- PASSFree tier or test mode3
- FAILAgent manifests4
- PASSsecurity.txt2
- FAILPublic status page3
Your fix pack: 9 changes, up to +44 points
Each change is ready to paste, filled in for github.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/github.com)