This belongs in a different mental category from everything around it: there is nothing to evaluate until you build something. What is worth judging is the platform's defaults, and the one that matters is authentication being on by default rather than a checkbox — a self-built MCP endpoint left open is the classic way to publish an internal workflow to the internet by accident.
Not one server but a factory. You compose actions from Boltic primitives — workflows and other building blocks — and the platform hosts the result. Every server you create gets its own URL, shown in the Connect MCP dialog.
The tools are whatever you built. Boltic calls them actions, and the documented types include exposing a Boltic workflow as a callable tool.
A Boltic workspace. Authentication is built into the generated endpoints — OAuth 2.0 or a bearer token — so a server you create is not open by default.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen