romania-mcp
Related Servers
Alternatives to romania-mcp
- AlicenseAqualityBmaintenanceEnables querying Spain's official company registry (BORME) for company events such as incorporations, director appointments, insolvencies, and capital changes, supporting filters by date, province, and act type.10MIT
- AlicenseAqualityBmaintenanceProvides passive OSINT reconnaissance for domains and IPs using public sources, with tools for WHOIS/RDAP, DNS, subdomain enumeration, Wayback Machine, HTTP headers, Shodan InternetDB, email security, TLS certificates, and ASN lookups, all without requiring API keys.1579 PyPIMIT
Related Servers
- AlicenseAqualityBmaintenanceProvides keyless access to Romanian public economic and cultural data, including exchange rates, company/VAT lookups, open datasets, official statistics, seismic-risk building records, and classified cultural heritage.12MIT
- AlicenseAqualityBmaintenanceRomanian company data for AI agents and developers: 4.2M firms from the ONRC registry, ANAF fiscal status and 18 years of financial statements, as a remote MCP server and REST API. Free key, 25 lookups/day.17MIT

howtoromaniaofficial
AlicenseNot gradedqualityCmaintenanceRemote MCP server that enables AI agents to query Romanian company, financial, court, KYB risk, e-Factura, and legislation data. It also supports validation and generation of e-Factura documents and checks of extracted company data against public sources.MIT- AlicenseAqualityFmaintenanceEnables querying Romanian financial regulation data, including regulations, enforcement actions, and currency checks, directly from AI assistants.6Apache 2.0
- AlicenseAqualityBmaintenanceEnables read-only search of Romanian legislation and multi-tier court decisions (first instance, appellate, supreme/constitutional), retrieval of full texts as Markdown, and verification of statutory and case law citations against official registries.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Romanian leu reference exchange rates from the National Bank of Romania for any day since 2005, converting amounts to and from RON, exploring historical rate series, and computing ANAF-style annual averages.68 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct domain object: company_financials (filings), company_lookup (registry status), court_cases (litigation), exchange_rate (FX), iban_check (bank validation), and shop_check (composite first-pass). company_financials vs company_lookup could be blurred but the descriptions clearly separate financials from registry/VAT status, and shop_check is explicitly positioned as a wrapper over the others.
All names are consistently snake_case with a domain_entity or verb_noun shape, which reads predictably. There is slight variation between noun_noun (court_cases, exchange_rate) and verb_noun (company_lookup, shop_check, iban_check), but the convention is readable and uniform.
Six tools is well-scoped for a Romanian company-vetting server, with each tool earning a clear place. No redundancy or filler: the composite shop_check and the granular primitives complement rather than duplicate each other.
The surface covers the core vetting lifecycle: identity/status, financials, litigation, FX for invoices, IBAN sanity, and an aggregate risk check. The notable gap is that company_lookup only accepts CUI, so name-based discovery is a dead end (though this is a real ANAF constraint, not a design omission).