Model Context Protocol
Verify emails from any AI agent.
Hosted MCP server, one verify_email tool. No install.
01 — setup
Get a key.
Sign up at app.skink.dev — 100 free credits, no card. Create a key under Dashboard → Keys.
02 — config
Client config.
Replace SKINK_API_KEY with your key in each.
Claude Desktop
Settings → Developer → Edit Config, paste this in:
{
"mcpServers": {
"skink": {
"command": "npx",
"args": ["mcp-remote", "https://api.skink.dev/mcp", "--header", "Authorization:Bearer SKINK_API_KEY"]
}
}
}Claude Code
Run in your terminal:
claude mcp add skink -- npx mcp-remote https://api.skink.dev/mcp \ --header "Authorization:Bearer SKINK_API_KEY"
Cursor
Settings → MCP → Add new MCP server, paste this in:
{
"mcpServers": {
"skink": {
"command": "npx",
"args": ["mcp-remote", "https://api.skink.dev/mcp", "--header", "Authorization:Bearer SKINK_API_KEY"]
}
}
}Other clients: use the Streamable HTTP transport at https://api.skink.dev/mcp, with an Authorization: Bearer SKINK_API_KEY header.
03 — reference
Tool reference.
| argument | meaning |
|---|---|
| Address to verify. Required. | |
| fast_fail | Optional. Skip the SMTP probe for a faster, lower-confidence result. |
| effort | Optional. thorough retries harder against catch-all/greylist servers, at higher latency. Mutually exclusive with fast_fail. |
{
"name": "verify_email",
"arguments": { "email": "jane.doe@acme.com", "fast_fail": false }
}Plain HTTP instead?
See the API docs