Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Veille MCP Server Check if john.doe@tempmail.com is a disposable email and give me its risk score"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Official Model Context Protocol server for the Veille fraud prevention API.
Validate emails, domains, IPs, VAT numbers and IBANs in milliseconds to block fake sign-ups, bots and fraud.
It lets Claude, Cursor, VS Code, Windsurf and any MCP client call the API as tools. Runs over stdio (local) or Streamable HTTP (self-hosted).
Related MCP server: email-verify
Veille runs this server for you at https://mcp.veille.io/ (Streamable HTTP). Send your API key in the x-api-key header; nothing to install.
claude mcp add --transport http veille https://mcp.veille.io/ --header "x-api-key: YOUR_API_KEY"{
"mcpServers": {
"veille": {
"url": "https://mcp.veille.io/",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}The hosted server and this package expose the same API; run the package locally when you want stdio, your own network egress, or to self-host it.
claude mcp add veille --env VEILLE_API_KEY=YOUR_API_KEY -- npx -y @veilleio/mcpAdd the server to the client's MCP configuration (claude_desktop_config.json, .cursor/mcp.json…):
{
"mcpServers": {
"veille": {
"command": "npx",
"args": ["-y", "@veilleio/mcp"],
"env": {
"VEILLE_API_KEY": "YOUR_API_KEY"
}
}
}
}{
"servers": {
"veille": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@veilleio/mcp"],
"env": {
"VEILLE_API_KEY": "${input:veille-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "veille-api-key",
"description": "Veille API key",
"password": true
}
]
}Download the .mcpb bundle from the releases page and open it; Claude Desktop asks for your API key.
docker build -t veille-mcp .
docker run -i --rm -e VEILLE_API_KEY=YOUR_API_KEY veille-mcpTool | Description |
| Check any domain instantly. Detects disposable email providers, public webmail, relay services, and education domains. Returns DNS health with MX provider detection, domain history, and optional SSL/… |
| Validate any email address in a single call. Detects disposable and temporary inboxes, identifies role accounts, public webmail, relay services, and returns a 0-100 risk score. For deep deliverabilit… |
| Deep email deliverability verification. Performs full Email Validation plus SMTP inbox check, catch-all detection, and returns a qualification verdict (valid, invalid, risky, disposable, unknown). |
| Assess the reputation of any IP address. Detects VPNs, proxies, Tor exit nodes, datacenter hosting, abusive traffic, and bots. Returns geolocation, network owner, and a 0-100 threat score. |
| Validate any phone number in E.164 format. Detects disposable and virtual numbers, identifies carrier and line type (mobile/fixed/VoIP), returns country and timezone, and computes a 0-100 risk score. |
| Infrastructure health for an engine or endpoint over the last hour. Not scoped to your account or tenant. Enabled per account: HTTP 403 means contact support to activate it. |
| Retrieve real-time usage statistics and credit balance for your Veille account. |
| Validate a European VAT number against the VIES database. Returns company name, registered address, and validity status for any EU member state. |
| Validate any IBAN and retrieve associated bank details. Returns the BIC/SWIFT code, bank name, country, BBAN structural breakdown, and SEPA zone membership. |
| Get current ECB exchange rates for any supported base currency. Optionally filter to specific target currencies. Updated daily from the European Central Bank. |
Every tool that calls the API consumes credits. JSON results are returned as text; images are returned inline and other files (PDF…) as embedded resources, up to 4 MB.
npx @veilleio/mcp --http --port 3000The endpoint is POST /mcp (stateless, JSON responses). Each client sends its own key in the x-api-key header (or Authorization: Bearer <key>); the server never uses a key of its own. It binds to 127.0.0.1 by default and rejects browser origins unless you allow them — put it behind TLS before exposing it.
createHttpHandler() is exported for Fetch-compatible runtimes (Cloudflare Workers, Deno, Bun):
import { createHttpHandler } from "@veilleio/mcp";
export default { fetch: createHttpHandler({ allowedOrigins: [] }) };The API key is read from VEILLE_API_KEY (stdio) or the request headers (HTTP) and removed from error messages.
Content fetched from websites is untrusted: the server instructions tell the model to treat it as data, not instructions.
See SECURITY.md to report a vulnerability.
npm install
npm test
npm run build
npx @modelcontextprotocol/inspector node dist/stdio.jsThe server uses the official Node.js SDK (@veilleio/sdk).
SDK | Package | Install |
Node.js |
| |
Python |
| |
Go |
| |
.NET |
| |
Ruby |
| |
PHP |
| |
Java | build from source, see its README | |
CLI |
| |
MCP server |
|
MIT — see LICENSE.
Domain Validation. Check any domain instantly. Detects disposable email providers, public webmail, relay services, and education domains. Returns DNS health with MX provider detection, domain history, and optional SSL/TLS certificate transparency. Credit cost: 2 credits per call.
Inputs: query (required), fields, certificate_transparency.
Email Validation. Validate any email address in a single call. Detects disposable and temporary inboxes, identifies role accounts, public webmail, relay services, and returns a 0-100 risk score. For deep deliverability verification (SMTP check, catch-all de… Credit cost: 3 credits per call.
Inputs: query (required), fields.
Email Qualification. Deep email deliverability verification. Performs full Email Validation plus SMTP inbox check, catch-all detection, and returns a qualification verdict (valid, invalid, risky, disposable, unknown). Credit cost: 5 credits per call.
Inputs: query (required), fields.
IP Reputation. Assess the reputation of any IP address. Detects VPNs, proxies, Tor exit nodes, datacenter hosting, abusive traffic, and bots. Returns geolocation, network owner, and a 0-100 threat score. Credit cost: 2 credits per call.
Inputs: query (required), fields.
Phone Validation. Validate any phone number in E.164 format. Detects disposable and virtual numbers, identifies carrier and line type (mobile/fixed/VoIP), returns country and timezone, and computes a 0-100 risk score. Credit cost: 1 credit per call.
Inputs: query (required), fields.
Stats. Infrastructure health for an engine or endpoint over the last hour. Not scoped to your account or tenant. Enabled per account: HTTP 403 means contact support to activate it.
Inputs: path, engine.
Usage. Retrieve real-time usage statistics and credit balance for your Veille account.
Inputs: no named parameters.
VAT Validation. Validate a European VAT number against the VIES database. Returns company name, registered address, and validity status for any EU member state. Credit cost: 1 credit per call.
Inputs: query (required), fields.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.
Email, phone, domain, URL & OFAC verification; phishing and IBAN checks via x402.
Verify companies, domains and counterparties before transacting. Sanctions, UBO, fraud scoring.
Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.
