
nintact
com.nintactPublished by nintact.comv0.5.2Updated Oct 24, 2026
Contact forms that actually arrive. No SPF/DKIM, no SMTP. AI sorts them and drafts the reply.
The publisher's own server: Ganty MCP
Overview
Local MCP server for nintact contact forms: an assistant can build forms, read submissions, and approve AI-drafted replies from the editor.
- What you can do
- Diagnose whether a domain can receive mail by reading public DNS records and returning a verdict with a next step. Design, create, list, get, update, duplicate and delete contact forms, and set or remove a form logo. Read the inbox, open messages and change their status. Regenerate, edit and approve AI-drafted replies. Manage the knowledge used to ground drafts, including scanning a site for it. Manage workspace settings, usage, inbound addresses and a custom sending domain.
- When to use it
- Useful when a site built with an AI assistant needs a working contact form without DNS, SMTP or mail-provider setup, and you want the assistant to create the form, triage incoming messages and prepare replies. Also handy for checking, before signup, whether a domain's mail will be delivered.
- Requirements
- Runs locally over stdio via npx, so Node.js is needed. Most tools need a nintact account and an API key, supplied as NINTACT_API_KEY or created with the login command, which stores it in a local config file. The deliverability check works without an account. Desktop MCP clients only; ChatGPT connectors cannot run a local server.
Installation
In SourceWeft
- Open nintact in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
nintact-mcp
MCP server for nintact — a contact form you paste in one line, an AI that sorts what comes in and drafts the reply, and delivery that needs no DNS work.
Build the form, read the inbox, and approve replies without leaving your editor.
Why this exists
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 the person who built the site finds out weeks later, from the customer who never got an answer.
nintact sends over an already-authenticated domain with Reply-To pointing at your own address,
so replies reach you without you touching DNS, SMTP, or a mail provider.
Install
login writes the key to ~/.nintact/config.json (0600). Passing it on the command line also
works and is what CI wants:
Prefer login on a person's own machine — a key typed into a command ends up in shell history
and in the client's config file in plaintext.
No claude on PATH?
The desktop app alone does not install the CLI. Add this at the top level of ~/.claude.json.
A session that is already open will not pick it up; open a new one.
Any MCP client works — Cursor, Codex CLI, Claude Desktop. ChatGPT itself cannot: its connectors only accept a server published over HTTPS, not one run locally.
Works without an account
check_deliverability needs no API key. It reads public DNS and tells you whether a domain can
actually get mail delivered — which is usually the question, before anyone has signed up for
anything.
Tools
32 tools covering the same surface as the REST API. No screen-only features.
Every error carries a next_step field describing how to recover, so an agent can fix its own
mistake instead of giving up on the tool.
Things worth knowing before you point this at someone's account
approve_draftsends a real email. Confirm with the person first. nintact never sends without an explicit approval, and neither should you.- Call
get_organization(or the API'sGET /me) first. It returns the workspace name and how many forms already exist. If that count is not zero, reuse a form instead of adding one — inquiries split across two forms land in two places, and the owner only watches one. - Notifications are held until the address confirms. Setting
notify_emailsemails a confirmation link to each address. Until someone opens it, submissions are stored and visible in the dashboard but no notification goes out. Tell the owner to check their mail. - AI can be switched off per form.
update_formwithmode: "relay"forwards everything untouched — no classification, no draft, nothing sent to a model.
Verifying an install without creating a real inquiry
Everything is checked as in a real submission, then nothing is stored and nobody is notified.
200 with {"data":{"ok":true,...}} means the install is correct. Use this instead of sending a
real submission to someone else's inbox.
Docs
https://nintact.com/llms.txt— one screen, enough to installhttps://nintact.com/llms-full.txt— the full API- npm:
nintact(client + CLI),nintact-mcp
License
MIT
Source: packages/nintact-mcp/README.md at commit 9f3902f
Tools
0Version history
2- v0.5.2LatestSep 18, 2026
- v0.3.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts