Aml Watcher Mcp Server
Description
AML Watcher MCP Server gives AI agents direct, real-time access to AML Watcher's proprietary sanctions, watchlist, and PEP databases. Connect your agentic workflows to 215+ sanctions regimes, 2.6M+ PEP profiles, and coverage across 235+ countries, no complex integrations…
About
AML Watcher MCP Server gives AI agents direct, real-time access to AML Watcher's proprietary sanctions, watchlist, and PEP databases. Connect your agentic workflows to 215+ sanctions regimes, 2.6M+ PEP profiles, and coverage across 235+ countries, no complex integrations required.
Details
- Author
- Tech-AML
- Downloads
- 364
- Categories
- Other, Database
Jump to
- Configurable search via environment variables
- Docker and NPX deployment options
- Filter reports by countries, categories, and match score
- Search within aliases and Relatives & Close Associates (RCA)
- Returns a maximum number of results per page
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Aml Watcher Mcp ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Configure the server in claude_desktop_config.json using either Docker or NPX. Provide an API key obtained from the AML Watcher Developer Portal and optionally set environment variables like PER_PAGE, MATCH_SCORE, and CATEGORIES. After integration, the user must provide a username.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"aml watcher mcp server": {
"aml": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_KEY",
"-e",
"PER_PAGE",
"-e",
"MATCH_SCORE",
"-e",
"CATEGORIES",
"-e",
"ALIAS_SEARCH",
"-e",
"RCA_SEARCH",
"-e",
"COUNTRIES",
"techamlw/aml-watcher"
],
"env": {
"API_KEY": "api_key",
"PER_PAGE": "1"
}
}
}
}
}McpServers
{
"aml": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"API_KEY",
"-e",
"PER_PAGE",
"-e",
"MATCH_SCORE",
"-e",
"CATEGORIES",
"-e",
"ALIAS_SEARCH",
"-e",
"RCA_SEARCH",
"-e",
"COUNTRIES",
"techamlw/aml-watcher"
],
"env": {
"API_KEY": "api_key",
"PER_PAGE": "1"
}
}
}<!-- ## 
-->
This README provides detailed documentation for the AML Watcher MCP server configuration, focusing on the environment arguments used in the claude_desktop_config.json file. It explains each argument, how to set or modify its values, and how to add new arguments if needed.
Overview
The MCP server is configured to run a Docker container for AML (Anti-Money Laundering) screening. The configuration is defined in the
claude_desktop_config.json file, which specifies the Docker command, arguments, and environment variables. The environment variables (env) control the behavior of the AML screening process, such as search parameters, filtering options, and monitoring settings.⚙️ Configuration
📝 Sign Up
- If you already have an account, Visit the AML Watcher Developer Portal.
- If you don’t have an account, please click here to contact us.
🔑 How to Generate Your API Key
- Navigate to the AML Watcher Developer Portal.
- Click on “API Key” and copy it.
🖥️ Usage with Claude Desktop
Add this to your
claude_desktop_config.json:🐳 Docker
``
json
{
"mcpServers": {
"aml": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "API_KEY",
"-e", "PER_PAGE",
"-e", "MATCH_SCORE",
"-e", "CATEGORIES",
"-e", "ALIAS_SEARCH",
"-e", "RCA_SEARCH",
"-e", "COUNTRIES",
"techamlw/aml-watcher"
],
"env": {
"API_KEY": "api_key",
"PER_PAGE": "1"
}
}
}
}
`
Add this to your :
NPX
`json
{
"mcpServers": {
"aml-watcher": {
"command": "npx",
"args": [
"-y",
"@amlwatcher-modelcontextprotocol/aml_watcher_mcp"
],
"env": {
"API_KEY": "your_api_key",
"PER_PAGE": "5"
}
}
}
}
`
- After this integration, the user has to provide a username.
🌐 Environment Arguments
Below is a detailed explanation of each environment argument specified in the section of the claude_desktop_config.json. Each argument includes its purpose, type, default value, constraints, and instructions for setting or modifying its value.
| Argument | Type | Required | Default Value | Description |
|----------------|---------|----------|----------------|----------------------------------------------------------------------------|
| API_KEY | String | Yes | N/A | The API key for authentication. |
| COUNTRIES | Array | No | N/A | Array of countries to filter reports. Note: ISO 3166-1 alpha-2 country codes are supported. Example: [\"CA\", \"IN\"]. <a href="https://doc.amlwatcher.com/docs/Technical-appendicies/supported-countries/" target="_blank" rel="noopener noreferrer">See supported countries</a> |
| PER_PAGE | Integer | No | 1 | The maximum number of results to return. |
| MATCH_SCORE | Integer | No | 80 | Match accuracy level (0–100).|
| CATEGORIES | Array | Yes | N/A | Filters reports by categories (e.g., [\"SIP\", \"PEP Level 1\"]). <a href="https://doc.amlwatcher.com/docs/Technical-appendicies/categories/" target="_blank" rel="noopener noreferrer" >See available categories</a> |
| RCA_SEARCH | Boolean | No | True | Whether to search within Relatives and Close Associates (RCA). |
| ALIAS_SEARCH | Boolean | No | True | Whether to search within aliases. |
You can define custom parameters inside the env section of your configuration file. These parameters are passed to the Docker container as environment variables.
🛠️ How to Add Environment Variables
Each variable listed in the args array using -e must have a matching key in the env section.
If a variable is not defined in the env block, the system may use a default value.
For example, if your args list contains:
`json
"args": [
"-e", "PER_PAGE",
"-e", "MATCH_SCORE"
]
`
Then your env should include:
json
"env": {
"PER_PAGE": "1",
"MATCH_SCORE": "80"
}
``💡Tip : If you want to manually set the value of a variable, make sure to use the exact same name as listed in the args section. Variable names must match exactly, otherwise the Docker container won't receive the value correctly.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
