Summary: Peptidase M10 serralysin C terminal
Peptidase M10 serralysin C terminal Provide feedback
Serralysins are peptidases related to mammalian matrix metallopeptidases (MMPs). The peptidase unit is found at the N terminal while this domain at the C terminal forms a corkscrew and is thought to be important for secretion of the protein through the bacterial cell wall. This domain contains the calcium ion binding domain PF00353.
Internal database links
|Similarity to PfamA using HHSearch:||HemolysinCabind|
External database links
This tab holds annotation information from the InterPro database.
InterPro entry IPR013858
In the MEROPS database peptidases and peptidase homologues are grouped into clans and families. Clans are groups of families for which there is evidence of common ancestry based on a common structural fold:
- Each clan is identified with two letters, the first representing the catalytic type of the families included in the clan (with the letter 'P' being used for a clan containing families of more than one of the catalytic types serine, threonine and cysteine). Some families cannot yet be assigned to clans, and when a formal assignment is required, such a family is described as belonging to clan A-, C-, M-, N-, S-, T- or U-, according to the catalytic type. Some clans are divided into subclans because there is evidence of a very ancient divergence within the clan, for example MA(E), the gluzincins, and MA(M), the metzincins.
- Peptidase families are grouped by their catalytic type, the first character representing the catalytic type: A, aspartic; C, cysteine; G, glutamic acid; M, metallo; N, asparagine; S, serine; T, threonine; and U, unknown. The serine, threonine and cysteine peptidases utilise the amino acid as a nucleophile and form an acyl intermediate - these peptidases can also readily act as transferases. In the case of aspartic, glutamic and metallopeptidases, the nucleophile is an activated water molecule. In the case of the asparagine endopeptidases, the nucleophile is asparagine and all are self-processing endopeptidases.
In many instances the structural protein fold that characterises the clan or family may have lost its catalytic activity, yet retain its function in protein recognition and binding.
Metalloproteases are the most diverse of the four main types of protease, with more than 50 families identified to date. In these enzymes, a divalent cation, usually zinc, activates the water molecule. The metal ion is held in place by amino acid ligands, usually three in number. The known metal ligands are His, Glu, Asp or Lys and at least one other residue is required for catalysis, which may play an electrophillic role. Of the known metalloproteases, around half contain an HEXXH motif, which has been shown in crystallographic studies to form part of the metal-binding site [PUBMED:7674922]. The HEXXH motif is relatively common, but can be more stringently defined for metalloproteases as 'abXHEbbHbc', where 'a' is most often valine or threonine and forms part of the S1' subsite in thermolysin and neprilysin, 'b' is an uncharged residue, and 'c' a hydrophobic residue. Proline is never found in this site, possibly because it would break the helical structure adopted by this motif in metalloproteases [PUBMED:7674922].
Proteins in this entry are metalloendopeptidases belong to the MEROPS peptidase family M10 (subfamily M10B, clan MA). They include serralysin, epralysin, mirabilysin, aeruginolysin and other related peptidases. The peptidase unit is found at the N terminus while in this entry it is found at the C terminus and forms a corkscrew. It is thought to be important for secretion of the protein through the bacterial cell wall. Proteins in this entry contain a calcium ion binding domain.
The mapping between Pfam and Gene Ontology is provided by InterPro. If you use this data please cite InterPro.
|Cellular component||extracellular space (GO:0005615)|
|Molecular function||metalloendopeptidase activity (GO:0004222)|
|calcium ion binding (GO:0005509)|
|zinc ion binding (GO:0008270)|
- the number of sequences which exhibit this architecture
a textual description of the architecture, e.g. Gla, EGF x 2, Trypsin.
This example describes an architecture with one
Gladomain, followed by two consecutive
EGFdomains, and finally a single
- the UniProt description of the protein sequence
- the number of residues in the sequence
- the Pfam graphic itself.
Loading domain graphics...
We make a range of alignments for each Pfam-A family:
- the curated alignment from which the HMM for the family is built
- the alignment generated by searching the sequence database using the HMM
- Representative Proteomes (RPs) at 15%, 35%, 55% and 75% co-membership thresholds
- alignment generated by searching the NCBI sequence database using the family HMM
- alignment generated by searching the metagenomics sequence database using the family HMM
You can see the alignments as HTML or in three different sequence viewers:
- Pfam viewer
- an HTML-based viewer that uses DAS to retrieve alignment fragments on request
1Cannot generate PP/Heatmap alignments for seeds; no PP data available
Key: available, not generated, — not available.
Format an alignment
If you find these logos useful in your own work, please consider citing the following article:
Note: You can also download the data file for the tree.
Curation and family details
|Seed source:||Rawlings ND|
|Author:||Mistry J, Rawlings ND|
|Number in seed:||15|
|Number in full:||432|
|Average length of the domain:||201.30 aa|
|Average identity of full alignment:||36 %|
|Average coverage of the sequence by the domain:||37.88 %|
|HMM build commands:||
build method: hmmbuild -o /dev/null --hand HMM SEED
search method: hmmsearch -Z 23193494 -E 1000 --cpu 4 HMM pfamseq
|Family (HMM) version:||6|
|Download:||download the raw HMM for this family|
Weight segments by...
Change the size of the sunburst
selected sequences to HMM
a FASTA-format file
- 0 sequences
- 0 species
How the sunburst is generated
Colouring and labels
Anomalies in the taxonomy tree
Missing taxonomic levels
Unmapped species names
Too many species/sequences
The tree shows the occurrence of this domain across different species. More...
You can use the tree controls to manipulate how the interactive tree is displayed:
- show/hide the summary boxes
- highlight species that are represented in the seed alignment
- expand/collapse the tree or expand it to a given depth
- select a sub-tree or a set of species within the tree and view them graphically or as an alignment
- save a plain text representation of the tree
There are 3 interactions for this family. More...
We determine these interactions using iPfam, which considers the interactions between residues in three-dimensional protein structures and maps those interactions back to Pfam families. You can find more information about the iPfam algorithm in the journal article that accompanies the website.
For those sequences which have a structure in the Protein DataBank, we use the mapping between UniProt, PDB and Pfam coordinate systems from the PDBe group, to allow us to map Pfam domains onto UniProt sequences and three-dimensional protein structures. The table below shows the structures on which the Peptidase_M10_C domain has been found. There are 24 instances of this domain found in the PDB. Note that there may be multiple copies of the domain in a single PDB structure, since many structures contain multiple copies of the same protein seqence.
Loading structure mapping...