The server is not started, neither with Docker nor manually using npm.

[effuone]

I got the following warning and error when testing your tool:

[warning] FastMCP could not infer client capabilities  
{"method":"ping","jsonrpc":"2.0","id":0}  

{"jsonrpc":"2.0","method":"notifications/cancelled","params":{"requestId":0,"reason":"McpError: MCP error -32001: Request timed out"}}  

Then this unhandled error appeared:

{"jsonrpc":"2.0","method":"notifications/cancelled","params":{"requestId":0,"reason":"McpError: MCP error -32001: Request timed out"}}
node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_UNHANDLED_ERROR]: Unhandled error. ({
  error: McpError: MCP error -32001: Request timed out
      at Timeout.timeoutHandler (file:///app/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:282:49)
      at listOnTimeout (node:internal/timers:569:17)
      at process.processTimers (node:internal/timers:512:7) {
    code: -32001,
    data: { timeout: 60000 }
  }
})
    at new NodeError (node:internal/errors:405:5)
    at FastMCPSession.emit (node:events:506:17)
    at Timeout._onTimeout (file:///app/node_modules/fastmcp/dist/FastMCP.js:273:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ERR_UNHANDLED_ERROR',
  context: {
    error: McpError: MCP error -32001: Request timed out
        at Timeout.timeoutHandler (file:///app/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:282:49)
        at listOnTimeout (node:internal/timers:569:17)
        at process.processTimers (node:internal/timers:512:7) {
      code: -32001,
      data: { timeout: 60000 }
    }
  }
}

Could this be caused by an internet connection issue?
How can I fix it? I'd like to test your tool. Thanks!