Palisade
REMOTE · API.PALISADE.EMAIL · 2 COMPONENTS · SCANNED SEP 20
Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Palisade MCP server?
Palisade is a hosted endpoint at https://api.palisade.email/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.palisade.email
claude mcp add --transport http email-palisade-palisade 'https://api.palisade.email/mcp'
{
"mcpServers": {
"email-palisade-palisade": {
"url": "https://api.palisade.email/mcp"
}
}
} {
"servers": {
"email-palisade-palisade": {
"type": "http",
"url": "https://api.palisade.email/mcp"
}
}
} [mcp_servers.email-palisade-palisade] url = "https://api.palisade.email/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"email-palisade-palisade": {
"type": "remote",
"url": "https://api.palisade.email/mcp",
"enabled": true
}
}
} openclaw mcp add email-palisade-palisade --url 'https://api.palisade.email/mcp' --transport streamable-http
mcp_servers:
email-palisade-palisade:
url: "https://api.palisade.email/mcp" {
"McpServers": {
"email-palisade-palisade": {
"Transport": "http",
"Url": "https://api.palisade.email/mcp"
}
}
} assistant mcp add email-palisade-palisade -t streamable-http -u 'https://api.palisade.email/mcp'
{
"mcpServers": {
"email-palisade-palisade": {
"type": "http",
"url": "https://api.palisade.email/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
- Authorization: partial → pass ▲ security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.palisade.email/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.palisade.email | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 11 Feb 2026 | 12 Mar 2027 | RSA 2048 | SHA256-RSA | 10378db9bfa57dca3446dc79dd661ce |
| SANs: api.palisade.email | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.palisade.email. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| email. | present | 62422 | 8 | Verified |
| palisade.email. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.palisade.email/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.palisade.email/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| www-authenticate | Bearer resource_metadata="https://api.palisade.email/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.palisade.email/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.palisade.email/mcp |
| Authorisation server | https://accounts.palisade.email/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.palisade.email/mcp | Auth required | 401 | |
| http (plaintext) | http://api.palisade.email/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
What is the Palisade MCP server?
Palisade is an MCP server listed in the public MCP registry as email.palisade/palisade. Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains. This page covers its hosted endpoint (https://api.palisade.email/mcp).
Is the Palisade MCP server safe to use?
Palisade scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the Palisade MCP server require authentication?
Yes. Palisade asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Palisade MCP server still maintained?
Palisade is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.