frankiefin
# @ktmcp/frankiefin
MCP server for Frankie Financial API
## Installation
```bash
npm install -g @ktmcp/frankiefin
```
## Usage
Add to your MCP settings:
```json
{
"mcpServers": {
"frankiefin": {
"command": "mcp-frankiefin"
}
}
}
```
## Description
------
This API allows developers to integrate the Frankie Financial Compliance Utility into their applications. The API allows:
- Checking name, address, date of birth against national databases
## Category
security
---
## Support KTMCP
If you find this CLI useful, we'd greatly appreciate your support! Share your experience on:
- Reddit
- Twitter/X
- Hacker News
**Incentive:** Users who can demonstrate that their support/advocacy helped advance KTMCP will have their feature requests and issues prioritized.
Just be mindful - these are real accounts and real communities. Authentic mentions and genuine recommendations go a long way!
## Support This Project
If you find this CLI useful, we'd appreciate support across Reddit, Twitter, Hacker News, or Moltbook. Please be mindful - these are real community accounts. Contributors who can demonstrate their support helped advance KTMCP will have their PRs and feature requests prioritized.
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.