# Kleros Scout - Metamask Snaps
Started in 2019 with the Tokens registry, [Kleros](https://kleros.io/?ref=blog.kleros.io) has been a pioneer in curating decentralised registries, especially around security metadata.
We now introduce Kleros Scout, a [Metamask Snap](https://metamask.io/snaps/) designed to enable safe contract interactions by providing insights, curated and secured by the community!
The Kleros Scout plugin in action.
The Kleros Scout Snap utilises information from the following Kleros Curate registries:
* [**Address Tags registry**](https://curate.kleros.io/tcr/100/0x66260C69d03837016d88c9877e61e08Ef74C59F2) of verified project and name tag of contracts
* [**Contract-Domain Name registry**](https://curate.kleros.io/tcr/100/0x957A53A994860BE4750810131d9c876b2f52d6E1) of verified contract-to-domain name pairings
* [**Tokens registry**](https://curate.kleros.io/tcr/100/0xeE1502e29795Ef6C2D60F8D7120596abE3baD990) of ERC-20 tokens
Install the Kleros Scout Plugin on the [**official Metamask Snaps Directory**](https://snaps.metamask.io/snap/npm/kleros/scout-snap/) today!
## 1. How can I install the Kleros Scout Snap?
Step 1: Install [Metamask Flask](https://metamask.io/flask/)
Step 2: Head to
Step 3: Search for ***@kleros/scout-snap***
Step 4: Install ***@kleros/scout-snap**!* It’s that easy :)
## 2. How to use the Snap's features?
Once you install the Kleros Scout Snap, with every txn/contract interaction, you will see a tab which provides you with insights around the same. Upon installation, If you see this, you are already using community curated contract insights for secure dapp interaction - the most important feature of the Kleros Scout Snap.
## 3. What does the Kleros Scout Snap do?
This Snap pulls contract metadata from Kleros's decentralized token curated registries (TCRs) to provide insights around the contract you are interacting with.
## 4. What does the Snap not do?
The Kleros Scout snap **does not**:
→ Endorse any contract interaction
→ Do any centralised whitelisting - all data is community curated. To know more about the same, go to ‘How is the registry data curated?’.
*→* Guarantee 100% accuracy or take on any liability caused as a result of an insight.
## 5. What decentralised registries by Kleros are used for this Snap?
The data used in this Snap is pulled from the following decentralised registries on Kleros Curate:
* [Contract-Domain Name Registry](https://curate.kleros.io/tcr/100/0x957a53a994860be4750810131d9c876b2f52d6e1)
* [Address Tags Registry](https://curate.kleros.io/tcr/100/0x66260c69d03837016d88c9877e61e08ef74c59f2)
* [Tokens Registry](https://curate.kleros.io/tcr/100/0x70533554fe5c17caf77fe530f77eab933b92af60)
[You can read more about these registries and their capabilities here.](https://blog.kleros.io/migrating-kleros-registries-to-v2/)
## 6. How can I reach out for Snap support?
You can either drop in a message on our [TG support group here](http://t.me/KlerosCurate) or [email us here](mailto:support@kleros.io)! We generally get back within 24-48hrs.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.kleros.io/products/curate/kleros-scout/kleros-scout-metamask-snaps.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.