mcp-registry/io.github.foundrynet/email-verify-mcp · v3.4.4
Also listed as glama/foundrynet/b2b-lead-quality-scorer-mcp
As of 2026-10-16 07:35 UTC, the Foundrynet Email Verify MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 1 minutes.
Verify emails — deliverability, disposable/role/free detection, MX validity, domain age.
Point your MCP client at this streamable-http endpoint: https://email-verify-mcp-production.up.railway.app/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
Handshake + tools/list takes ~10,938 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.foundrynet%2Femail-verify-mcp/fixes
{
"name": "mint_info",
"description": "FoundryNet Data Network + MINT Protocol details (FREE). How to attest your\nagent's email/contact verification on-chain for verifiable proof of work, and\nthe sibling data servers available across the network.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.foundrynet/email-verify-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.foundrynet/email-verify-mcp"}) over MCP.
daily_brief ~360 tokenslead_quality_score ~319 tokensbatch_lead_score ~290 tokensbatch_verify ~290 tokensverify_email ~278 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.foundrynet%2Femail-verify-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.foundrynet%2Femail-verify-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.foundrynet%2Femail-verify-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.foundrynet%2Femail-verify-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.foundrynet%2Femail-verify-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1efc6b4d073e8f5e…, first seen 2026-10-17, included at leaf 14041 of 17,510. Version history · verify what your client received.
Compare: most reliable data servers · most reliable email servers · most reliable sales servers · most reliable blockchain servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-16 07:35 UTC, the Foundrynet Email Verify MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 1 minutes.
Foundrynet Email Verify MCP server advertises 7 tools, including batch_lead_score, batch_verify, brief_summary, daily_brief, lead_quality_score.
Point your MCP client at this streamable-http endpoint: https://email-verify-mcp-production.up.railway.app/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.