Verifai — Email Verification & Domain Intelligence MCP server
io.github.zikriz/verifaizikrizstreamable-httpv1.0.0Scanned
Email verification and domain intelligence for AI agents. MX, RDAP, SSL checks. 25 free credits.
7 tools: 7 change things.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Verifai — Email Verification & Domain Intelligence MCP server can do
The Verifai — Email Verification & Domain Intelligence MCP server is published by the GitHub account zikriz. It has 7 tools. It can create or change data (7 tools: register_free_key, verify_email, verify_emails, domain_intel and 3 more), but cannot delete data. None of its tools only reads.
3 tools bring in text other people can write (verify_email, verify_emails and domain_intel).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 7Claude Code: ask
add_creditsOWNER ONLY: add credits to a customer's key after payment is received.No findings
Why it is in this group
- The name "add_credits" says "add": a word for a change.
Description, as the server wrote it OWNER ONLY: add credits to a customer's key after payment is received.
Annotations the server declares
- title: Add Credits (Owner Only)
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
admin_statsOWNER ONLY: business overview — total customers, calls made, credits outstanding, paid vs free breakdown.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it OWNER ONLY: business overview — total customers, calls made, credits outstanding, paid vs free breakdown.
Annotations the server declares
- title: Admin Stats (Owner Only)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
check_creditsCheck remaining credits for an API key.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check remaining credits for an API key.
Annotations the server declares
- title: Check Credit Balance
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
domain_intelDomain intelligence: DNS records (A/AAAA/MX/NS/TXT), RDAP registration (registrar, created/expiry dates, status) and SSL certificate days left.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Domain intelligence: DNS records (A/AAAA/MX/NS/TXT), RDAP registration (registrar, created/expiry dates, status) and SSL certificate days left. Costs 1 credit.
Annotations the server declares
- title: Domain Intelligence
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
register_free_keyRegister a free API key with starter credits.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Register a free API key with starter credits. One per agent; paid top-ups available from the operator.
Annotations the server declares
- title: Register Free API Key
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
verify_emailVerify one email address: syntax, disposable-provider check, and MX (mail server) lookup to judge deliverability.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Verify one email address: syntax, disposable-provider check, and MX (mail server) lookup to judge deliverability. Costs 1 credit.
Annotations the server declares
- title: Verify Email Address
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
verify_emailsBulk-verify up to 50 emails.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Bulk-verify up to 50 emails. Costs 1 credit per address.
Annotations the server declares
- title: Verify Emails (Bulk)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://165-227-136-26.sslip.io/mcp: tools/list returned 7 tools to an anonymous client, including register_free_key (write), verify_email (write), verify_emails (write), domain_intel (write), check_credits (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http verifai https://165-227-136-26.sslip.io/mcpclaude mcp add --transport http verifai https://165-227-136-26.sslip.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__verifai__register_free_key",
"mcp__verifai__verify_email",
"mcp__verifai__verify_emails",
"mcp__verifai__domain_intel",
"mcp__verifai__check_credits",
"mcp__verifai__admin_stats",
"mcp__verifai__add_credits"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as verifai. Review it before you use it.
Capability tags behind 3 rules
- mcp__verifai__verify_email untrusted-input
- mcp__verifai__verify_emails untrusted-input
- mcp__verifai__domain_intel untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.zikriz/verifai/verify?hash=451098753d0f5cc3f00a1c7897f44fa03638cbfa1484f9674421ca6584c5970b" | jq -e '.changed == false'Pinned hash 451098753d0f, from Nov 21, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.zikriz/verifai/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.zikriz/verifai)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.
Verifai — Email Verification & Domain Intelligence MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Verifai — Email Verification & Domain Intelligence MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Verifai — Email Verification & Domain Intelligence MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Verifai — Email Verification & Domain Intelligence MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Verifai — Email Verification & Domain Intelligence MCP server have?
- 7 tools: 7 write. register_free_key, verify_email, verify_emails, domain_intel, check_credits, admin_stats and add_credits.
Does the Verifai — Email Verification & Domain Intelligence MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Verifai — Email Verification & Domain Intelligence MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Verifai — Email Verification & Domain Intelligence MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.