DaData.ru
DaData provides APIs for data validation, standardization, and enrichment, including address parsing, company information retrieval, and more.
Verdict
Common use cases
- Validate customer addresses before shipment
- Parse Cyrillic names into surname, given name, patronymic
- Verify passport numbers against federal registry
- Standardize phone numbers from web forms
- Geocode postal addresses to FIAS identifiers
Integration
- Vendor
- DaData.ru
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 42
- Composio slug
dadata_ru
Tools
- Clean Address
Tool to clean and standardize russian postal addresses. use when you need structured address fields from raw strings.
- Clean Birthdate
Tool to standardize and validate birthdate strings. use after capturing raw birthdate inputs to normalize them to yyyy-mm-dd.
- Clean Email
Tool to standardize and validate email addresses. use when you have raw email input and need to fix typos, correct domains, and classify as personal, corporate, or disposable. use after collecting user-provided emails.
- Clean Name (FIO)
Tool to standardize and parse full names (fio), detect gender, and return grammatical cases. use when you need structured name parsing and declensions from raw fio inputs.
- Clean Passport
Tool to validate a russian passport number against the official registry. use after collecting passport details.
- Clean Phone
Tool to standardize and validate phone numbers. use when you need to convert arbitrary phone inputs into a uniform, validated 11-digit format for further processing.
- Clean Vehicle
Tool to standardize and parse vehicle data fields. use after obtaining raw vehicle info to extract brand, model, year, vin, and other identifiers.
- Find Address
Tool to find address by identifier. use when you need full address details from a cadastral number, fias id, or kladr code.
- Find Bank
Tool to find bank by bic, swift, inn, or registration number. use when you need full bank details for a specific identifier. provide optional kpp for branch-level queries.
- Find Belarus Party by UNP
Tool to find a belarusian company or entrepreneur by unp. use when you have the unp and need the full registry record. example: "find party by unp = 190657494".
- Find Car Brand
Tool to find car brand by its identifier. use when you need detailed car brand information by code. example: find details for brand code '1010'.
- Find Company or Entrepreneur
Tool to find company or individual entrepreneur details by inn, ogrn, or kpp. use when you have a valid identifier and need full registration data.
- Find Country
Tool to find country details by iso or numeric code. use when you have a valid country code and need full metadata.
- Find Currency
Tool to find currency details by iso 4217 code. use when you have a currency code and need its full metadata.
- Find Delivery City IDs
Tool to get delivery service city ids by kladr code. use when you need the cdek, boxberry, or dpd city identifiers for a given kladr code.
- Find FMS Unit
Tool to find passport authority (fms unit) by code. use when you have the fms unit code or name and need to retrieve detailed authority information.
- Find FTS Unit
Tool to find customs (fts) office by code. use when you have a customs office identifier and need detailed information.
- Find Kazakhstan Company by BIN
Tool to find kazakhstan company or entrepreneur details by bin or name. use when you have a bin or official name and need specific registration data for kz entities.
- Find MKTU
Tool to find mktu classification details by code. use when you have an mktu code and need its descriptions and metadata.
- Find OKVED2
Tool to find okved2 classifier entries by code. use when you have an okved2 code and need full metadata.
- Geolocate Address
Tool to find nearest addresses by geographic coordinates. use when you need address suggestions around a specific location.
- Get Profile Balance
Tool to retrieve current dadata account balance. use before making api calls that consume funds.
- Get Profile Statistics
Tool to get daily aggregated usage statistics per dadata api service. use when you need a breakdown of calls and remaining balances for a specific date.
- Get Reference Versions
Tool to retrieve the last update dates for dadata reference datasets (fias, egrul, banks, etc.). use before performing operations that depend on the currency of reference data.
- IP Locate Address
Tool to determine russian address by ip. use when you need to resolve an ip to city/region data.
- Suggest Address
Tool to autocomplete and suggest addresses. use when user types partial address fragments to retrieve possible address completions.
- Suggest Bank
Tool to autocomplete and suggest banks by partial details. use when you need to find russian banks by name, bic, inn, swift, or registry number.
- Suggest Car Brand
Tool to suggest car brands. use when you need to autocomplete or correct partial car brand names in russian or english.
- Suggest Court
Tool to suggest russian courts by name or location. use when user types partial court name or provides filters to retrieve possible court suggestions.
- Suggest Currency
Tool to suggest currencies by iso 4217 code or name. use when you need currency autocompletion.
- Suggest Email
Tool to autocomplete and suggest email addresses. use when user provides an email prefix and you need possible completions.
- Suggest FMS Unit
Tool to autocomplete and suggest passport issuing authorities. use when you need to lookup russian fms units by partial code or name.
- Suggest FNS Unit
Tool to suggest russian tax inspection units by partial name or code. use when you need to identify a tax inspection authority from incomplete user input. for example, use query='7700' to retrieve units with code 7700.
- Suggest FTS Unit
Tool to autocomplete and suggest russian customs (fts) units. use when user provides partial name or code to retrieve matching offices.
- Suggest Metro
Tool to suggest metro stations. use when you need to autocomplete metro station names in russian cities.
- Suggest MKTU
Tool to suggest mktu entries. use when you need to autocomplete or find international classifier of goods and services codes based on name or description.
- Suggest Name
Tool to autocomplete and suggest full names (fio). use when user types partial name fragments to retrieve possible full name completions.
- Suggest OKPD2
Tool to autocomplete and suggest russian product classification codes (okpd2). use when you need to find or validate okpd2 codes by partial queries.
- Suggest OKTMO
Tool to suggest russian municipal territory codes (oktmo). use when user needs to autocomplete or search for oktmo codes by name or code fragment.
- Suggest OKVED2
Tool to suggest okved2 codes by text query. use when you have a fragment of a russian economic activity code or name and need structured suggestions.
- Suggest Party
Tool to autocomplete and suggest russian companies or entrepreneurs. use when you have a partial name, inn, ogrn, or address and need structured suggestions.
- Suggest Postal Unit
Tool to suggest russian postal units by index or coordinates. use when autocompleting postal office codes or finding nearby mail offices.
Setup
Setup guide
- 11. Sign up at dadata.ru and generate an API key from your account dashboard. 2. In Switchy, open Settings → Integrations → MCP Servers and click 'Add Server'. 3. Select 'DaData.ru' from the list and paste your API key when prompted. 4. Click 'Connect' — Switchy tests the key by calling the service health endpoint. 5. Once connected, open any Space and type '@DaData.ru' to see available tools in the autocomplete menu. 6. Test the connection by running '@DaData.ru clean this phone number: +7 (999) 123-45-67' — you should receive a standardized 11-digit format. 7. The MCP exposes 42 tools; most require Russian-language input (Cyrillic addresses, FIO names, passport series). 8. If a tool returns an error, check that your API key has sufficient quota and that the input matches the expected format (e.g., passport numbers need series and number separated).
What teammates see: by default, memories from DaData.ru are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Clean Address List
@DaData.ru clean these addresses and return structured fields with postal codes: 'Москва, ул. Ленина, д. 5', 'СПб, Невский пр-т, 28', 'Екатеринбург, Малышева 101'Open in a Space →
Parse Full Names
@DaData.ru parse these Russian names and return gender plus genitive case for each: 'Иванов Иван Иванович', 'Петрова Мария Сергеевна', 'Сидоров Алексей'Open in a Space →
Validate Passport
@DaData.ru verify this passport number against the federal registry: series 4509, number 234567Open in a Space →
Standardize Phones
@DaData.ru clean these phone numbers and tell me which are mobile vs landline: '+7 999 123-45-67', '8(495)1234567', '9161234567'Open in a Space →
Enrich Vehicle Data
@DaData.ru parse this vehicle info and extract brand, model, year: 'LADA GRANTA 2015 XTA219000F0123456'Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@DaData.ru clean this phone number: 8-926-123-45-67 and tell me if it's valid
The phone number has been standardized to +7 926 123 45 67 (11-digit format). It's a valid mobile number registered to MTS in the Moscow region. The number is currently active according to the carrier database. The cleaned output includes the country code (+7), area code (926), and formatted digits for consistent storage.
This example shows DaData's phone validation strength: converting messy input into a uniform format while checking carrier validity. Requires an API key with phone-cleaning scope. Note that validation checks number format and carrier registry, but doesn't verify if the number is currently in service or who owns it.
@DaData.ru I have a customer named 'иванов иван иванович' — parse it and give me the genitive case for an invoice
The name has been parsed into structured fields: Last name 'Иванов', First name 'Иван', Patronymic 'Иванович'. Gender detected as male. For your invoice, the genitive case (родительный падеж) is 'Иванова Ивана Ивановича'. This is the correct form for phrases like 'счёт для Иванова Ивана Ивановича' (invoice for...).
This showcases DaData's Russian-language name parsing and grammatical case generation — essential for legal documents and formal correspondence in Russian markets. The tool handles Cyrillic input, detects gender from patronymics, and returns all six grammatical cases. Useful for invoice generation, contract templates, and CRM normalization.
@DaData.ru we collected 50 raw address strings from a signup form — can you batch-clean them and flag any that are incomplete or ambiguous?
All 50 addresses have been processed. 43 were successfully standardized with full FIAS codes, postal indices, and structured fields (region, city, street, house). 5 addresses are ambiguous (multiple matches found — e.g., 'Ленина 10' exists in 200+ cities) and require user clarification. 2 addresses are incomplete (missing house numbers). Each result includes a quality score (0-10) and a list of missing components.
This example highlights batch address cleaning for Russian postal data, a core DaData strength. The tool returns FIAS identifiers (federal address registry codes) for integration with logistics and government systems. Be aware: ambiguous addresses require follow-up prompts or user selection. API rate limits apply to batch requests (check your plan tier).
Use-case deep-dives
When DaData wins for customer record hygiene at scale
A 6-person sales team at a B2B SaaS company selling into Russia imports 2,000 leads per month from webforms, trade shows, and partner lists. Raw inputs are a mess: phone numbers missing country codes, addresses with typos, names in mixed case. DaData's Clean Phone, Clean Address, and Clean Name tools run on import to standardize everything before it hits Salesforce. The passport and vehicle cleaners sit unused unless you're in fintech or logistics—most teams only need the core three. Auth is straightforward API key management; no OAuth dance. If your CRM already has decent validation and you're not dealing with Cyrillic input, skip this MCP. If you're handling Russian customer data at any volume, DaData pays for itself in the first week by killing duplicate records and bad routing.
When real-time passport checks matter for compliance
A 12-person fintech startup building a Russian neobank uses DaData's Clean Passport tool during KYC onboarding. A customer types their passport number; the MCP hits the official registry and returns validity status in under a second. This blocks fake documents before manual review, cutting fraud escalations by 40%. The Clean Birthdate and Clean Name tools run in the same flow to catch typos that would fail downstream identity checks. The 42-tool catalog looks big, but most fintechs use five or six; the rest are niche (vehicle data, cadastral lookups). If you're not in a regulated vertical or don't operate in Russia, the compliance tooling is overkill. If you need to verify Russian government IDs in production, DaData is the only MCP that plugs directly into state registries without building your own integration.
When structured address fields unlock automated routing
A 20-person logistics company running last-mile delivery in Moscow gets 300 support tickets daily with address complaints. Customers paste addresses in free text; agents manually parse city, street, building number to reroute packages. DaData's Clean Address tool extracts structured fields (postal code, FIAS ID, geo coordinates) from raw strings, feeding them into the routing system without human touch. Find Address works the reverse direction when a driver reports a cadastral number from a rural delivery. The email and phone cleaners help dedupe customer records, but the real win is address normalization cutting ticket resolution time by half. If your delivery zone is outside Russia or you're under 50 tickets per day, manual parsing is faster than MCP setup. If you're scaling Russian logistics and drowning in address chaos, DaData turns unstructured text into routable data in one API call.
Frequently asked
What does the DaData.ru MCP do in Switchy?
It validates and standardises Russian data — postal addresses, phone numbers, passport IDs, full names, birthdates, vehicle registrations, and emails. The MCP calls DaData's API to clean messy inputs, detect typos, parse structured fields, and check official registries. Use it when your team needs reliable Russian data normalisation without writing custom validation logic.
Do I need a paid DaData account to use this MCP?
Yes. You need an API key from DaData.ru, which requires a paid subscription after the free tier runs out. The MCP authenticates with that key; Switchy doesn't bundle DaData credits. Check DaData's pricing page for current limits — the free tier typically covers a few thousand requests per month.
Can this MCP send validated data back to my CRM or database?
No. The DaData MCP only reads from DaData's API and returns cleaned results to your Switchy chat. To write validated addresses or phone numbers into Salesforce, Notion, or a database, chain this MCP with another integration that has write permissions — or export the cleaned data manually.
Why use this MCP instead of calling DaData's API directly?
The MCP wraps 42 DaData endpoints in natural-language tools, so your team can validate a passport or parse a name by typing a question — no curl commands, no JSON payloads. If you already have engineers writing Python scripts against DaData, stick with the API. If you want non-technical teammates to clean data in chat, use the MCP.
Who on my team should connect the DaData MCP?
Whoever holds your DaData API key and understands your data-quality workflows. Typically a data analyst, operations lead, or backend engineer. Once connected, any Switchy workspace member can invoke the tools — but only the person who added the MCP can rotate the key or disconnect it.