AML Watcher MCP Server

Created By
Tech-AMLa year ago
MCP Server for the AML Watcher API, enabling AML screening for individuals, companies, organizations, crypto wallets, vessels, and aircraft across various categories such as Sanctions, PEP Level 1, PEP Level 2, PEP Level 3, PEP Level 4, SIP, SIE, etc.
Overview

What is AML Watcher MCP Server?

AML Watcher MCP Server is a server designed for the AML Watcher API, facilitating Anti-Money Laundering (AML) screening for various entities including individuals, companies, organizations, and more across multiple categories such as Sanctions and Politically Exposed Persons (PEP).

How to use AML Watcher MCP Server?

To use the AML Watcher MCP Server, you need to configure it in a Docker container using the claude_desktop_config.json file, where you will specify the necessary environment variables and arguments for the server to function properly.

Key features of AML Watcher MCP Server?

  • Supports AML screening for a wide range of entities.
  • Configurable via a JSON file for easy setup.
  • Allows filtering by various categories and parameters.

Use cases of AML Watcher MCP Server?

  1. Screening individuals and organizations against sanctions lists.
  2. Monitoring crypto wallets for suspicious activities.
  3. Conducting due diligence for financial institutions.

FAQ from AML Watcher MCP Server?

  • How do I generate my API key?

You can generate your API key by logging into the AML Watcher Developer Portal and navigating to the API Key section.

  • What categories can I filter by?

You can filter by categories such as Sanctions, PEP Level 1 to 4, and more.

  • Is there a limit on the number of results returned?

Yes, you can set the maximum number of results to return using the PER_PAGE environment variable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Tech-AML
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago