MxToolbox MCP integration for AI agents.
Connect AI agents to MxToolbox through 13 structured actions, including lookup bimi record, lookup blacklist, and lookup dkim. Review authentication, inputs…
- ACTION CONTRACTS
- 13
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the MxToolbox integration exposes
The MxToolbox Agent App exposes 13 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent look up the bimi record for a domain and return the official mxtoolbox response payload, check whether a domain or ip is listed on blacklists and return the official mxtoolbox response payload, and look up one dkim record and return the official mxtoolbox response payload. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected MxToolbox account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real MxToolbox capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
lookup_bimi_recordREADLook up the BIMI record for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_blacklistREADCheck whether a domain or IP is listed on blacklists and return the official MxToolbox response payload.
INPUTS: domain_or_ip
lookup_dkimREADLook up one DKIM record and return the official MxToolbox response payload.
INPUTS: domain
lookup_dmarcREADLook up the DMARC record for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_dnsREADPerform a comprehensive DNS lookup for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_httpREADRun an HTTP lookup for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_mta_sts_recordREADLook up the MTA-STS record for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_mxREADLook up MX records for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_pingREADPing a domain or IP and return the official MxToolbox response payload.
INPUTS: domain_or_ip
lookup_smtpREADRun an SMTP lookup for a domain and return the official MxToolbox response payload.
INPUTS: domain
lookup_spfREADLook up the SPF record for a domain and return the official MxToolbox response payload.
INPUTS: domain
monitor_statusREADRetrieve the current status of all monitors in the authenticated MxToolbox account.
INPUT CONTRACTS
Know what the action needs before it runs.
lookup_bimi_record
domainREQUIRED- The bare domain whose BIMI record should be looked up, such as `example.com`.
lookup_blacklist
domain_or_ipREQUIRED- The bare domain or IP address that should be checked against blacklists.
lookup_dkim
domainREQUIRED- The full DKIM DNS hostname in the form `selector._domainkey.domain`, such as `default._domainkey.example.com`.
lookup_dmarc
domainREQUIRED- The bare domain whose DMARC record should be looked up, such as `example.com`.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Lookup Bimi Record
Look up the BIMI record for a domain and return the official MxToolbox response payload. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
lookup_bimi_recordVerify with Lookup Blacklist
Check whether a domain or IP is listed on blacklists and return the official MxToolbox response payload. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
lookup_blacklistSAFETY BOUNDARY
Operate MxToolbox with explicit limits
- Authorize MxToolbox with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned MxToolbox data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in MxToolbox rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the MxToolbox task completed successfully.
CONNECTION MODEL
API key
MxToolbox API key UUID sent in the Authorization header. Find it under Settings > API in your account: https://knowledgebase.mxtoolbox.com/home/about-api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 13
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by MxToolbox.