Verify the Connection

• Connection diagnostics (no MCP host needed): run the server with --test:
  SystemWeaverMCP.exe --test
  It resolves the credential, connects to the broker, prints the outcome (host/user/connected, no secret) and exits.
• From the AI host: confirm the "systemweaver" MCP server shows as connected, then call the mcp_server_info tool - it reports the server version, the connected broker (user/host/port), the auth method, a live connected flag, and whether the license grants the product (licensed, licenceState). It never returns a secret. With licenceState notLicensed, a license must be assigned; only mcp_server_info is served until then.
• If it reports connected=false, call it again rather than restarting the server: the call starts an attempt to re-establish the connection, and that attempt deliberately does not delay the response, so the restored state appears on the following call.

Security notes

• Secrets live only in the DPAPI store (current user, this machine). The launcher config and appsettings.json carry NO connection details or secrets.
• A missing / tampered / wrong-user / corrupt store is treated as "no profile" (fail-closed): the server reports the missing-credential message and does not connect with a partial profile.
• Write axes are off by default. Enable only the mutation surface you need.
• The server only reads the store; provisioning (writing) is exclusively the CredentialTool.