EmailVerify by Techforce Global
REMOTE · CLOUD.TECHFORCE.GLOBAL
Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks.
Available components
Last scanned (7 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 313 tokens (~156/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://cloud.techforce.global/emailverify/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cloud.techforce.global | CN=YE1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 605c5337613c49b884d1d2c16b1034320d8 |
| SANs: cloud.techforce.global | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of cloud.techforce.global. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| global. | DS published | 13060, 52924 | 8, 8 | Verified |
| techforce.global. | DS published | 2371 | 13 | Verified |
| cloud.techforce.global. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cloud.techforce.global/emailverify/mcp | Verified | 200 | |
| http (plaintext) | http://cloud.techforce.global/emailverify/mcp | HTTPS enforced | 301 | https://cloud.techforce.global/emailverify/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify_email Verify email address ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify, e.g. john.doe@company.com |
| Name | Type | Req | Description |
|---|---|---|---|
| business_email | boolean | – | – |
| checks | object | – | – |
| confidence | number | – | – |
| did_you_mean | string|null | – | – |
| string | yes | – | |
| flags | array | – | – |
| free_provider | boolean | – | – |
| mail_provider | string|null | – | – |
| reasons | array | – | – |
| score | number | yes | – |
| status | string | yes | – |
No examples provided.
verify_email_batch Verify a list of emails ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify (1-50) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| results | array | yes | – |
| summary | object | yes | – |
No examples provided.
How do I install the EmailVerify by Techforce Global MCP server?
EmailVerify by Techforce Global is a hosted endpoint at https://cloud.techforce.global/emailverify/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cloud.techforce.global
claude mcp add --transport http global-techforce-cloud-emailverify 'https://cloud.techforce.global/emailverify/mcp'
What is the EmailVerify by Techforce Global MCP server?
EmailVerify by Techforce Global is an MCP server listed in the public MCP registry as global.techforce.cloud/emailverify. Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks. This page covers its hosted endpoint (https://cloud.techforce.global/emailverify/mcp).
Is the EmailVerify by Techforce Global MCP server safe to use?
EmailVerify by Techforce Global scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EmailVerify by Techforce Global MCP server expose?
EmailVerify by Techforce Global exposes 2 tools: verify_email, verify_email_batch. Their descriptions and schemas cost roughly 191 tokens of context every time the server is loaded.
Does the EmailVerify by Techforce Global MCP server require authentication?
No. We connected to EmailVerify by Techforce Global without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EmailVerify by Techforce Global MCP server still maintained?
EmailVerify by Techforce Global is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EmailVerify by Techforce Global MCP server?
VerifyMCP ran 13 checks on EmailVerify by Techforce Global, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.