Is it a duplicated question?
Please search in Issues without filters: https://github.com/louislam/uptime-kuma/issues?q=

I have not been able to find this feature request prior.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I am working on a Blockchain project, and while a server/ip/port may still be up and open it does not necessarily mean that the blockchain is working properly. In my use case, I would like to be able to do a WSS call and verify the response is what is expected.

Describe the solution you'd like
A clear and concise description of what you want to happen.

_WS/WSS added as an item type. Support to make a request via the specified WSS server and verify the response, similar to how the HTTP(S) - Keyword monitor type works.

(this next part is a want, not a need)
This is a stretch, but the ability to perform operations on the response to test the next response would be amazing, for example, if I am wanting to make sure a counter on the WSS server went up I could to a check such as Last # < New #. or even just +1 the number like its a for loop or something. _

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Ive attempted to use the HTTP/TCP/Port options but they all fall short because of the nature of how WSS works, due to the fact that it is an HTTP connection that is then upgraded to a TCP connection, it is in this middle ground of item types currently supported within Uptime Kuma.

Additional context
Add any other context or screenshots about the feature request here.

This is a major improvement that will allow uptime Kuma to be used as an API status page as well, allowing even further integration within any service needed.
Additionally, if you know of a way to get this to work with the current implementation I would love to hear it :)