Unlock SaaS is listed as active in the registry but did not answer our last check. It exposes 3 tools.
Playbook engine: non-dev founders land first paying customer in 60 days or refund
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
claude mcp add unlocksaas --transport http https://unlocksaas.com/api/mcp
{
"mcpServers": {
"unlocksaas": {
"url": "https://unlocksaas.com/api/mcp"
}
}
}
[mcp_servers.unlocksaas]
url = "https://unlocksaas.com/api/mcp"
{
"mcpServers": {
"unlocksaas": {
"url": "https://unlocksaas.com/api/mcp"
}
}
}
{
"mcpServers": {
"unlocksaas": {
"url": "https://unlocksaas.com/api/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_churn_cost
get_ltv
project_revenue
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://unlocksaas.com/api/mcp | streamable-http | answering | 60 ms | 3 min ago |
Answers built from our own checks of this server.