Mx toolbox MCP integration

No. Every action in the connected toolkit is diagnostic: Monitor Status reads the health of monitors that already exist, and the remaining twelve are lookups and connectivity tests. Setting up or editing a monitor stays in MxToolbox, and Ayro reports on what is configured there.

Yes, they run on the API key you connect and draw from that account's quota. Check Usage returns the current request counts, the maximum allowed, and any overage errors separately for DNS lookups and for network operations such as HTTP, SMTP, and ping, so you can see exactly what has been consumed.

Most of the toolkit is public DNS resolution, so blacklist, MX, SPF, DKIM, DMARC, BIMI, and ping checks work on any domain a customer names in the conversation. Monitor Status is the exception - it only returns monitors configured in the account whose key is connected.

The web tool answers one lookup at a time and needs someone at a keyboard. Ayro runs the sequence a diagnosis actually calls for - blacklist, then MX, then SMTP - inside the conversation where the complaint arrived, and hands off to a human agent with those results attached when the fix is a configuration change.