Audit MCPServer constructor parameters

From the V2 checklist in #1253:

We need to recheck the constructor parameters of the MCPServer class. I did remove and refactor a bit, but we need to audit it a bit better.

PR #1732 renamed FastMCP to MCPServer and moved transport-specific options (host, port, stateless_http, etc.) to run(). However, the constructor still has parameters that may need further review:

• Are all remaining constructor parameters appropriate for the constructor vs. run()?
• Are there parameters that should be removed, renamed, or have their defaults reconsidered?
• Is the constructor signature clean and minimal for the common case?

This is a follow-up audit to ensure the MCPServer API surface is well-designed before V2 stabilizes.

Ref: Kludex's V2 checklist in #1253, follow-up to #1732

Commencez par examiner le constructeur de MCPServer et son point d’entrée run(), ainsi que les changements de PR #1732 et la checklist V2 dans #1253. Vérifiez quels paramètres appartiennent à chaque API et documentez ou testez les décisions qui en résultent afin que le constructeur soit minimal et adapté à V2.