frankiefin
Related Servers
Alternatives to frankiefin
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables identity verification from any MCP client by providing tools to create verification sessions, generate capture links, screen against sanctions and PEP lists, read results, and manage the review queue.22 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables ID document validation using IDmission's identity verification API, including ID validation, face matching, and liveness checks.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that compares Brazilian identity data (CPF, name, birth, address) and returns a similarity score against official records, enabling identity verification through natural language.MIT

eKYC Suite MCP Serverofficial
AlicenseAqualityBmaintenanceProvides 8 financial-grade KYC identity verification tools for AI agents, including face comparison, liveness detection, document OCR, and risk media labeling.867 npm4MIT- FlicenseNot gradedqualityDmaintenanceEnables KYC (Know Your Customer) verification through API integration, supporting PAN card verification, PAN-Aadhaar link checking, and identity validation with advanced caching and rate limiting.-
- AlicenseAqualityAmaintenanceProvides AI agents with compliance screening (OFAC sanctions, risk scoring, Know-Your-Agent) plus disposable email and SMS verification for OTPs, accessible via MCP tools, HTTP API, and CLI.102MIT
TDQS
Scored across 46 tools
Many tools are clearly separated by Create/Update/Delete/Query prefixes, but the sheer number of Create/Update variants for documents and IDs, along with overlapping terms like 'Check', 'Search', and 'Query', creates boundary ambiguity. Descriptions help in most cases, but an agent could easily pick the wrong variant when dealing with entities vs organisations or document details vs full document scans.
Most tools follow a PascalCase Verb+Object pattern such as CreateEntity or DeleteDocument, which is readable. However, tools like InternationalBusinessProfile, BusinessOwnershipQuery, EntityMonitoring, StatusCheck, and notifyResult break the pattern with noun-first names or inconsistent casing and word order, making the naming mixed rather than uniform.
At 46 tools, the surface is well beyond the typical well-scoped range of 3-15 and even beyond the 25+ threshold for 'too many'. The domain is broad, but many tools are variations of the same create/update operation and could likely be consolidated via parameters or narrower tool groupings.
The tool set covers full CRUD-style lifecycles for both documents and entities, plus state management, checks, IDV, reporting, and service status. Some gaps exist, such as no dedicated list/report operations and no obvious way to update document check results, but most workflows can be completed through Query/Search and Update variants.