Email Validation Skill
The tool
Let your agent verify email addresses. Call it as an MCP tool to check format, domain and mailbox validity before your app trusts an email.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as EmailValidationSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "EmailValidationSkill",
"arguments": {
"email": "[email protected]"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about [email protected] in the terms this source covers is enough for it to reach for EmailValidationSkill on its own.
Connecting
One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.
{
"mcpServers": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.
| Argument | Type | Example | Description |
|---|---|---|---|
emailRequired | string | [email protected] | The email address to validate (e.g., [email protected]) |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"email": "[email protected]",
"domain": "myspace.com",
"username": "support",
"isRegexValid": true,
"hasTypo": false,
"isMxValid": true,
"isValid": true,
"isFreeEmail": false,
"isCompanyEmail": true,
"isDisposable": false,
"isRoleAccount": true,
"suggestedCorrection": null,
"riskScore": 10,
"riskLevel": "low"
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
email | string | [email protected] | The email address that was validated |
domain | string | myspace.com | The domain portion extracted from the email |
username | string | support | The username (local part) extracted from the email |
isRegexValid | boolean | true | Email passes standard regex format validation |
hasTypo | boolean | false | The address is malformed and fails format validation |
isMxValid | boolean | true | The domain has valid mail exchange (MX) records and can receive mail |
isValid | boolean | true | Indicates whether the email address is valid |
isFreeEmail | boolean | false | Domain belongs to a free consumer email provider |
isCompanyEmail | boolean | true | Domain appears to be a corporate/company domain |
isDisposable | boolean | false | Domain is a known disposable or throwaway email provider |
isRoleAccount | boolean | true | Mailbox is a role or shared address (e.g. info@, support@, noreply@) rather than a person |
suggestedCorrectionPremium | object | null | The likely intended email when a common domain typo is detected (e.g. gmial.com to gmail.com), otherwise null |
riskScorePremium | number | 10 | Composite 0-100 risk score combining deliverability, disposable, role and format signals (higher is riskier) |
riskLevelPremium | string | low | Risk band derived from the score: low, medium or high |
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use Email Validation Skill
Set up Email Validation Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use EmailValidationSkill?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
5 credits each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.