newdb
OfficialRelated Servers
Alternatives to newdb
No user-submitted related servers found.
Related Servers
- 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).871 PyPI14MIT
- 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.582 PyPI1Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for checking Russian FSSP (Federal Bailiff Service) debts, enabling AI agents to look up enforcement proceedings for individuals and legal entities through MCP clients like Cursor and Claude Desktop.542 PyPIMIT
- FlicenseNot gradedqualityDmaintenanceAML Watcher MCP Server gives AI agents direct, real-time access to AML Watcher's proprietary sanctions, watchlist, and PEP databases. Connect your agentic workflows to 215+ sanctions regimes, 2.6M+ PEP profiles, and coverage across 235+ countries, no complex integrations required.-
- AlicenseAqualityBmaintenanceLook up Russian companies by INN (tax ID) from Claude Desktop, Cursor or any MCP client: full company card, multi-year financials from official tax filings, bankruptcy and state-inspection history, trademarks and sanctions lists. Works without an API key — the anonymous free tier is enabled by default.5MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to verify Korean ground-truth data through MCP and REST, including business registration, addresses, corporations, apartment trade prices, and statutes, metered with prepaid credits.-
TDQS
Scored across 8 tools
Most tools target distinct registries: bankruptcy, passport, FSSP, EGRUL, and FNS block checking are clearly scoped. The two complex_check tools intentionally overlap these simple checks, but their names and descriptions make the aggregation purpose obvious, so an agent should rarely select the wrong one.
All tools follow a consistent `newdb_<verb>_<target>` pattern, using `check_` for registry lookups and `get_` only for the plainly different balance operation. Prefixes and underscore separators are uniform, making the tool names predictable and easy to navigate.
Eight tools is a well-scoped set for a registry-checking server: enough specific checks to cover major resources without overwhelming an agent. Each tool earns its place, especially the two aggregate checks that reduce the need to invoke many simple checks manually.
The set covers the core domain well: person checks, legal entity checks, debt/bankruptcy/account-block checks, and an aggregate version for each side. It is missing some standalone variants such as a direct court-case-only check or simple INN lookup, but those are bundled into the complex checks, so the main workflows are still supported.