Provide MicroProfile Health Check

[sberyozkin]

Right now, MCP clients built on top of LangChain4j issue request to the actual SSE or Streamable HTTP endpoints to determine if the MCP server is up, but it does not work if the MCP server is secured and it would be good to be able to get a dedicated MCP server health status check without actually having to open an SSE or Streamable HTTP channel by issuing a basic HTTP /q/health query.

For example, if the handlers are up and running, ready to process SSE or Streamable HTTP requests, then the MCP server status can be considered healthy, as far as the MicroProfile Health Check status is concerned

[mkouba]

For example, if the handlers are up and running, ready to process SSE or Streamable HTTP requests, then the MCP server status can be considered healthy, as far as the MicroProfile Health Check status is concerned

The SSE/streamable transport is ready once the HTTP server is ready so I believe that the built-in checks should be enough. In other words, I'm not sure what else needs to be added.

[sberyozkin]

@mkouba Right, just to have an MCP server check specific section in the Health Check JSON response, say, named mcp-server, may be it will have only status: UP to start with ?

It won't add anything extra in addition to the general status: UP I can see by only adding smallrye-health, but may be a few more specific details will be added later (one section per the MCP server endpoint, some other extra details)...

I'm not 100% sure, just guessing that having a dedicated check section may be better...

[mkouba]

I'm not 100% sure, just guessing that having a dedicated check section may be better...

I'm not 100% convinced either ;-). I can imagine that we could add a healtch check that could list all MCP server configurations but I'm not sure if it should be a liveness or readiness check and the usefulness is IMO disputable until we find more specific details that should be included 🤷.