MXToolbox
MxToolbox provides a suite of network diagnostic and monitoring tools, including DNS lookups, blacklist checks, and email health analysis.
Verdict
Common use cases
- Diagnose email deliverability failures during outages
- Audit domain security posture before launch
- Verify DNS propagation after migration cutover
- Triage blacklist reports from customers
- Validate DMARC policy changes in staging
Integration
- Vendor
- MXToolbox
- Category
- other
- Auth
- API_KEY
- Tools
- 13
- Composio slug
mx_toolbox
Tools
- Check Usage
Tool to retrieve api usage statistics. use when you need to monitor remaining api calls and quota reset timing.
- HTTP Lookup
Tool to perform an http test on a domain. use when you need to assess http connectivity and status for a given domain.
- Lookup BIMI Record
Tool to retrieve bimi (brand indicators for message identification) record for a domain. use when checking domain brand identity via bimi lookup.
- Lookup Blacklist
Tool to perform a blacklist check on a domain or ip. use when you need to verify whether a domain or ip is listed in common blacklists.
- Lookup DKIM Record
Tool to retrieve dkim records for a domain. use when verifying dkim configuration before sending email.
- Lookup DMARC Record
Tool to retrieve dmarc records for a domain. use after confirming the domain is correctly formatted.
- Lookup DNS Records
Tool to retrieve dns records for a given domain. use when you need dns lookup details.
- Lookup MTA-STS Record
Tool to lookup mta-sts record for a domain. use when validating mail transport security policy.
- Lookup MX Records
Tool to retrieve mx records for a given domain. use when you need to discover mail exchange servers after obtaining a domain.
- Lookup SPF Record
Tool to retrieve spf records for a specified domain. use when confirming email sender authorization policies.
- Monitor Status
Tool to retrieve all monitor statuses. use when you need to get current health details of all account monitors.
- Ping Lookup
Tool to perform a ping test on a specified domain or ip address. use when you need hop-by-hop network latency diagnostics.
- SMTP Lookup
Tool to perform an smtp test on the specified domain. use when verifying smtp connectivity for a domain.
Setup
Setup guide
- 1Click the MCP tab in your Switchy workspace settings and select MXToolbox from the catalog. Choose API Key authentication when prompted. Log into your MXToolbox account, navigate to API Settings, and generate a new key with read permissions for DNS and blacklist lookups. Paste the key into Switchy and click Connect. Open any Space and type '@MXToolbox check usage' to confirm the connection works — you should see your current quota and reset time. To invoke a tool, @mention MXToolbox followed by your request (e.g. '@MXToolbox lookup blacklist for 203.0.113.5'). The MCP will parse your intent, call the appropriate tool, and return results inline. If you hit rate limits, the response will show your reset window.
What teammates see: by default, memories from MXToolbox are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Blacklist Check
@MXToolbox lookup blacklist for mail.example.com and summarize any listings found with remediation stepsOpen in a Space →
DMARC Validation
@MXToolbox lookup dmarc record for example.com and explain any policy gaps or syntax errorsOpen in a Space →
DNS Record Audit
@MXToolbox lookup dns records for example.com and highlight any missing or misconfigured entriesOpen in a Space →
HTTP Endpoint Test
@MXToolbox http lookup for https://api.example.com and report response time and any certificate warningsOpen in a Space →
DKIM Verification
@MXToolbox lookup dkim record for selector1._domainkey.example.com and confirm it matches our current keyOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@MXToolbox check if our domain example.com is on any blacklists and show me the DMARC policy
Blacklist check for example.com shows clean across 87 monitored lists — no listings found on Spamhaus, Barracuda, or SORBS. DMARC record retrieved: 'v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com' — policy is set to quarantine suspicious messages with aggregate reports enabled. This illustrative example shows how the MCP combines multiple DNS security checks in a single query.
This example demonstrates read-heavy lookups combining blacklist monitoring with email authentication policy checks. Requires API key with sufficient quota — blacklist checks consume multiple API calls per domain (one per list checked). Results reflect point-in-time status; blacklist inclusion can change hourly.
@MXToolbox verify DKIM and SPF records for newdomain.io before we start sending customer emails
DKIM lookup for newdomain.io returns no valid records found — you'll need to publish a DKIM selector before sending authenticated mail. SPF record retrieved: 'v=spf1 include:_spf.google.com ~all' — configured for Google Workspace with soft fail policy. This illustrative response shows pre-send validation catching missing authentication that would hurt deliverability.
This example showcases proactive email authentication verification before launching campaigns. Catches configuration gaps early — missing DKIM or weak SPF policies directly impact inbox placement rates. Each DNS lookup counts against your MXToolbox API quota; monitor usage via the Check Usage tool.
@MXToolbox run a full email security audit on clientdomain.com and summarize what needs fixing
Audit complete for clientdomain.com. Critical findings: (1) DMARC policy set to 'p=none' — monitoring only, not enforcing. (2) MTA-STS record missing — no transport security policy published. (3) BIMI record not found — brand logo won't display in supported email clients. Positive: DKIM properly configured, blacklist status clean. This illustrative summary shows the AI synthesizing multiple MXToolbox lookups into prioritized remediation steps.
This example pairs the MCP's DNS lookup tools with AI reasoning to deliver actionable security posture analysis. Executes 5-7 API calls in sequence (DMARC, DKIM, SPF, MTA-STS, BIMI, blacklist checks). Useful for onboarding new domains or quarterly audits — but watch quota limits on bulk assessments.
Use-case deep-dives
When MXToolbox saves your outbound email reputation
A 6-person SaaS startup notices their onboarding emails landing in spam. The support lead needs to audit SPF, DKIM, and DMARC records without waiting on engineering. MXToolbox is the right call here: the Lookup DKIM Record, Lookup DMARC Record, and Lookup Blacklist tools let non-technical teammates diagnose misconfiguration in minutes. The Check Usage tool keeps you honest about API limits if you're running daily checks. This MCP stops being useful once you need continuous monitoring or alerting—at that scale, you want a dedicated email-ops platform. For one-off audits or quarterly hygiene checks, MXToolbox gives your team the DNS literacy to fix deliverability without opening a DevOps ticket.
Blacklist checks during a phishing scare
A 12-person agency gets a client complaint that their domain is flagged as suspicious. The account manager needs to confirm whether the domain or IP is actually blacklisted before escalating to IT. The Lookup Blacklist tool checks common blocklists in one call, and the Lookup DNS Records tool surfaces any hijacked subdomains. MXToolbox works well here because the scenario is reactive and infrequent—you're not running these checks hourly. If your team handles security incidents weekly or needs automated threat feeds, this MCP is too manual. For ad-hoc "are we compromised" questions during a fire drill, MXToolbox gives non-engineers the forensic data to triage fast.
Auditing a new domain before go-live
A 4-person product team is launching a new marketing site on a fresh domain. Before flipping DNS, they need to verify HTTP connectivity, MTA-STS policy, and BIMI branding records. The HTTP Lookup, Lookup MTA-STS Record, and Lookup BIMI Record tools let the PM run a pre-flight checklist without SSH access or command-line tools. MXToolbox is ideal for this one-time validation—13 tools cover the full DNS and email stack. It stops being the right choice if you're launching domains monthly and need CI/CD integration. For teams that ship a new domain twice a year and want a human-readable audit trail, MXToolbox turns launch-day paranoia into a 10-minute checklist.
Frequently asked
What does the MXToolbox MCP do in Switchy?
It runs email deliverability and DNS diagnostics directly in your workspace. Your team can check blacklist status, validate SPF/DKIM/DMARC records, test HTTP connectivity, and pull DNS lookups without leaving Switchy. Think of it as MXToolbox's command-line tools embedded in your AI chat—useful when troubleshooting email bounces or auditing domain security before a campaign goes live.
Do I need an MXToolbox account to use this MCP?
Yes. You need an active MXToolbox subscription and an API key. The MCP calls MXToolbox's paid API, so free-tier users won't have access. Whoever connects the integration should grab the API key from their MXToolbox account settings and paste it into Switchy's auth flow. The key stays scoped to that user's quota, so monitor usage via the Check Usage tool if you're on a metered plan.
Can the MXToolbox MCP fix DNS records or update DMARC policies?
No. It's read-only. The MCP retrieves and validates records—blacklist checks, DKIM lookups, BIMI queries—but it can't write changes back to your DNS provider or email server. If you find a misconfigured DMARC policy, you'll still need to log into your DNS host (Cloudflare, Route 53, etc.) to edit the TXT record. Use this MCP for diagnosis, not remediation.
How is this different from just using MXToolbox's website?
Speed and context. Instead of copy-pasting domains into MXToolbox's web UI and switching tabs, you ask Switchy to run the checks inline. The AI can chain lookups—check blacklist status, then pull DMARC, then validate DKIM—and summarise results in one response. You lose the visual dashboard MXToolbox's site offers, but you gain workflow continuity when you're already troubleshooting in Switchy.
Does MXToolbox MCP usage count against my Switchy plan limits?
No. Switchy doesn't meter MCP tool calls separately. However, every lookup hits MXToolbox's API and counts against your MXToolbox subscription quota. If you're on a plan with 500 API calls per month, running 20 blacklist checks in Switchy burns 20 of those calls. Use the Check Usage tool to track your remaining quota so you don't hit rate limits mid-investigation.