AgentEconomy Compliance API
Paid KYC, AML, and regulatory risk assessment over MCP via x402 USDC micropayments on Base.
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"compliance-api": {
"url": "https://api.netbrainis.co.za/mcp"
}
}
}Puntos de conexión remotos
https://api.netbrainis.co.za/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (4)
🔴aml_screen(amount, currency, entity_name, transaction_id, wallet_address)
Screen an entity against Anti-Money Laundering (AML) watchlists including OFAC SDN and UN sanctions. Returns risk level, risk score, recommendation (approve/review/reject), and sanctions match details. Uses Jaro-Winkler fuzzy name matching for accurate detection. Cost: $0.05 USDC per screening. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.
Esquema de entrada
{
"type": "object",
"properties": {
"amount": {
"description": "Transaction amount",
"type": "string"
},
"currency": {
"description": "Currency code (e.g. USDC, ETH, BTC)",
"type": "string"
},
"entity_name": {
"description": "Full legal name of the person or entity to screen",
"type": "string"
},
"transaction_id": {
"description": "Transaction identifier for audit trail",
"type": "string"
},
"wallet_address": {
"description": "Blockchain wallet address to check",
"type": "string"
}
},
"required": [
"entity_name"
]
}🔴kyc_check(country, entity_id, entity_name, wallet_address)
Run a KYC (Know Your Customer) identity verification check against OFAC and UN sanctions lists. Returns verification status, risk score (0-100), and sanctions/PEP match results. Powered by real government sanctions data (OFAC SDN + UN Security Council). Cost: $0.01 USDC per check. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.
Esquema de entrada
{
"type": "object",
"properties": {
"country": {
"description": "ISO 3166-1 alpha-2 country code (e.g. US, GB, ZA, IR)",
"type": "string"
},
"entity_id": {
"description": "National ID, passport number, or company registration number",
"type": "string"
},
"entity_name": {
"description": "Full legal name of the person or entity to verify",
"type": "string"
},
"wallet_address": {
"description": "Blockchain wallet address (e.g. 0x...)",
"type": "string"
}
},
"required": [
"entity_name"
]
}🔴risk_report(entity_name, entity_type, include_transaction_analysis, wallet_address)
Generate a comprehensive regulatory risk assessment report combining KYC verification, AML sanctions screening, and multi-jurisdiction risk analysis. Returns overall risk level, risk score, sanctions results, jurisdiction-specific risk factors, and recommended compliance actions. Cost: $0.10 USDC per report. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.
Esquema de entrada
{
"type": "object",
"properties": {
"entity_name": {
"description": "Full legal name of the person or entity",
"type": "string"
},
"entity_type": {
"description": "Entity type: 'individual' or 'company'",
"type": "string"
},
"include_transaction_analysis": {
"description": "Include on-chain transaction analysis in the report",
"type": "boolean"
},
"wallet_address": {
"description": "Blockchain wallet address",
"type": "string"
}
},
"required": [
"entity_name"
]
}🔴wallet_screen(wallet_address)
Screen a blockchain wallet address for compliance risk. Combines a direct OFAC sanctioned-address check with on-chain exposure analysis across Ethereum and Base — flagging sanctioned counterparties the wallet transacted with and known mixer (e.g. Tornado Cash) exposure. Returns risk level, score (0-100), and recommendation (approve/review/reject). No entity name required. Cost: $0.05 USDC per screening. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.
Esquema de entrada
{
"type": "object",
"properties": {
"wallet_address": {
"description": "EVM wallet address to screen (0x + 40 hex chars)",
"type": "string"
}
},
"required": [
"wallet_address"
]
}Comunidad
Evidencia