Palisade logo

Palisade

Manage SPF, DKIM, DMARC, MTA-STS, and BIMI for domains through Palisade's MCP endpoints.

Install Palisade

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "palisade-2": {
      "command": "npx",
      "args": [
        "-y",
        "@palisadeemail/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @palisadeemail/mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

The palisade MCP server connects MCP clients to Palisade's email authentication service for monitoring and managing SPF, DKIM, DMARC, MTA-STS, and BIMI. Its package is a local stdio bridge that authenticates through Palisade's OAuth flow and forwards requests to the remote Streamable HTTP endpoint. A public endpoint provides unauthenticated DNS audits with limited tools, while organization-scoped operations require sign-in. Use it when an agent needs to inspect authentication posture, manage domains and remediation work, or review reporting through Palisade.

Use cases

  • Audit a domain's email authentication posture
  • Manage domain verification and DNS setup
  • Review DMARC aggregate data and senders
  • Track remediation tasks for authentication issues
  • Generate prospecting reports for multiple domains

Key features

  • SPF, DKIM, DMARC, MTA-STS, and BIMI monitoring
  • Organization-scoped domain management
  • Public unauthenticated DNS audits
  • DMARC summaries and sender breakdowns
  • Remediation task and webhook management
  • Prospecting reports with hosted PDF links

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

16/16 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @palisadeemail/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads899Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Palisade works

What palisade MCP server does

The palisade MCP server exposes Palisade's email authentication service to MCP-compatible clients. It covers domain-level checks and management for SPF, DKIM, DMARC, MTA-STS, and BIMI, along with related account, task, reporting, billing, webhook, group, and DNS-connection operations.

Signed-in operations apply to the organization selected during OAuth authentication. Public DNS inspection is available without a Palisade account through a separate endpoint. That public route provides audit_domain, which evaluates a domain's authentication posture, and validate_spf_include, which checks an SPF include against the ten-lookup limit.

How it works

The hosted service runs at https://api.palisade.email/mcp over Streamable HTTP. The npm package is a local stdio adapter built around mcp-remote, allowing stdio-oriented clients to connect without implementing the remote transport themselves.

Running the package opens a browser for OAuth sign-in. You choose an organization, and the bridge retains a token limited by that organization and the user's role. The authorization flow uses Palisade's public OAuth client; API keys are not accepted by the MCP endpoint. The local callback defaults to port 8765, which must be available and registered with the authorization service.

Clients that support Streamable HTTP can connect to the hosted endpoint directly. The public endpoint at /mcp/public does not open a browser or require a token, but its calls are throttled by client address. The package can be pointed at that endpoint for stdio-only clients.

Setup and configuration

For a stdio client, run:

Terminal
npx -y @palisadeemail/mcp

A typical client entry uses npx as the command and -y @palisadeemail/mcp as its arguments. Codex can register the same command with codex mcp add. Claude Code can skip the bridge and connect to the remote endpoint using HTTP, the supplied OAuth client ID, and callback port 8765.

The bridge supports three optional environment variables. PALISADE_MCP_URL changes the endpoint, PALISADE_MCP_CLIENT_ID changes the OAuth client ID, and PALISADE_MCP_CALLBACK_PORT changes the callback port. The replacement port must also be known to the authorization server. Set the URL to https://api.palisade.email/mcp/public to use only public DNS tools without authentication.

Tools and capabilities

Available operations include:

  • Inspecting accounts, domains, live DNS, SPF diagnostics, DNS records, and domain remediation plans.
  • Creating, updating, verifying, and deleting domains, groups, hosted DMARC, and MTA-STS configuration.
  • Listing, completing, and dismissing remediation tasks.
  • Reviewing DMARC aggregate summaries and sender-level source breakdowns.
  • Managing subscriptions, checkout, billing portals, webhook endpoints, webhook events, and activity logs.
  • Creating prospecting reports for up to ten domains, returning a hosted PDF link, and managing those reports.
  • Reviewing DNS provider connections and whether Palisade can publish records for a domain.

Palisade returns the DNS records to publish, but the actual changes are made at the DNS provider hosting the domain unless a supported DNS connection can publish them. Webhooks can be used instead of polling for long-running state changes. A webhook signing secret is returned only when the endpoint is created, so it must be stored at that time.

Limitations and notes

The palisade MCP server scopes organization data and write operations to the authenticated organization. audit_domain, validate_spf_include, and prospecting reports use domain names and public DNS instead of an account domain ID. Each domain in a prospecting report consumes the same live-DNS budget as an individual audit.

A connection that exposes only authenticate and complete_authentication has not completed browser sign-in. Complete the OAuth flow before expecting Palisade's tools. If another configuration with the same server name is active, inspect the effective client entry; Claude Code scope can cause a different entry to win.

API-key authentication and dynamically registered OAuth clients are refused by the MCP endpoint. Payment actions open Stripe-hosted pages, and SPF validation is constrained by the DNS protocol's ten-lookup limit.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Palisade

palisade is an MCP server that connects AI clients to Palisade's email authentication platform. Its main tools audit public DNS, manage organization domains, inspect SPF and DMARC status, configure hosted DMARC and MTA-STS, track remediation tasks, review reports, and manage related webhooks, billing, and DNS connections.

Run `npx -y @palisadeemail/mcp` and add that command to your client's stdio MCP configuration. The package acts as a local bridge to Palisade's remote Streamable HTTP service and starts the browser-based OAuth sign-in when authenticated tools are used.

Yes, palisade can be used with Cursor through its standard stdio MCP configuration. Configure the client to run `npx` with `-y @palisadeemail/mcp`; the bridge handles the connection to Palisade's remote endpoint.

Yes, use `https://api.palisade.email/mcp/public` without signing in. This endpoint provides `audit_domain` and `validate_spf_include`, which read public DNS for any domain; organization records and management operations remain on the authenticated endpoint.

Complete the browser OAuth sign-in first. A session showing only `authenticate` and `complete_authentication` is still waiting for authentication, or another same-named MCP configuration may be taking precedence. In Claude Code, `claude mcp get palisade` shows the effective entry.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPalisade AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/palisade-2?style=directory)](https://allmcps.com/mcp/palisade-2)
HTML Embed
<a href="https://allmcps.com/mcp/palisade-2"><img src="https://allmcps.com/api/badge/palisade-2?style=directory" alt="Palisade on AllMCPs" /></a>