GitHub remote: two public read operations

A historical connection test with expected results, an observed tool inventory and explicitly unverified write permissions.

2026-09-07T12:44:31.631Z · https://api.githubcopilot.com/mcp/

This report describes the test on the stated date. It does not measure current service health.

Content updated: 2026-09-08

Expected and observed results

• initialize: passed
• tools/list: passed
• search_repositories: passed

  Returned the requested public repository

  {
    "query": "repo:github/github-mcp-server",
    "perPage": 1
  }

• list_issues: passed

  Returned numbered issues belonging to the requested public repository

  {
    "owner": "github",
    "repo": "github-mcp-server",
    "perPage": 1,
    "state": "OPEN"
  }

Environment and authentication

darwin · Node v25.9.0 · @modelcontextprotocol/sdk 1.30.0

Bearer · github/github-mcp-server

Tests and limitations

Effective scopes and the remote version are unknown. Two successful reads establish neither write permissions nor a complete automation. Private user reports are not added here.

Reproduce the test

Initialize MCP, read the complete tools/list, then call search_repositories for repo:github/github-mcp-server and list_issues for that public repository. Independently compare the repository and the issue number/title with the GitHub REST API. Provide credentials locally. Do not use private repositories or write operations.

GitHub MCP Server · GitHub REST

Machine-readable original report · GitHub