Skip to main content
Glama
Siemssen-Consulting-GmbH

mcp-easycompliance

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EC_API_KEYYesAPI key provided by easycompliance customer service.
EC_PEP_URLNoPEP API endpoint. Default: https://www.easycompliance.de/pep.apihttps://www.easycompliance.de/pep.api
EC_SANCTIONS_URLNoSanctions list API endpoint. Default: https://www.easycompliance.de/easy.apihttps://www.easycompliance.de/easy.api

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Siemssen-Consulting-GmbH/mcp-easycompliance'

If you have feedback or need assistance with the MCP directory API, please join our Discord server