EmailVerify by Techforce Global
global.techforce.cloud/emailverifycloud.techforce.globalstreamable-httpv1.0.0Scanned
Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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.
2 tools
Changes things 2Claude Code: ask
verify_emailCheck if a single email address is real and deliverable.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 Check if a single email address is real and deliverable. Runs syntax, domain/MX, disposable, role-account, live SMTP mailbox, catch-all, SPF/DMARC and typo checks, and returns status (valid / invalid / risky / unknown), a 0-100 confidence score, reasons and a did_you_mean suggestion for likely typos. Takes 1-20 seconds.
Annotations the server declares
- title: Verify email address
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_email_batchVerify up to 50 email addresses in one call (for example a lead list before an outreach campaign).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 up to 50 email addresses in one call (for example a lead list before an outreach campaign). Returns a count per status (valid / invalid / risky / unknown) and the full result for each address. Duplicates are checked once. For larger lists, split into several calls.
Annotations the server declares
- title: Verify a list of emails
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 write2
- 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.
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 emailverify https://cloud.techforce.global/emailverify/mcpclaude mcp add --transport http emailverify https://cloud.techforce.global/emailverify/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__emailverify__verify_email",
"mcp__emailverify__verify_email_batch"
],
"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 emailverify. Review it before you use it.
Capability tags behind 2 rules
- mcp__emailverify__verify_email untrusted-input
- mcp__emailverify__verify_email_batch 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://anlyon.dev/api/v1/servers/global.techforce.cloud/emailverify/verify?hash=e79f0ded4a189da3b352176a50ac2da7eeeaa1607cc60896338158fb065452e7" | jq -e '.changed == false'Pinned hash e79f0ded4a18, from Oct 29, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/global.techforce.cloud/emailverify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/global.techforce.cloud/emailverify)Source: MCP Registry. Synced Oct 29, 2026, 10:17 UTC.