KYA-BRASIL
Related Servers
Alternatives to KYA-BRASIL
FlicenseNot gradedqualityDmaintenanceA ready-to-deploy MCP server with in-process agent verification via KYA-OS Checkpoint, enabling secure tool access for verified agents.1-
Related Servers
- AlicenseNot gradedqualityDmaintenanceKYA (Know Your Agent) identity, trust scoring, and insurance protocol for autonomous AI agents. Issues verifiable credentials, computes real-time trust scores, and provides agent liability coverage on Base L2.MIT
- AlicenseBqualityBmaintenanceAutonomous M2M compliance and trust APIs for AI agents (KYB, OFAC, VAT, Sanctions checking).5MIT
- FlicenseAqualityDmaintenanceAgentic KYC/AML compliance server with tools for sanctions screening, identity verification, and risk assessment, where AI orchestrates discretionary checks within deterministic compliance guardrails.6-

Brazilayer MCP Serverofficial
AlicenseBqualityBmaintenanceEnables AI agents to access Brazilian public data including company registry and official sanction lists via MCP tools, with pay-per-call via USDC.47MIT- AlicenseNot gradedqualityCmaintenanceW3C DID resolution and agent KYC for autonomous agent counterparties, enabling identity verification and trust scoring.MIT
- AlicenseBqualityCmaintenanceConnects AI agents to Brazilian tax compliance data (CNPJ, CPF, NFe, SPED, eSocial) and provides tools for due diligence, risk scoring, and tax regime comparison.44165 PyPI319MIT
TDQS
Scored across 10 tools
Several tool pairs overlap heavily (kya_verify vs kya_verify_paid, kya_check_action vs kya_check_mandate, kya_validate_mandate vs kya_check_mandate), but the descriptions explicitly cross-reference each other and state when to use the free/offline vs live/paid variant, so boundaries are largely recoverable. An agent must read carefully to pick the right variant, which keeps this from a 5.
All tools share a consistent kya_ snake_case prefix followed by a verb_noun form (validate_mandate, check_action, verify_delegation). Minor deviations exist: kya_revocations and kya_about are noun-only with no verb, and the verify family uses inconsistent suffixes (verify, verify_paid, verify_credential_offline).
Ten tools is well within the ideal 3-15 range and each covers a distinct verification/validation concern for the KYA credential lifecycle. No tool feels gratuitous given the breadth of the domain.
The surface covers the full verifier lifecycle: pre-registration mandate validation, signing link, offline and live credential verification, action/mandate checks, revocation polling, delegation chains, and documentation. Only minor gaps, such as issuance itself being external, keep it short of perfect coverage.