maxctrl or the REST API command to get connected slave hosts to the binlogrouter

maxctrl show service <binlog-service-name>

reports only the total connection count (e.g., "Current Connections: 2"), but no per-client details (IP/host, server_id, binlog position, etc.).
The corresponding REST API endpoint /v1/services/<service-name> provides the same high-level stats.
There is no visible maxctrl show binlogrouter, list slaves, or module-specific command for connected slaves.
The only functional method found is connecting to the listener port with a replication user and running SHOW SLAVE HOSTS; which works but is less ideal for automated monitoring (requires credentials, direct network access to the port, and output parsing).

Is there currently any way to retrieve a list of connected replication slaves — including at least IP/host and server_id — through maxctrl or the REST API?