remove server requirements, move requirements to schenario description

[ihrpr]

Instead of maintaining a separate requirements file, it's better to include the requirements per each schenario.

Now if a test fails, it outputs:

> tsx src/index.ts server --url http://localhost:3000/mcp --scenario server-initialize

Running client scenario 'server-initialize' against server: http://localhost:3000/mcp
Results saved to results/server-server-initialize-2025-11-14T16-46-16-208Z
Checks:
[
  {
    "id": "server-initialize",
    "name": "ServerInitialize",
    "description": "Server responds to initialize request with valid structure",
    "status": "FAILURE",
    "timestamp": "2025-11-14T16:46:16.237Z",
    "specReferences": [
      {
        "id": "MCP-Initialize",
        "url": "https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle#initialization"
      }
    ],
    "details": {
      "serverUrl": "http://localhost:3000/mcp",
      "connected": true
    }
  }
]

Test Results:
Passed: 0/1, 1 failed

=== Failed Checks ===

  - ServerInitialize: Server responds to initialize request with valid structure

Test basic server initialization handshake.

Server Implementation Requirements:

Endpoint: initialize

Requirements:
- Accept initialize request with client info and capabilities
- Return valid initialize response with server info, protocol version, and capabilities
- Accept initialized notification from client after handshake

This test verifies the server can complete the two-phase initialization handshake successfully.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/conformance/@modelcontextprotocol/conformance@30

commit: 23c2dc2

[pcarleton]

awesome!