Veille MCP Server
OfficialRelated Servers
Alternatives to Veille MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceComprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.MIT
- AlicenseAqualityDmaintenanceEnables real-time email verification via MCP tools, checking syntax, MX, disposable domains, and optional SMTP probe to determine deliverability with a VALID/RISKY/INVALID verdict.210 npmMIT
- FlicenseAqualityBmaintenanceEnables email address verification through a single MCP tool, returning whether an address is valid, invalid, or risky.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and onboarding/KYB workflows to validate VAT and EORI numbers, look up companies, screen sanctions lists, and run combined checks through remote MCP tools and a pay-per-call API.MIT
- AlicenseAqualityBmaintenanceLimitguard MCP server: lead validation for AI agents. Checks the company behind a lead in the Dutch (KVK) and Belgian (KBO) registers, EU VAT (VIES) and sanctions lists. Pay per call with x402 or an API key.101MIT
- AlicenseNot gradedqualityCmaintenanceEnables real-time email verification, phone and WhatsApp validation, caller ID, IP geolocation, blacklist and spam checks, web and social scraping, Google SERP lookups, and AI brand visibility audits through 19 tools. It runs as a hosted Streamable HTTP endpoint with an included stdio bridge so any MCP client can connect out of the box.MIT
TDQS
Scored across 10 tools
Most tools target distinct resources, but there are real collision risks: `intelligence_email` is a strict subset of `intelligence_emailq` (same payload, different depth), `vat_rates` is actually ECB exchange rates rather than VAT rates (only the description saves it), and `usage` vs `stats` both read as 'account/health numbers'. Descriptions do resolve these, but an agent skim-reading names will misselect.
Two families coexist without a unifying verb_noun schema: prefixed intelligence tools (`intelligence_domain/email/emailq/ip/phone`) versus bare or vat_ prefixed tools (`vat`, `vat_rates`, `vat_iban`, `usage`, `stats`). The `emailq` abbreviation and the `vat_rates` name that does not validate VAT rates are both actively misleading.
Ten tools is well within a healthy range for a data-validation API and each maps to a discrete check (email, email qualification, phone, IP, domain, IBAN, VAT, FX, usage, health). No filler or single-purpose bloat.
Core validation primitives for a data-quality suite are all present (email, phone, domain, IP, IBAN, VAT), so the main lifecycle is covered. Gaps are minor but real: no batch/bulk validation, no address or company/name validation, and `usage` only shows current balance with no history or top-up path.