Contact forms that actually arrive. No SPF/DKIM, no SMTP. AI sorts them and drafts the reply.
A contact form you paste in one line. An AI that sorts what comes in and drafts the reply. Delivery that needs no DNS work.
This repository holds the two published packages. The hosted service lives at nintact.com.
| Package | What it is |
|---|---|
nintact-mcp | MCP server — 32 tools. Build forms, read the inbox, approve replies from your editor. |
nintact | JavaScript client, React component, and CLI. |
A site built with an AI assistant usually works until the contact form. Then the mail silently stops. Gmail and Yahoo! reject mail from a domain with no SPF/DKIM, and whoever built the site finds out weeks later — from the customer who never got an answer.
The usual fixes all end at the same wall: an SMTP plugin still needs a domain you have authenticated, and authenticating a domain means DNS records the person often cannot edit.
nintact sends over an already-authenticated domain, with Reply-To pointing at your own address.
Replies reach you without touching DNS, SMTP, or a mail provider.
npx nintact-mcp login # 6-digit code by email; the key is stored, not pasted
claude mcp add nintact -- npx -y nintact-mcp
Then ask your assistant to build the form.
No account yet? check_deliverability works without a key — it reads public DNS and tells you
whether a domain can actually get mail delivered.
curl https://nintact.com/api/v1/check?domain=example.com
https://nintact.com/llms.txt — one screen, enough to installhttps://nintact.com/llms-full.txt — the full APInpm install
npm run build
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y nintact-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-nintact-nintact": {
"command": "npx",
"args": [
"-y",
"nintact-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencenintact-mcpnpmnintact works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.