Bindler MCP
OfficialRelated Servers
Alternatives to Bindler MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides GCC regulatory intelligence including ZATCA e-invoicing, Arabic NLP, UAE Corporate Tax, and compliance tools for AI agents via the Model Context Protocol.44 npmMIT
- AlicenseBqualityDmaintenanceAI workbench for financial contract analysis, risk analytics (VaR/CVaR, RWA Basel III), regulatory compliance (EMIR, REMIT, MiFID II, CBAM, EUDR) and counterparty due diligence (KYB/UBO, OFAC, IMO). Zero Retention. 8 MCP tools.815 npmMIT
- AlicenseAqualityDmaintenanceEU AI Act · APRA · NIST AI RMF · ISO 42001 · AU AI Safety — grounded compliance citations for any MCP client.654 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for EU AI Act compliance analysis — classify any AI system or workflow against Regulation (EU) 2024/1689, updated with AI Omnibus 2026.MIT
- FlicenseNot gradedqualityBmaintenanceEnables retrieval-augmented question answering over EU AI Act and NIS-2 legal texts via MCP tools, with hybrid search and verified article-level citations.-
- AlicenseAqualityDmaintenanceMCP server for EU AI Act compliance, providing risk classification of AI features and Article 50 transparency notices.226 PyPI1Apache 2.0
TDQS
Scored across 4 tools
Each tool maps to a distinct regulation and jurisdiction (UAE corporate tax, EU AI Act, CBAM, CSRD), so there is no realistic overlap or risk of misselection. Descriptions even state explicitly when to prefer each tool over estimation.
All names are snake_case and prefixed by the regulation/subject area (uae_, eu_ai_act_, cbam_, csrd_), which is predictable. The trailing token varies in kind—noun (tax, cost, scope) versus verb (classify)—a minor inconsistency rather than a real problem.
Four tools is well within the sensible 3-15 range, and each one is a substantial, self-contained statutory computation with no filler tools. The surface is tightly scoped to a regulatory-calculation purpose.
Each tool covers its full computation lifecycle (inputs, verdict, article-level breakdown, dates, fines), so no single regulation is a dead end. Minor gaps remain: no cross-regulation discovery tool (e.g. 'which of these apply to my company') and no scenario comparison or output-format options outside CBAM's built-in year sweep.