MxToolbox provides a suite of network diagnostic and monitoring tools, including DNS lookups, blacklist checks, and email health analysis.
MxToolbox provides a suite of network diagnostic and monitoring tools, including DNS lookups, blacklist checks, and email health analysis. On Nagent, MXToolbox is exposed as a fully-configurable server monitoring integration that any agent can call — 13 actions, and API key authentication. No code is required to wire MXToolbox into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use MXToolbox to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire MXToolbox into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against MXToolbox, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MX_TOOLBOX_LOOKUP_BIMI_RECORDRetrieves BIMI (Brand Indicators for Message Identification) record and diagnostic information for a domain. BIMI allows organizations to display verified logos in email clients. This tool checks: - Whether a BIMI record exists at default._bimi.{domain} - DMARC policy requirements (quarantine or reject needed for BIMI) - DNS resolution details and nameserver information - Related diagnostic checks and recommendations Returns comprehensive lookup data including passed/failed checks, DMARC records, DNS transcript, and related lookups. Use when verifying email branding configuration or troubleshooting BIMI implementation.
Input parameters
The domain to perform BIMI lookup on (e.g., 'example.com', 'google.com').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_BLACKLISTTool 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.
Input parameters
The domain name or IP address to lookup in blacklists Must be a bare hostname or IP address without protocol prefixes (e.g., no 'http://') or path suffixes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_DKIMTool to retrieve DKIM (DomainKeys Identified Mail) records for a domain. DKIM is an email authentication method that helps prevent email spoofing by allowing the receiver to verify that an email was actually sent and authorized by the owner of that domain. Use this tool to verify DKIM configuration and troubleshoot email authentication issues.
Input parameters
DKIM record name in DNS format: 'selector._domainkey.domain' (e.g., 'google._domainkey.google.com' where 'google' is the selector). This is the full DNS hostname for the DKIM TXT record. Common selectors include 'default', 'google', 'k1', 's1', 's2', or 'email'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_DMARCRetrieves DMARC (Domain-based Message Authentication, Reporting & Conformance) records for a domain and performs validation checks. Returns detailed information about the DMARC record including policy settings (reject/quarantine/none), reporting addresses, alignment modes, and diagnostic check results. Useful for verifying email authentication configuration and troubleshooting email delivery issues.
Input parameters
The domain to lookup DMARC record for. Must be a bare hostname (e.g., 'example.com') without protocol prefixes ('https://') or path components.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_DNSPerforms comprehensive DNS health check and retrieves name server records for a domain. Returns detailed diagnostics including: - Name server (NS) records with IP addresses, TTL, and status - DNS configuration health checks (warnings, errors, passed tests) - Query transcripts showing DNS resolution path - Related lookup suggestions (A, MX, SPF records) Use this to diagnose DNS issues, verify name server configurations, or check DNS propagation status.
Input parameters
Domain to perform DNS lookup on, for example 'google.com' Bare hostname only — no protocols (e.g., 'http://'), subpath, or trailing slashes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_HTTPTool to perform an HTTP test on a domain. Use when you need to assess HTTP connectivity and status for a given domain.
Input parameters
The domain to perform HTTP diagnostics on (e.g., 'example.com'). Do not include protocol or paths.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_MTA_STS_RECORDTool to lookup MTA-STS record for a domain. Use when validating mail transport security policy.
Input parameters
The domain to perform MTA-STS lookup on.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_MXRetrieves MX (Mail Exchange) records for a domain. Returns the mail servers responsible for receiving email for the domain, including their priority, hostname, IP address, and TTL. Use this to discover and verify email infrastructure for any domain.
Input parameters
Domain name to lookup MX records for (e.g., example.com) Bare hostname only — no protocol prefix (e.g., not 'http://example.com') or path suffix.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_PINGPerforms a ping test to check network connectivity and measure round-trip time to a domain or IP address. Returns detailed ping statistics including response time, TTL (Time-To-Live), packet size, and ASN (Autonomous System Number) information. Useful for diagnosing network connectivity issues, measuring latency, and verifying host availability.
Input parameters
The domain name or IP address to ping (e.g., 'google.com' or '8.8.8.8').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_SMTPTool to perform an SMTP connectivity test on a domain. Returns diagnostic results including connection status, DNS checks, TLS support, and other email deliverability indicators. Use when verifying SMTP server configuration or troubleshooting email delivery issues for a domain.
Input parameters
Domain to perform SMTP test on (must be a valid hostname, e.g. 'google.com')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_LOOKUP_SPFTool to retrieve SPF records for a specified domain. Use when confirming email sender authorization policies.
Input parameters
The domain to perform the SPF lookup on. Must be a bare hostname with no protocol prefix (e.g., not 'https://example.com') or path suffixes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_MONITOR_STATUSRetrieves the current status of all monitors configured in the MX Toolbox account. This action returns a list of all monitors with their health status, last check time, reputation scores, and any failing checks or warnings. Use this when you need to: - Check the overall health of all configured monitors - Get a comprehensive view of monitoring status across all services - Identify which monitors are failing or have warnings - Review when monitors were last checked No parameters are required - this action retrieves all monitors for the authenticated account. Returns an empty list if no monitors are configured.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MX_TOOLBOX_USAGE_CHECKRetrieve API usage statistics for DNS and network lookups. Returns current request counts, maximum allowed requests, and any overage errors for both DNS lookups and network operations (HTTP, SMTP, Ping).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 33 agents privately built on Nagent that already use MXToolbox.
Build on Nagent
Connect MXToolbox to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find MXToolbox, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, MXToolbox is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once MXToolbox is connected, you configure its 13 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop MXToolbox steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a MXToolbox event fires, the agent kicks off automatically.
Every MXToolbox action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While MXToolbox ships with 13 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching MXToolbox together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build MXToolbox-based workflows tailored to your business.