Cant seems to get Huntress working with Copilot,

MCP server returns non-compliant response to

initialized

The Huntress MCP endpoint at https://api.huntress.io/v1/mcp returns a JSON body of null in response to

initialized JSON-RPC notifications.

Per the MCP specification (Streamable HTTP transport) and JSON-RPC 2.0, notifications must not produce a response the server should return HTTP 202 Accepted with an empty body.

This breaks integration with Microsoft Copilot Studio, which appears to validate the response and fails the handshake. The initialize and list methods work correctly; the failure is isolated to notification handling.

Tested via Postman:

Request:

mcp

body

initialized","params":{}}

Response: body = null (should be empty)

Please update the MCP server to return 202 with no body for notification methods.