Mail7 Email Validation vs Discourse MCP
A side-by-side look at the Mail7 Email Validation and Discourse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mail7 Email Validation for communication work as a local process; choose Discourse MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mail7 Email Validation when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MAIL7_API_KEY, MAIL7_BASE_URL. - You want tools like
validate_email, validate_emails, check_domain.
Choose Discourse MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
discourse_select_site, discourse_search, discourse_filter_topics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 56/100 · Good | 87/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | MAIL7_API_KEYMAIL7_BASE_URL | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 77 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 4 | 16 |
| Full listing | View Mail7 Email Validation | View Discourse MCP |
Tools & capabilities
Mail7 Email Validation tools 4
validate_emailCheck whether a single email address is deliverable: syntax, domain MX records, disposable-domain database and a live SMTP mailbox probe. Status is one of "Valid", "Not Valid", "Unknown". Unknown means the mailbox could NOT be checked (catch-all domain, greylisting, blocked SMTP port) - it is NOT a bad address. Never delete, reject or report Unknown addresses as invalid; present them separately and let the user decide. Use validate_emails instead when you have more than one address.validate_emailsCheck up to 50 email addresses in one call and get a per-address verdict plus a summary. Status is one of "Valid", "Not Valid", "Unknown". Unknown means the mailbox could NOT be checked (catch-all domain, greylisting, blocked SMTP port) - it is NOT a bad address. Never delete, reject or report Unknown addresses as invalid; present them separately and let the user decide. Requires MAIL7_API_KEY (anonymous callers get a 25-address free sample only). Each address takes a few seconds of real SMTP work, so this call is slow by nature: for a longer list, split it and call this tool repeatedly with the next 50 addresses. Never run two calls in parallel - the API serialises one bulk job per client and the second call fails.check_domainAudit a domain's email setup in one call: MX records, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and BIMI, graded A-F with a fix for every problem found. Use this to answer "can this domain send and receive mail" or "why do our messages land in spam". Takes a domain (example.com), not an email address. The default answer summarises every section; pass `section` to get the full records and findings of one of them.check_spfFetch and analyse the SPF record of a domain: the raw record, its mechanisms, lookup count and common misconfigurations. Use check_domain instead when the question is about overall deliverability rather than SPF specifically.
Discourse MCP tools 16
discourse_select_siteValidate and select a Discourse site. Returns JSON with site URL and title.discourse_searchSearch site content. Returns JSON object with results array of matching topics (id, slug, title) and meta (total, has_more).discourse_filter_topicsDiscover topics through a filtered, top, or hot view. Filtered uses Discourse TopicsFilter syntax; top uses Discourse's authoritative top score and defaults to weekly; hot is defined exactly as daily top (not sentiment, controversy, or real-time velocity). Returns a uniform rich topic projection and truthful pagination metadata.discourse_read_topicRead topic metadata and posts. Large post limits can require multiple upstream requests. For moderation queues, prefer reviewable list/detail evidence instead of fanning this tool out across flagged topics.discourse_read_postRead a specific post. Returns JSON with id, topic_id, post_number, username, created_at, and raw content.discourse_read_topic_postsRead exact, earliest, latest, around-post, or username-filtered topic evidence. Selection is bounded to 50 posts and reports the visible stream size without claiming the entire topic was loaded.discourse_search_postsSearch post-level evidence with Discourse query syntax. Unlike discourse_search, this preserves matched posts, highlighted blurbs, authors, topics, categories, and truthful bounded continuation. This is keyword search, not Discourse AI semantic search.discourse_get_userGet user info. Returns JSON with id, username, name, trust_level, created_at, bio, admin, and moderator.discourse_list_user_postsGet paginated list of user posts/replies. Returns JSON object with posts array (id, topic_id, post_number, slug, title, created_at, excerpt, category_id) and meta (page, limit, has_more).discourse_list_usersList users via admin API. Requires admin API key. Returns ~100 users per page (Discourse's fixed page size). Returns JSON with users array and pagination meta.discourse_get_chat_messagesGet messages from a chat channel. Returns JSON object with channel_id, messages array (id, username, created_at, message, edited, thread_id, in_reply_to_id), and meta.discourse_get_draftRetrieve a specific draft by key. Returns JSON with draft_key, sequence, and parsed data (title, reply, categoryId, tags, action).- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mail7 Email Validation
{
"mcpServers": {
"mail7-email-validation": {
"command": "npx",
"args": [
"-y",
"mail7-mcp"
],
"env": {
"MAIL7_API_KEY": "YOUR_MAIL7_API_KEY_HERE",
"MAIL7_BASE_URL": "YOUR_MAIL7_BASE_URL_HERE"
}
}
}
}
Discourse MCP
{
"mcpServers": {
"discourse-discourse-mcp": {
"command": "npx",
"args": [
"-y",
"@discourse/mcp@latest"
]
}
}
}
Frequently asked questions
Mail7 Email Validation is categorized under Communication and uses a local stdio subprocess. Discourse MCP belongs to Communication and uses a local stdio subprocess. Pick Mail7 Email Validation for communication work and Discourse MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mail7 Email Validation has no declared pricing — check the project's own site. Discourse MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mail7-email-validation and discourse-discourse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mail7 Email Validation has a quality signal of 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Discourse MCP has 87/100 (Excellent) with 5 views, 0 installs and 77 GitHub stars.