An MCP server exposing 8 production tools built on the NewKwLab API suite: email validation, phone number validation, payment card checks, nutrition lookup and other verification and data tools for agents and developers. All tools are live and production-tested.
Scored across 8 tools
Most tools target distinct resources: airport lookup vs. airport search are separated by input type (code vs. keyword), LEI search by name vs. LEI verify by code are distinct, and each validate_* targets a different data type. The only mild overlap is lookup_airport vs. search_airports, but the descriptions clarify the boundary.
All eight tools follow a snake_case verb_noun pattern (lookup_, search_, validate_, verify_, screen_). Minor deviation: lookup_ vs search_ vs verify_ are near-synonyms that could confuse, and search_lei_by_name is a longer form, but the overall convention is clear and predictable.
Eight tools is well within a healthy range and each earns its place: two for airports, two for LEI, three validators, and one sanctions screener. No redundant or trivial tools are present.
Each of the three domains (airports, LEI, data validation) has both a lookup and a search/verify path, giving good coverage. Minor gaps remain—e.g., no phone/IP validator and no batch or reverse-lookup operations—but agents can work around these.
Look up an airport by IATA, ICAO or local code in the OurAirports public-domain database (86k+ airports): name, coordinates, elevation, country, municipality and runway summary.
Inputs: code (required).
Screen a person or company name against the US OFAC SDN sanctions list (bundled snapshot, fuzzy matching with a similarity threshold) and return any matches with list details. An empty result means no match in the snapshot, not a legal clearance.
Inputs: name (required), limit.
Search airports by name or city keyword in the OurAirports public-domain database and return matching airports with codes and coordinates.
Inputs: q (required), limit.
Search the GLEIF registry by company legal name and return matching entities with their LEI codes, country and entity status.
Inputs: name (required), limit.
Validate a payment card number locally: Luhn check, length, network detection (Visa, Mastercard, Amex and more) and test-card detection. No network call is made to any payment processor and the full number is never stored; the result masks all but the first 6 and last 4 digits.
Inputs: number (required).
Validate an email address at domain level: syntax, domain and MX health, disposable-domain and role-account flags, typo suggestion and a 0-100 domain risk score. Does not probe whether the mailbox itself exists (no SMTP check).
Inputs: email (required).
Validate an EU (or UK) VAT number against the official VIES registry and return the registered business name and address when the registry provides them.
Inputs: number (required), country.
Verify a Legal Entity Identifier (LEI, ISO 17442) against the GLEIF registry: legal name, entity status, registration status and next renewal date, with a plain-language flag when the record has lapsed or has other issues.
Inputs: lei (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.