Agent MCP Directory

GitHub: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for GitHub at api.githubcopilot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyGitHub
Domaingithub.com
CategoryDeveloper Tools (Ora leaderboard category)
MCP serverSign-in required (OAuth without client registration)
Tranco rank34 on the list of 4 November 2026
Ora score65, grade C; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for github.com, a vendor-published score)
Company found throughthe vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://api.githubcopilot.com/mcp/
How it was foundlisted in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:06 UTC
Handshake time1,544 ms over 1 attempt
Documentationgithub.com

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

3 connections on 4 November 2026, read-only methods only

  • 19:55:52Z https://api.githubcopilot.com/mcp/ sent initialize result auth-required (HTTP 401) 1232 ms
  • 20:01:27Z https://api.githubcopilot.com/mcp/ sent initialize result auth-required (HTTP 401) 1664 ms
  • 20:06:07Z https://api.githubcopilot.com/mcp/ sent initialize result auth-required (HTTP 401) 1544 ms

Authentication

Auth typeOAuth without client registration
What the challenge saidBearer error="invalid_request", error_description="No access token was provided in this request", resource_metadata="https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp/"
Protected resource metadataapi.githubcopilot.com
Authorization server metadatagithub.com
Auth as listed by a registryAPI Key (a claim, not checked by connecting)

The sign-in route, step by step

  1. Request https://api.githubcopilot.com/mcp/ without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the OAuth metadata at https://github.com/.well-known/oauth-authorization-server/login/oauth. It lists no registration endpoint.
  3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one.
  4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for GitHub. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileFound: raw.githubusercontent.com (JSON, via vendor docs).
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversYes
SmitheryYes: compoid/compoid-mcp
GlamaNot checked: Glama's API needs a key and attribution terms.