# Email Verification MCP (remote · email-verify-mcp-production.up.railway.app)

Verify emails — deliverability, disposable/role/free detection, MX validity, domain age.

- Trust score: 62/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `email-verify-mcp-production.up.railway.app`: 62/100 (this document), [markdown](https://verifymcp.io/servers/foundrynet-email-verify-mcp/email-verify-mcp-production.md), [page](https://verifymcp.io/servers/foundrynet-email-verify-mcp/email-verify-mcp-production)

## Channel facts

- Endpoint: `https://email-verify-mcp-production.up.railway.app/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-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http foundrynet-email-verify-mcp https://email-verify-mcp-production.up.railway.app/mcp
```

### Codex

```toml
[mcp_servers.foundrynet-email-verify-mcp]
url = "https://email-verify-mcp-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "foundrynet-email-verify-mcp": {
      "type": "remote",
      "url": "https://email-verify-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add foundrynet-email-verify-mcp --url https://email-verify-mcp-production.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  foundrynet-email-verify-mcp:
    url: "https://email-verify-mcp-production.up.railway.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "foundrynet-email-verify-mcp": {
      "type": "http",
      "url": "https://email-verify-mcp-production.up.railway.app/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-07-31 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +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-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (7)

### `verify_email` (~200 tokens)

Verify a single email address — deliverability and quality signals for
lead enrichment, signup gating, and list hygiene. Returns deliverable
(true/false/unknown), mx_valid, disposable (throwaway/temp-mail), role_account
(info@, support@, …), free_provider (gmail, yahoo, …), domain_age_days, and a
best-effort smtp_check. Domain-level facts are cached 7 days.

PAID: $0.005 USDC per query after a daily free allowance (25/day). On a 402,
pay the returned Solana memo and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `email` (string, required): the email address to verify.
- `payment_tx`: Solana tx signature, when re-calling after a 402.

### `batch_verify` (~198 tokens)

Verify an array of email addresses in one call — the volume play for list
hygiene and bulk lead enrichment. Returns a per-email result array (same
signals as verify_email) plus a deliverable/disposable summary. Up to 100
emails per call; domain-level facts are cached and deduped, so repeat domains
are cheap.

PAID: $0.003 USDC per email, minimum $0.05, after the daily free allowance.
On a 402, pay the returned Solana memo and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `emails` (array, required): list of email addresses (max 100; deduped).
- `payment_tx`: Solana tx signature, when re-calling after a 402.

### `lead_quality_score` (~219 tokens)

Score a B2B lead 0-100 (grade A-F) from email deliverability + domain
credibility — decide whether a lead is worth your outreach time before you
spend it. Combines deliverable/MX validity, disposable & role-account & free-
provider detection, and domain age (cross-enriched from the FoundryNet brand-
intel network) into a single score, with named signals and a recommendation.

PAID: $0.01 USDC per lead after the daily free allowance (25/day). On a 402,
pay the returned Solana memo and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `domain`: optional company domain (defaults to the email's domain).
- `email` (string, required): the lead's email address.
- `payment_tx`: Solana tx signature, when re-calling after a 402.

### `batch_lead_score` (~200 tokens)

Score a batch of B2B leads in one call and get them back ranked best-first
— the volume play for prioritizing a prospect list. Each lead is scored 0-100
(A-F) on email deliverability + domain credibility; returns a ranked result
array plus a grade distribution and average score. Up to 100 leads per call.

PAID: $0.01 USDC per lead, minimum $0.05, after the daily free allowance. On a
402, pay the returned Solana memo and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `leads` (array, required): list of email addresses (max 100; deduped).
- `payment_tx`: Solana tx signature, when re-calling after a 402.

### `daily_brief` (~240 tokens)

Get the curated daily email-verification brief — the day's verification
activity in one package: volume, deliverability mix, disposable-domain hit
rate, and the most-queried + most-flagged domains. Each brief carries a MINT
provenance attestation so a buyer can verify it was produced by this server,
unaltered.

PAID: $5 USDC per brief. Defaults to today (UTC); a brief expires at the next
midnight UTC. On a 402, pay the returned Solana memo and re-call with the SAME
args plus payment_tx=<signature>. An fnet_ Bearer key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `date`: brief date YYYY-MM-DD (default today, UTC).
- `payment_tx`: Solana tx signature, when re-calling after a 402.
- `stripe_token`: Stripe Checkout Session id (cs_…), when re-calling after paying the Stripe payment link (alternative to x402). Can also be supplied via the X-Stripe-Token header.

### `brief_summary` (~169 tokens)

Get the top 5 signals from today's brief as structured JSON — a cheap
sample of the full daily_brief. Returns the day's highest-priority items
(no prose) so an agent can decide whether to buy the full brief.

PAID: $0.50 USDC (vs the full daily_brief price). Defaults to today (UTC).
On a 402, pay the returned Solana memo and re-call with the SAME args plus
payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Input parameters:

- `agent_id`: stable id for your agent (scopes the free-tier counter).
- `date`: brief date YYYY-MM-DD (default today, UTC).
- `payment_tx`: Solana tx signature, when re-calling after a 402.

### `mint_info` (~51 tokens)

FoundryNet Data Network + MINT Protocol details (FREE). How to attest your
agent's email/contact verification on-chain for verifiable proof of work, and
the sibling data servers available across the network.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/foundrynet-email-verify-mcp/email-verify-mcp-production#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 62
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://email-verify-mcp-production.up.railway.app/mcp
- Repository: https://github.com/FoundryNet/email-verify-mcp
- Changelog RSS feed: https://verifymcp.io/servers/foundrynet-email-verify-mcp/email-verify-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/foundrynet-email-verify-mcp/email-verify-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/foundrynet-email-verify-mcp/email-verify-mcp-production