looktwice-mcp
Related Servers
Alternatives to looktwice-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes an email verification tool, returning verdicts of valid, invalid, or risky with reasons.-
- AlicenseAqualityCmaintenanceEmail validation MCP server using MailboxValidator API to determine validity of an email address.320 npm1MIT
- FlicenseAqualityBmaintenanceA local MCP server providing payment validation tools and resources, including card number Luhn checks, card network detection, and IBAN validation, with no network calls required.3-
- AlicenseNot gradedqualityBmaintenanceAn MCP server for validating JSON against schemas, checking email deliverability, verifying URLs, assessing data quality, and validating API responses using RFC-compliant checks and heuristic analysis.4 npm40 PyPIMIT
- AlicenseAqualityBmaintenanceLocal MCP server for validating EU VAT numbers using the official VIES API. Enables AI to check VAT validity and optionally retrieve consultation numbers for legal proof.2MIT
- FlicenseNot gradedqualityDmaintenanceComprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.-
TDQS
Scored across 6 tools
Each tool targets a distinct entity type—email, IBAN, VAT, domain, product recall, and credits—so there is no overlap or ambiguity in purpose. An agent can clearly differentiate them without confusion.
Most tools follow a consistent [entity]_check pattern (email_check, iban_check, vat_check, domain_check), but cpsc_recall_match and credits_balance deviate from this verb convention. The naming is still mostly predictable and readable.
With six tools, the set is well-scoped for a validation/lookup server. Each tool serves a specific, justified function without redundancy or excessive specialization.
The set covers the main validation types a user would expect (email, IBAN, VAT, domain, product recall) and includes a balance check for the API. Minor gaps exist, such as phone or IP validation, but these are not critical to the core purpose.