Palisade MCP × Porkbun

Launch preview

Porkbun email authentication

Porkbun exposes a broad domain and DNS API, while Palisade specializes the workflow for SPF, DKIM, DMARC, BIMI, and MTA-STS. MCP prepares the exact fix; Smart DNS Deployment publishes it after approval in the app until the direct MCP provider-write path ships.

Connect Porkbun Run a free domain audit

1 domain free up to 1,000 emails/month

Analysis is liveHuman approval before publish

Palisade MCP

›

Protect the unused Porkbun domain from sending mail.

Porkbun DNS detected for parked.example

No SPF, DKIM, or DMARC policy published

No-mail SPF and reject DMARC plan prepared

Two-record changeset requires approval

Proposed recordApproval required

TXT @ "v=spf1 -all"

TXT _dmarc "v=DMARC1; p=reject"

Illustrative parked-domain policy

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

Built for Porkbun

Provider-aware where mistakes get expensive

Use the provider API without broadening the task

Porkbun's API covers registrations, renewals, DNSSEC, SSL, and more. Palisade keeps an email-authentication request scoped to the records and verification needed for that job.

Protect parked and defensive domains

A domain that never sends mail still needs an explicit posture. The workflow can distinguish a no-mail policy from an active sender migration instead of applying the same DMARC recipe to both.

Preserve a reversible changeset

The proposed DNS state stays visible before publication so a compact registrar dashboard does not become the only record of what changed and why.

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 Porkbun-hosted email-authentication DNS

Available through Palisade MCP and the public DNS evidence it retrieves.

Live

Prepare active-sender or parked-domain policies

Recommendations depend on the domain's actual sending role.

Live

Publish approved records into Porkbun

Smart DNS Deployment performs the provider write after approval.

App handoff

Call Porkbun DNS writes directly from Palisade MCP

Staged for a later provider-write tool surface.

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

Porkbun details worth preserving in every change review

Provider API: Porkbun documents a REST/JSON API for domains, DNS, DNSSEC, SSL, nameservers, and more.
DNS operations: Porkbun documents full create, read, update, and delete support for common DNS records.
DNSSEC: The Porkbun API includes DNSSEC DS-record management.
Palisade scope: Current automatic publishing is limited to approved email-authentication records.

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 Porkbun

CriterionPorkbunPalisade

Primary scope

Porkbun:Domains, renewals, DNS, DNSSEC, SSL, and hosting

Palisade:Email-authentication diagnosis and approved record deployment

Domain intent

Porkbun:Generic domain administration

Palisade:Active sender, parked domain, or defensive-registration posture

Current write path

Porkbun:Porkbun console or API

Palisade:Palisade app after a visible approval

After publication

Porkbun:Provider operation result

Palisade:Public record and email-authentication state verified

Questions

Porkbun MCP FAQ

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

Is this Porkbun's first-party MCP server?

No. Porkbun documents its own API and first-party MCP capabilities. This page describes Palisade's specialized email-authentication workflow for Porkbun-hosted DNS.

Can Palisade buy or renew Porkbun domains?

That is not part of the current Palisade provider connection described here. Palisade's present automatic publishing scope is approved email-authentication records.

Can Palisade protect a parked Porkbun domain?

Palisade can diagnose the domain and prepare an explicit no-mail SPF and DMARC posture. The owner should confirm that the domain truly has no legitimate sending path before approving it.