404 error with IP-restricted Organization.

[hrsuzuki]

Describe the bug

The following error occurs when used with an IP-restricted Organization.

The following is the output from the chat when the ISSUE is created from the CopilotAgent.

I attempted to create an issue, but encountered a "404 Not Found" error.
This typically occurs if the repository name or owner name is incorrect, or if you lack sufficient access permissions.
Please verify the existence of the repository and your access permissions, then try again.
Let me know if you need further assistance.

Affected version

Steps to reproduce the behavior

1. Create a GitHub Personal Access Token (PAT)
   1.1. Open your GitHub Settings › Developer settings › Personal access tokens page.
   1.2. Click Generate new token and choose either Fine‑grained or Classic.
   1.3. Grant the scopes required for the MCP server to access the GitHub API (see GitHub docs for details).
   1.4. Copy the generated PAT; you will need it in Step 3.

2. Install the MCP Server (One‑Click Install — Recommended)
   2.1. In the repository README, click the Install with Docker in VS Code button.
   2.2. Follow the on‑screen prompts to start the automated setup inside VS Code.

3. Configure Your PAT
   3.1. During installation—or right after it finishes—paste the PAT from Step 1 when prompted.
   3.2. Save the settings to ensure the server can authenticate with GitHub.

4. Prepare VS Code
   4.1. Reload VS Code so the new configuration is applied.
   - Windows / Linux: Press Ctrl + Shift + P, type Reload Window, and press Enter.
   - macOS: Press Cmd + Shift + P, type Reload Window, and press Return.

5. Run in Copilot Agent Mode
   5.1. Start VS Code in Copilot Agent mode (insert any project‑specific commands or extensions here if applicable).
   5.2. Verify that the MCP server integrates correctly with the Copilot Agent environment.
   5.3. In the currently active repository, instruct the Copilot Agent to create a new GitHub Issue

Expected vs actual behavior

Organization without IP restrictions worked normally.

Logs