Changelog
New features, improvements, security fixes, and bug fixes, newest first.
Private beta access, and a tool list that tells the truth
Version 0.7.2 ·
Accounts open to a named list of addresses while the private beta runs. The MCP tool list now shows only the tools a deployment can actually run.
New features
-
Signup opens to a named list of addresses
A deployment can now run in three states: closed, open to a list of addresses, or open to anyone. In the middle state the whole product works normally, and only the listed addresses can create an account. This is what runs during the private beta. An address that is not on the list gets the same answer whether or not it already has an account, so the refusal says nothing about who has signed up.
Improvements
-
The MCP tool list shows only the tools that work
The Slack and Linear tools were offered to agents even where the connectors are not configured, so an agent could pick a tool that could only fail. A tool now appears in the list only where it can run, and calling one that is absent returns the same error as calling a tool that does not exist.
-
Security, privacy, and terms pages you can read without an account
The privacy policy, the terms, the subprocessor list, and a new security page are published on looptro.dev. They were only reachable inside the app before, where search engines could not read them. The security page also states what Looptro does not have yet, including SOC 2 and ISO 27001, which are in progress.
Security fixes
-
Updated the TLS library for an advisory low
The TLS library accepted some handshake messages that arrived at the wrong point in the exchange. Looptro was not known to be affected, and the library is updated to the fixed version.