# EmailVerify by Techforce Global (remote · cloud.techforce.global)

Verify email addresses: syntax, MX, disposable, role, SMTP mailbox, catch-all and typo checks.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cloud.techforce.global`: 76/100 (this document), [markdown](https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp.md), [page](https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp)

## Channel facts

- Endpoint: `https://cloud.techforce.global/emailverify/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http global-techforce-cloud-emailverify 'https://cloud.techforce.global/emailverify/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "global-techforce-cloud-emailverify": {
      "url": "https://cloud.techforce.global/emailverify/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "global-techforce-cloud-emailverify": {
      "type": "http",
      "url": "https://cloud.techforce.global/emailverify/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.global-techforce-cloud-emailverify]
url = "https://cloud.techforce.global/emailverify/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "global-techforce-cloud-emailverify": {
      "type": "remote",
      "url": "https://cloud.techforce.global/emailverify/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add global-techforce-cloud-emailverify --url 'https://cloud.techforce.global/emailverify/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  global-techforce-cloud-emailverify:
    url: "https://cloud.techforce.global/emailverify/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "global-techforce-cloud-emailverify": {
      "Transport": "http",
      "Url": "https://cloud.techforce.global/emailverify/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add global-techforce-cloud-emailverify -t streamable-http -u 'https://cloud.techforce.global/emailverify/mcp'
```

### Other

```json
{
  "mcpServers": {
    "global-techforce-cloud-emailverify": {
      "type": "http",
      "url": "https://cloud.techforce.global/emailverify/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +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.

### 2026-11-02 (score 75, +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.

### 2026-10-31 (score 74, +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.

### 2026-10-30 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 73)

First indexed and scored.

## MCP tools (2)

### `verify_email` (~108 tokens)

Verify email address

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.

Input parameters:

- `email` (string, required): The email address to verify, e.g. john.doe@company.com

Output parameters:

- `business_email` (boolean)
- `checks` (object)
- `confidence` (number)
- `did_you_mean` (string|null)
- `email` (string)
- `flags` (array)
- `free_provider` (boolean)
- `mail_provider` (string|null)
- `reasons` (array)
- `score` (number)
- `status` (string)

### `verify_email_batch` (~83 tokens)

Verify a list of emails

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.

Input parameters:

- `emails` (array, required): Email addresses to verify (1-50)

Output parameters:

- `count` (number)
- `results` (array)
- `summary` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://cloud.techforce.global/emailverify/mcp
- Website: https://emailverify.techforce.global/
- Changelog RSS feed: https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/global-techforce-cloud-emailverify/emailverify-mcp