What Zactonz MCP server does
The Zactonz MCP server connects an MCP-compatible AI client to the Zactonz APIs. It provides tools for capturing web pages, rendering supplied HTML, extracting page content as Markdown, and retrieving link metadata such as a title, description, image, and other URL information.
Its domain and email tools cover DNS records and DNSSEC status, TLS certificate details, WHOIS data, and email-domain records including MX, SPF, DKIM, and DMARC. It can also assess whether email addresses can receive mail. Other tools generate or decode QR codes, generate barcodes and Open Graph images, process images, translate text between 46 languages, create direct Google Drive download links, and report an API key's plan and remaining quota.
How it works
The Zactonz MCP server runs on the user's machine and communicates with the MCP client over standard input and output. The package can be started with npx -y @zactonz/mcp, or launched from a cloned repository with Node.js. No build step is required for the source installation described in the repository.
Each API key belongs to one Zactonz product. The server reads all supplied keys, chooses the key associated with the requested tool, and exposes only the tools those keys can call. Requests are sent to api.zactonz.com using the key in an authorization header; the keys are not included in results returned to the assistant.
Tool results are returned as JSON text. Markdown tools place the extracted or converted Markdown before the remaining JSON fields and request no more than 20,000 characters unless more is requested. Image-producing tools return a link and may include the image inline when it is no larger than the configured inline-image limit. PDFs and larger images are returned as links.
Setup and configuration
Create keys in the Zactonz API console, then add the server to an MCP client configuration. Put the comma-separated keys in ZACTONZ_API_KEYS. The default package configuration uses npx; source-based setups instead point the client to bin/zactonz-mcp.js with an absolute path. Node.js 18 or newer is required.
ZACTONZ_BASE_URL can replace the default API endpoint, and ZACTONZ_MCP_INLINE_IMAGE_BYTES controls the largest image returned inline. Setting the latter to 0 makes image results link-only. The server can start without keys, but calls then return setup instructions rather than making API requests.
Tools and capabilities
Available operations include:
- Capture screenshots or PDFs and render HTML as images or PDFs.
- Read webpages and convert HTML into Markdown.
- Preview links and inspect DNS, DNSSEC, SSL certificates, and WHOIS data.
- Score email-domain configuration and verify whether addresses can receive mail.
- Generate or decode QR codes, generate barcodes, and create social images.
- Convert, resize, crop, and inspect images.
- Translate text, obtain Google Drive download links, and inspect API-key quota.
Limitations and notes
Calls consume units from the relevant Zactonz plan quota. The server gives each call up to 55 seconds and may retry certain rate-limit or gateway failures once. Returned page text, link previews, and QR contents are untrusted third-party data and may contain instructions aimed at an assistant.
Generated screenshots, PDFs, QR codes, barcodes, and converted images are stored at public, unguessable links on api.zactonz.com for the period specified by the relevant endpoint. Do not use these tools for documents that must remain private. The Zactonz MCP server also depends on having the correct product key; an unrelated or invalid key is ignored and reported on stderr.