The MCP server SHOULD have an informational GET endpoint

[esnible]

Currently, when the MCP server is deployed, the route "/mcp*" is sent to the MCP server.

Thus, a user can do

curl http://mcp.127-0-0-1.sslip.io:8090/mcp/rutabaga and get the output

Hello, World!  BTW, the MCP server is on /mcp

This provides a quick test that the MCP server is operational, and gives the user a hint on what the PATH part of the URL should look like.

It would be helpful to the user if other paths, e.g. /, also output the same informational message instead of returning 404

An HTTP GET on /mcp may choose to block, as we do now. Although we may want to have the server complain if an expected Accept header isn't present.

[david-martin]

Moving this out of the 0.5 milestone as I wouldn't see this as a blocker for that milestone, given how it ties to a developer preview.
It sounds like a good thing to have.
I'm not sure about 'should' at this time.
Are there provisions for this in the MCP spec, or is this a best practice you have seen?