KYC Compliance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| screen_sanctionsA | Screen one or more individual or entity names against the live OFAC SDN sanctions list. Call this for every applicant, every beneficial owner, and every company name. A potential match must be treated as disqualifying (FAIL) pending human review. |
| assess_country_riskA | Assess AML/sanctions country risk for a given country (name or ISO-2 code), returning a 0-10 risk score and band. Call for the applicant's country and for any beneficial owner whose country differs. Score >= 7 should drive ESCALATE. |
| lookup_businessA | Look up a business entity in the SEC EDGAR registry to verify it is a real, SEC-registered filer. Call for any business applicant. Note: only public/SEC-registered companies appear — a no-match is expected for small private LLCs and is NOT itself disqualifying, but an applicant claiming to be a public company with no EDGAR match is a red flag worth ESCALATE. |
| assess_industry_riskA | Classify a business industry for AML risk. Returns one of PROHIBITED (hard gate — decision must be FAIL), STATE_CONDITIONAL (e.g. cannabis — legality depends on state, drive ESCALATE), ELEVATED (allowed with enhanced due diligence), or STANDARD. Call for every business applicant. Pass the state so cannabis can be resolved correctly. |
| screen_pepA | Screen names for Politically Exposed Person (PEP) status. NOTE: this is an integration point — credible PEP data is licensed (OpenSanctions key/license, World-Check, Dow Jones). It returns a defined-but-not-live status, NOT a clean result. A returned status of INTEGRATION_POINT means PEP screening must be completed manually as an enhanced-due-diligence step; do not treat it as 'no PEP found'. |
| verify_identityA | Validate a personal applicant's identity documents structurally: SSN format/range (SSA rules), driver's-license format for the claimed state, and address presence. Returns VALID_FORMAT / INVALID_FORMAT / SUSPICIOUS / INSUFFICIENT_DATA. NOTE: this is structural validation only — it does NOT confirm the identifiers belong to the person (authoritative SSA/DMV match is a gated integration point). INVALID_FORMAT is a red flag. |
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 targets a distinct aspect of KYC compliance: country risk, industry risk, business entity lookup, PEP screening, sanctions screening, and identity verification. There is no overlap; each has a clear, separate purpose.
All tool names follow a consistent verb_noun pattern (e.g., assess_country_risk, screen_pep, verify_identity). The naming is uniform and predictable, aiding agent understanding.
Six tools is an ideal number for a KYC compliance server. It covers essential risk assessment, entity verification, and screening functions without being excessive or insufficient.
The set covers core KYC operations, but lacks tools for automated PEP resolution (noted as integration point), document upload verification, or ongoing monitoring. Minor gaps exist but do not severely hinder basic workflows.