Summary: MutS domain V
Pfam includes annotations and additional family information from a range of different sources. These sources can be accessed via the tabs below.
The Pfam group coordinates the annotation of Pfam families in Wikipedia, but we have not yet assigned a Wikipedia article to this family. If you think that a particular Wikipedia article provides good annotation, please let us know.
This tab holds the annotation information that is stored in the Pfam database. As we move to using Wikipedia as our main source of annotation, the contents of this tab will be gradually replaced by the Wikipedia tab.
MutS domain V Provide feedback
This domain is found in proteins of the MutS family (DNA mismatch repair proteins) and is found associated with PF01624 PF05188 PF05192 and PF05190. The mutS family of proteins is named after the Salmonella typhimurium MutS protein involved in mismatch repair; other members of the family included the eukaryotic MSH 1,2,3, 4,5 and 6 proteins. These have various roles in DNA repair and recombination. Human MSH has been implicated in non-polyposis colorectal carcinoma (HNPCC) and is a mismatch binding protein . The aligned region corresponds with domain V of Thermus aquaticus MutS as characterised in  which contains a Walker A motif, and is structurally similar to the ATPase domain of ABC transporters.
Tachiki H, Kato R, Masui R, Hasegawa K, Itakura H, Fukuyama K, Kuramitsu S; , Nucleic Acids Res 1998;26:4153-4159.: Domain organization and functional analysis of Thermus thermophilus MutS protein [published erratum appears in Nucleic Acids Res 1998 Oct 15;26(20):following 4789] PUBMED:9722634 EPMC:9722634
Internal database links
|SCOOP:||AAA AAA_14 AAA_23 AAA_27 AAA_29 MutS_III|
|Similarity to PfamA using HHSearch:||AAA ABC_tran RNA_helicase NTPase_1 AAA_21 AAA_22 AAA_23 AAA_28 AAA_29|
External database links
|HOMSTRAD:||MutS_D2 MutS_D3 MutS_N MutS_NC|
This tab holds annotation information from the InterPro database.
InterPro entry IPR000432
Mismatch repair contributes to the overall fidelity of DNA replication and is essential for combating the adverse effects of damage to the genome. It involves the correction of mismatched base pairs that have been missed by the proofreading element of the DNA polymerase complex. The post-replicative Mismatch Repair System (MMRS) of Escherichia coli involves MutS (Mutator S), MutL and MutH proteins, and acts to correct point mutations or small insertion/deletion loops produced during DNA replication [PUBMED:17919654]. MutS and MutL are involved in preventing recombination between partially homologous DNA sequences. The assembly of MMRS is initiated by MutS, which recognises and binds to mispaired nucleotides and allows further action of MutL and MutH to eliminate a portion of newly synthesized DNA strand containing the mispaired base [PUBMED:17599803]. MutS can also collaborate with methyltransferases in the repair of O(6)-methylguanine damage, which would otherwise pair with thymine during replication to create an O(6)mG:T mismatch [PUBMED:17951114]. MutS exists as a dimer, where the two monomers have different conformations and form a heterodimer at the structural level [PUBMED:17426027]. Only one monomer recognises the mismatch specifically and has ADP bound. Non-specific major groove DNA-binding domains from both monomers embrace the DNA in a clamp-like structure. Mismatch binding induces ATP uptake and a conformational change in the MutS protein, resulting in a clamp that translocates on DNA.
MutS is a modular protein with a complex structure [PUBMED:11048711], and is composed of:
- N-terminal mismatch-recognition domain, which is similar in structure to tRNA endonuclease.
- Connector domain, which is similar in structure to Holliday junction resolvase ruvC.
- Core domain, which is composed of two separate subdomains that join together to form a helical bundle; from within the core domain, two helices act as levers that extend towards (but do not touch) the DNA.
- Clamp domain, which is inserted between the two subdomains of the core domain at the top of the lever helices; the clamp domain has a beta-sheet structure.
- ATPase domain (connected to the core domain), which has a classical Walker A motif.
- HTH (helix-turn-helix) domain, which is involved in dimer contacts.
The MutS family of proteins is named after the Salmonella typhimurium MutS protein involved in mismatch repair. Homologues of MutS have been found in many species including eukaryotes (MSH 1, 2, 3, 4, 5, and 6 proteins), archaea and bacteria, and together these proteins have been grouped into the MutS family. Although many of these proteins have similar activities to the E. coli MutS, there is significant diversity of function among the MutS family members. Human MSH has been implicated in non-polyposis colorectal carcinoma (HNPCC) and is a mismatch binding protein [PUBMED:8036718].This diversity is even seen within species, where many species encode multiple MutS homologues with distinct functions [PUBMED:9722651]. Inter-species homologues may have arisen through frequent ancient horizontal gene transfer of MutS (and MutL) from bacteria to archaea and eukaryotes via endosymbiotic ancestors of mitochondria and chloroplasts [PUBMED:17965091].
This entry represents the C-terminal domain found in proteins in the MutS family of DNA mismatch repair proteins. The C-terminal region of MutS is comprised of the ATPase domain and the HTH (helix-turn-helix) domain, the latter being involved in dimer contacts. Yeast MSH3 [PUBMED:8510668], bacterial proteins involved in DNA mismatch repair, and the predicted protein product of the Rep-3 gene of mouse share extensive sequence similarity. Human MSH has been implicated in non-polyposis colorectal carcinoma (HNPCC) and is a mismatch binding protein.
The mapping between Pfam and Gene Ontology is provided by InterPro. If you use this data please cite InterPro.
|Molecular function||ATP binding (GO:0005524)|
|mismatched DNA binding (GO:0030983)|
|Biological process||mismatch repair (GO:0006298)|
Below is a listing of the unique domain organisations or architectures in which this domain is found. More...
The graphic that is shown by default represents the longest sequence with a given architecture. Each row contains the following information:
- 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
- a link to the page in the Pfam site showing information about the sequence that the graphic describes
- the UniProt description of the protein sequence
- the number of residues in the sequence
- the Pfam graphic itself.
Note that you can see the family page for a particular domain by clicking on the graphic. You can also choose to see all sequences which have a given architecture by clicking on the Show link in each row.
Finally, because some families can be found in a very large number of architectures, we load only the first fifty architectures by default. If you want to see more architectures, click the button at the bottom of the page to load the next set.
Loading domain graphics...
AAA family proteins often perform chaperone-like functions that assist in the assembly, operation, or disassembly of protein complexes .
The clan contains the following 229 members:6PF2K AAA AAA-ATPase_like AAA_10 AAA_11 AAA_12 AAA_13 AAA_14 AAA_15 AAA_16 AAA_17 AAA_18 AAA_19 AAA_2 AAA_21 AAA_22 AAA_23 AAA_24 AAA_25 AAA_26 AAA_27 AAA_28 AAA_29 AAA_3 AAA_30 AAA_31 AAA_32 AAA_33 AAA_34 AAA_35 AAA_5 AAA_6 AAA_7 AAA_8 AAA_9 AAA_PrkA ABC_ATPase ABC_tran ABC_tran_Xtn Adeno_IVa2 Adenylsucc_synt ADK AFG1_ATPase AIG1 APS_kinase Arf ArsA_ATPase ATP-synt_ab ATP_bind_1 ATP_bind_2 ATPase ATPase_2 Bac_DnaA BCA_ABC_TP_C Beta-Casp Cas_Csn2 Cas_St_Csn2 CbiA CBP_BcsQ CDC73_C CENP-M CFTR_R CLP1_P CMS1 CoaE CobA_CobO_BtuR CobU cobW CPT CSM2 CTP_synth_N Cytidylate_kin Cytidylate_kin2 DAP3 DBINO DEAD DEAD_2 DLIC DNA_pack_C DNA_pack_N DNA_pol3_delta DNA_pol3_delta2 DnaB_C dNK DUF1611 DUF1726 DUF2075 DUF2326 DUF2478 DUF257 DUF2791 DUF2813 DUF3584 DUF463 DUF815 DUF853 DUF87 DUF927 Dynamin_N Dynein_heavy Elong_Iki1 ELP6 ERCC3_RAD25_C Exonuc_V_gamma FeoB_N Fer4_NifH Flavi_DEAD FTHFS FtsK_SpoIIIE G-alpha Gal-3-0_sulfotr GBP GBP_C GTP_EFTU Gtr1_RagA Guanylate_kin GvpD HDA2-3 Helicase_C Helicase_C_2 Helicase_C_4 Helicase_RecD Herpes_Helicase Herpes_ori_bp Herpes_TK HSA HydF_dimer HydF_tetramer Hydin_ADK IIGP IPPT IPT IstB_IS21 KAP_NTPase KdpD Kinase-PPPase Kinesin KTI12 LAP1C Lon_2 LpxK MCM MeaB MEDS Mg_chelatase Microtub_bd MipZ MMR_HSR1 MMR_HSR1_C MobB MukB MutS_V Myosin_head NACHT NB-ARC NOG1 NTPase_1 NTPase_P4 ORC3_N ParA Parvo_NS1 PAXNEB PduV-EutP PhoH PIF1 Ploopntkinase1 Ploopntkinase2 Ploopntkinase3 Podovirus_Gp16 Polyoma_lg_T_C Pox_A32 PPK2 PPV_E1_C PRK PSY3 Rad17 Rad51 Ras RecA ResIII RHD3 RHSP RNA12 RNA_helicase Roc RsgA_GTPase RuvB_N SbcCD_C SecA_DEAD Septin Sigma54_activ_2 Sigma54_activat SKI SMC_N SNF2_N Spore_IV_A SRP54 SRPRB SulA Sulfotransfer_1 Sulfotransfer_2 Sulfotransfer_3 Sulfotransfer_4 Sulphotransf SWI2_SNF2 T2SSE T4SS-DNA_transf Terminase_1 Terminase_3 Terminase_6 Terminase_GpA Thymidylate_kin TIP49 TK TniB Torsin TraG-D_C tRNA_lig_kinase TrwB_AAD_bind TsaE UvrB UvrD-helicase UvrD_C UvrD_C_2 Viral_helicase1 VirC1 VirE Zeta_toxin Zot
We store a range of different sequence alignments for families. As well as the seed alignment from which the family is built, we provide the full alignment, generated by searching the sequence database (reference proteomes) using the family HMM. We also generate alignments using four representative proteomes (RP) sets, the UniProtKB sequence database, the NCBI sequence database, and our metagenomics sequence database. More...
There are various ways to view or download the sequence alignments that we store. We provide several sequence viewers and a plain-text Stockholm-format file for download.
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 UniProtKB sequence database using the family HMM
- 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:
- a Java applet developed at the University of Dundee. You will need Java installed before running jalview
- an HTML page showing the whole alignment.Please note: full Pfam alignments can be very large. These HTML views are extremely large and often cause problems for browsers. Please use either jalview or the Pfam viewer if you have trouble viewing the HTML version
- an HTML-based representation of the alignment, coloured according to the posterior-probability (PP) values from the HMM. As for the standard HTML view, heatmap alignments can also be very large and slow to render.
You can download (or view in your browser) a text representation of a Pfam alignment in various formats:
You can also change the order in which sequences are listed in the alignment, change how insertions are represented, alter the characters that are used to represent gaps in sequences and, finally, choose whether to download the alignment or to view it in your browser directly.
You may find that large alignments cause problems for the viewers and the reformatting tool, so we also provide all alignments in Stockholm format. You can download either the plain text alignment, or a gzipped version of it.
We make a range of alignments for each Pfam-A family. You can see a description of each above. You can view these alignments in various ways but please note that some types of alignment are never generated while others may not be available for all families, most commonly because the alignments are too large to handle.
1Cannot generate PP/Heatmap alignments for seeds; no PP data available
Key: available, not generated, — not available.
Format an alignment
We make all of our alignments available in Stockholm format. You can download them here as raw, plain text files or as gzip-compressed files.
You can also download a FASTA format file containing the full-length sequences for all sequences in the full alignment.
HMM logos is one way of visualising profile HMMs. Logos provide a quick overview of the properties of an HMM in a graphical form. You can see a more detailed description of HMM logos and find out how you can interpret them here. More...
If you find these logos useful in your own work, please consider citing the following article:
This page displays the phylogenetic tree for this family's seed alignment. We use FastTree to calculate neighbour join trees with a local bootstrap based on 100 resamples (shown next to the tree nodes). FastTree calculates approximately-maximum-likelihood phylogenetic trees from our seed alignment.
Note: You can also download the data file for the tree.
Curation and family details
This section shows the detailed information about the Pfam family. You can see the definitions of many of the terms in this section in the glossary and a fuller explanation of the scoring system that we use in the scores section of the help pages.
|Author:||Finn RD , Studholme DJ|
|Number in seed:||30|
|Number in full:||18408|
|Average length of the domain:||181.20 aa|
|Average identity of full alignment:||35 %|
|Average coverage of the sequence by the domain:||22.19 %|
|HMM build commands:||
build method: hmmbuild -o /dev/null HMM SEED
search method: hmmsearch -Z 45638612 -E 1000 --cpu 4 HMM pfamseq
|Family (HMM) version:||21|
|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
This visualisation provides a simple graphical representation of the distribution of this family across species. You can find the original interactive tree in the More....
This chart is a modified "sunburst" visualisation of the species tree for this family. It shows each node in the tree as a separate arc, arranged radially with the superkingdoms at the centre and the species arrayed around the outermost ring.
How the sunburst is generated
The tree is built by considering the taxonomic lineage of each sequence that has a match to this family. For each node in the resulting tree, we draw an arc in the sunburst. The radius of the arc, its distance from the root node at the centre of the sunburst, shows the taxonomic level ("superkingdom", "kingdom", etc). The length of the arc represents either the number of sequences represented at a given level, or the number of species that are found beneath the node in the tree. The weighting scheme can be changed using the sunburst controls.
In order to reduce the complexity of the representation, we reduce the number of taxonomic levels that we show. We consider only the following eight major taxonomic levels:
Colouring and labels
Segments of the tree are coloured approximately according to their superkingdom. For example, archeal branches are coloured with shades of orange, eukaryotes in shades of purple, etc. The colour assignments are shown under the sunburst controls. Where space allows, the name of the taxonomic level will be written on the arc itself.
As you move your mouse across the sunburst, the current node will be highlighted. In the top section of the controls panel we show a summary of the lineage of the currently highlighed node. If you pause over an arc, a tooltip will be shown, giving the name of the taxonomic level in the title and a summary of the number of sequences and species below that node in the tree.
Anomalies in the taxonomy tree
There are some situations that the sunburst tree cannot easily handle and for which we have work-arounds in place.
Missing taxonomic levels
Some species in the taxonomic tree may not have one or more of the main eight levels that we display. For example, Bos taurus is not assigned an order in the NCBI taxonomic tree. In such cases we mark the omitted level with, for example, "No order", in both the tooltip and the lineage summary.
Unmapped species names
The tree is built by looking at each sequence in the full alignment for the family. We take the name of the species given by UniProt and try to map that to the full taxonomic tree from NCBI. In some cases, the name chosen by UniProt does not map to any node in the NCBI tree, perhaps because the chosen name is listed as a synonym or a misspelling in the NCBI taxonomy.
So that these nodes are not simply omitted from the sunburst tree, we group them together in a separate branch (or segment of the sunburst tree). Since we cannot determine the lineage for these unmapped species, we show all levels between the superkingdom and the species as "uncategorised".
Since we reduce the species tree to only the eight main taxonomic levels, sequences that are mapped to the sub-species level in the tree would not normally be shown. Rather than leave out these species, we map them instead to their parent species. So, for example, for sequences belonging to one of the Vibrio cholerae sub-species in the NCBI taxonomy, we show them instead as belonging to the species Vibrio cholerae.
Too many species/sequences
For large species trees, you may see blank regions in the outer layers of the sunburst. These occur when there are large numbers of arcs to be drawn in a small space. If an arc is less than approximately one pixel wide, it will not be drawn and the space will be left blank. You may still be able to get some information about the species in that region by moving your mouse across the area, but since each arc will be very small, it will be difficult to accurately locate a particular species.
The tree shows the occurrence of this domain across different species. More...
We show the species tree in one of two ways. For smaller trees we try to show an interactive representation, which allows you to select specific nodes in the tree and view them as an alignment or as a set of Pfam domain graphics.
Unfortunately we have found that there are problems viewing the interactive tree when the it becomes larger than a certain limit. Furthermore, we have found that Internet Explorer can become unresponsive when viewing some trees, regardless of their size. We therefore show a text representation of the species tree when the size is above a certain limit or if you are using Internet Explorer to view the site.
If you are using IE you can still load the interactive tree by clicking the "Generate interactive tree" button, but please be aware of the potential problems that the interactive species tree can cause.
For all of the domain matches in a full alignment, we count the number that are found on all sequences in the alignment. This total is shown in the purple box.
We also count the number of unique sequences on which each domain is found, which is shown in green. Note that a domain may appear multiple times on the same sequence, leading to the difference between these two numbers.
Finally, we group sequences from the same organism according to the NCBI code that is assigned by UniProt, allowing us to count the number of distinct sequences on which the domain is found. This value is shown in the pink boxes.
We use the NCBI species tree to group organisms according to their taxonomy and this forms the structure of the displayed tree. Note that in some cases the trees are too large (have too many nodes) to allow us to build an interactive tree, but in most cases you can still view the tree in a plain text, non-interactive representation. Those species which are represented in the seed alignment for this domain are highlighted.
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
Please note: for large trees this can take some time. While the tree is loading, you can safely switch away from this tab but if you browse away from the family page entirely, the tree will not be loaded.
There are 4 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 MutS_V domain has been found. There are 71 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 sequence.
Loading structure mapping...