Pep–Whisperer: Inhibitory peptide design

Naama Hurwitz*, Daniel Zaidman, Haim J. Wolfson

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

3 Scopus citations


Designing peptides for protein–protein interaction inhibition is of significant interest in computer-aided drug design. Such inhibitory peptides could mimic and compete with the binding of the partner protein to the inhibition target. Experimental peptide design is a laborious, time consuming, and expensive multi-step process. Therefore, in silico peptide design can be beneficial for achieving this task. We present a novel algorithm, Pep–Whisperer, which aims to design inhibitory peptides for protein–protein interaction. The desirable peptides would have a relatively high predicted binding affinity to the target protein in a given protein–protein complex. The algorithm outputs linear peptides which are based on an initial template. The template could either be a peptide which is retrieved from the interaction site, or a patch of nonconsecutive amino acids from the protein–protein interface which is completed to a linear peptide by short polyalanine linkers. In addition, the algorithm takes into consideration the conservation of the amino acids in the ligand-protein binding site by using evolutionary information for choosing the preferred amino acids in each position of the designed peptide. Our algorithm was able to design peptides with high predicted binding affinity to the target protein. The method is fully automated and available as a web server at

Original languageEnglish
Pages (from-to)1886-1895
Number of pages10
JournalProteins: Structure, Function and Bioinformatics
Issue number11
StatePublished - Nov 2022


FundersFunder number
Blavatnik Family Foundation


    • in silico mutations
    • peptide design
    • peptides
    • protein-peptide docking
    • protein–protein interaction inhibitors


    Dive into the research topics of 'Pep–Whisperer: Inhibitory peptide design'. Together they form a unique fingerprint.

    Cite this