kontragentpro-mcp
Related Servers
Alternatives to kontragentpro-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform counterparty due-diligence by Russian INN, aggregating open registries (EGRUL, FSSP, courts, bankruptcies, finances) into a risk traffic light with source-backed signals, sanctions screening, affiliate graph, and fragmentation indicators via read-only MCP tools.8Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to validate Russian business requisites (INN, OGRN, bank accounts) via checksums, extract them from text, and retrieve counterparty details by INN using DaData.5MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve data about Russian companies, entrepreneurs, and individuals via the Checko.ru API, including financial reports, legal cases, and bankruptcy information.1213MIT
- AlicenseAqualityAmaintenanceRussian business data with no API key: company check by INN/OGRN in FNS EGRUL/EGRIP, Bank of Russia exchange rates and key rate, late-payment interest, production calendar with business-day math, and bank details by BIK.610MIT
- AlicenseNot gradedqualityCmaintenanceGives Claude direct, keyless access to Polish public registries: it validates NIP checksums, checks a company's VAT status and bank account against the VAT whitelist, pulls KRS court-registry extracts, and fetches the correct NBP exchange rate for an invoice date. Runs locally as an MCP server for Claude Desktop, Claude Code, Cursor and other MCP clients.MIT
- AlicenseAqualityAmaintenanceMCP server for verifying Russian counterparties (legal entities and individual entrepreneurs) via public Federal Tax Service data: EGRUL/EGRIP, bankruptcy registry (EFRSB), Transparent Business, bailiff service (FSSP), and arbitration courts (KAD).8161 PyPI15MIT
TDQS
Scored across 5 tools
Every tool targets a distinct purpose: searching, retrieving a company summary, detailed financials, event timeline, or checking account status. Overlap between get_company and get_company_financials is minimal and clearly separated by summary vs. multi-year dynamics.
All tools follow a consistent verb_noun snake_case pattern: search_companies, check_account, get_company, get_company_financials, get_company_timeline. The shared get_company_ prefix for company-specific detail views makes the API predictable.
Five tools is well-scoped for a business intelligence API: search, general company card, financials, event timeline, and account management. No tool is redundant or missing at this abstraction level.
The toolset covers the core lifecycle of company investigation: finding candidates via search, retrieving a full company card, diving into financial history, exploring event timelines, and managing API access. No obvious dead ends or required missing operations.