MCP · Windows

MCP stays failed or pending on Windows

An MCP failure can happen at four independent layers. Reinstalling alone cannot reveal which one failed.

Updated July 11, 2026 · 6 min

Read the state first

  • failed: startup command, dependency, path, or process exit.
  • pending: unfinished authorization or network handshake.
  • connected with no tools: server capability, plugin loading, or scope issue.
SecurityNever share OAuth links, access tokens, client secrets, cookies, or complete environment dumps.

Four-step verification

  1. Process: inspect the MCP log and runtime path.
  2. Transport: distinguish stdio from HTTP and check proxy, firewall, and certificates.
  3. Identity: run a self or account tool. This proves login only.
  4. Resource: run one search and one fetch to prove discovery and reading.

Success checks

  • Status is no longer failed or pending.
  • Expected tools appear.
  • A real resource completes search → fetch.