Palisade MCP × Namecheap

Launch preview

Namecheap email authentication

Palisade MCP turns a Namecheap-hosted domain into a checkable workflow: inspect the live authentication state, prepare the exact record, approve it, publish through Smart DNS Deployment, and verify the public result. The current MCP server stops before the external provider write.

Connect Namecheap Run a free domain audit

1 domain free up to 1,000 emails/month

Analysis is liveHuman approval before publish

Palisade MCP

›

Find out why mail from shop.example fails DKIM alignment.

Namecheap BasicDNS detected

Selector exists; signing domain is misaligned

Sender-specific CNAME change prepared

Approval required before provider publish

Proposed recordApproval required

CNAME selector1._domainkey

selector1.sender.example.net

Host field excludes the parent domain

Illustrative workflow. Provider writes currently happen in the Palisade app.

Built for Namecheap

Provider-aware where mistakes get expensive

Detect whether Advanced DNS is actually authoritative

Namecheap exposes Host Records only for BasicDNS, FreeDNS, or PremiumDNS. Palisade does not send a change to Namecheap merely because the domain was purchased there.

Translate the Host field correctly

Namecheap expects @ for the apex and only the subdomain label for a child record. The approval diff keeps the provider field separate from the complete DNS owner name.

Respect the cache window

Namecheap documents a 30-minute default TTL for most records. Palisade distinguishes an accepted change from a globally visible answer and schedules the verification accordingly.

Current capability

What works now, and what is still a preview

The important boundary is explicit: MCP can inspect, explain, and prepare the record. The connected-provider write currently starts after approval in the Palisade app.

Audit a Namecheap-hosted domain through MCP

Reads the public authentication state and Palisade's domain evidence.

Live

Generate provider-shaped TXT and CNAME changes

Keeps Namecheap Host, Value, and TTL semantics visible in the proposal.

Live

Publish an approved record into Namecheap

The Palisade app performs the approved Smart DNS Deployment write.

App handoff

Write Namecheap DNS directly from MCP

Staged for the provider-write release; not represented as a current capability.

Preview

The governed loop

From a question in your AI client to verified DNS

01
Detect authority
Confirm which provider is actually answering for the domain before choosing a publishing path.
02
Ask Palisade
Use your MCP client to inspect the domain, its senders, and the authentication task behind the warning.
03
Review the diff
See the exact owner, record type, value, and provider-specific handling before anything changes.
04
Approve and publish
Approve in Palisade, then Smart DNS Deployment writes the record into the connected provider.
05
Verify the outcome
Recheck public DNS and the underlying SPF, DKIM, or DMARC evidence after propagation.

Provider notes

Namecheap details worth preserving in every change review

Eligible Namecheap DNS: BasicDNS, FreeDNS, or PremiumDNS must host the records.
Host field: Use @ for the apex or only the subdomain label—not the full domain.
Default TTL: Namecheap documents 30 minutes for most host records and 5 minutes for ALIAS.
Zone limit: Namecheap documents up to 800 host records for the supported managed-DNS services.

Connect from an MCP client

Add Palisade to Claude Code, then sign in when it opens your browser. The same governed workflow is available from any remote-MCP client.

Claude Code

bash

claude mcp add --transport http palisade https://api.palisade.email/mcp

See all client configurations

Division of work

Where Palisade fits beside Namecheap

CriterionNamecheapPalisade

Primary scope

Namecheap:Namecheap account and managed-DNS records

Palisade:Email-authentication remediation across the customer's DNS estate

Field handling

Namecheap:Host, Value, and TTL in Advanced DNS

Palisade:Full DNS owner mapped to Namecheap's shortened Host field

Current write path

Namecheap:Namecheap panel or provider API

Palisade:Approved Smart DNS Deployment from the Palisade app

Verification

Namecheap:Record saved in Namecheap

Palisade:Public resolution and the sender-alignment task rechecked

Questions

Namecheap MCP FAQ

Straight answers about provider authority, approval, and the current write boundary.

Is this Namecheap's official MCP server?

No. It is Palisade's email-authentication workflow for domains using Namecheap DNS. Palisade focuses on cross-provider diagnosis, approval, publishing, and verification.

Why can't Palisade find editable Namecheap records?

The domain may use third-party nameservers or Namecheap hosting nameservers. Namecheap documents editable Host Records in Advanced DNS for BasicDNS, FreeDNS, and PremiumDNS.

Should the Namecheap Host field contain the full domain?

Usually no. Namecheap documents @ for the apex and only the child label for subdomains. Palisade keeps the complete DNS owner visible while mapping it to the provider field.