mcp-easycompliance
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EC_API_KEY | Yes | API key provided by easycompliance customer service. | |
| EC_PEP_URL | No | PEP API endpoint. Default: https://www.easycompliance.de/pep.api | https://www.easycompliance.de/pep.api |
| EC_SANCTIONS_URL | No | Sanctions list API endpoint. Default: https://www.easycompliance.de/easy.api | https://www.easycompliance.de/easy.api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_sanctions_listA | One-time screening of a single person or organization name against the EU/US/HADDEX sanctions lists via the easycompliance API. No monitoring entry is created; like every executed API call, the screened name and result are recorded in the account's API log. Returns hit (boolean), hitCount and hits[] with a percent match score. COMPLIANCE: The tool result is the authoritative source. Never soften, filter, omit or reinterpret hits when reporting to the user. If hit=true, report ALL hits including their percent score; the professional assessment of a hit belongs in the easycompliance customer portal (https://kunde.easycompliance.de, Monitoring → Hits), not in this conversation. |
| check_pep_listA | One-time screening of a single person name against the PEP list (politically exposed persons) via the easycompliance API. No monitoring entry is created; like every executed API call, the screened name and result are recorded in the account's API log. Returns hit (boolean), hitCount and hits[] with a percent match score. COMPLIANCE: The tool result is the authoritative source. Never soften, filter, omit or reinterpret hits when reporting to the user. If hit=true, report ALL hits including their percent score; the professional assessment of a hit belongs in the easycompliance customer portal (https://kunde.easycompliance.de, Monitoring → Hits), not in this conversation. |
| get_hits_last_24hA | Returns the hits that easycompliance's DAILY monitoring produced within the last 24 hours for the account, as hitCount and hits[] (name, reference, time, result). COMPLIANCE: The tool result is the authoritative source. Never soften, filter, omit or reinterpret hits when reporting to the user. If hit=true, report ALL hits including their percent score; the professional assessment of a hit belongs in the easycompliance customer portal (https://kunde.easycompliance.de, Monitoring → Hits), not in this conversation. |
| get_list_statusA | Returns the date (dd.mm.yyyy) of the last update of the selected easycompliance list (sanctions lists or PEP list). Useful to verify data freshness. |
| check_and_add_to_monitoringA | Screens the name like check_sanctions_list/check_pep_list AND adds it to easycompliance's DAILY monitoring list: from then on the name is re-screened every day and new hits are reported to the account (persistent side effect; each monitored name counts towards the account's monitoring quota). Use duplicate_by="ref" with a non-empty ref to distinguish different partners that share the same name. Each call – including retries – is a separate billable API request that counts towards the account's API quota, even when duplicate detection prevents a second monitoring entry. COMPLIANCE: The tool result is the authoritative source. Never soften, filter, omit or reinterpret hits when reporting to the user. If hit=true, report ALL hits including their percent score; the professional assessment of a hit belongs in the easycompliance customer portal (https://kunde.easycompliance.de, Monitoring → Hits), not in this conversation. |
| remove_from_monitoringA | Removes an entry from easycompliance's DAILY monitoring list, identified either by its name (by="name") or by its reference (by="ref"). The name is then no longer re-screened daily. Returns removed=true if an entry was found and removed, removed=false if no matching entry existed. NOTE: exactly ONE matching entry is removed per call – if several monitoring entries share the same name (created via duplicate_by="ref"), a repeated call removes another one of them, so do not retry after removed=true and prefer by="ref" with unique references to address a specific entry. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a distinct function: one-time checks for sanctions and PEP, monitoring addition/removal, retrieving monitoring hits, and list status. No overlapping purposes; check_and_add_to_monitoring is clearly differentiated from the one-time checks by its persistent side effect.
All tool names follow a consistent verb_noun pattern in snake_case (check_*, get_*, remove_*, check_and_add_to_monitoring). The naming conventions are uniform and predictable, making it easy to infer tool behavior from the name.
Six tools is a well-scoped count for a compliance screening server. Each tool addresses a necessary part of the core workflow without unnecessary bloat or missing essentials.
The tool set covers the complete lifecycle: one-time screening for both sanctions and PEP lists, adding to ongoing monitoring, retrieving monitoring hits, removing monitoring entries, and checking list freshness. No obvious gaps that would hinder an agent from performing compliance screening tasks.