3 findingsStatic scanned
Palisadeemail MCP
palisadeemail · MCP server
Palisade Email Authentication monitors and manages SPF, DKIM, DMARC, MTA-STS and BIMI for your domains, and this package connects your AI assistant to it through a local bridge. Your agent can audit any domain, check what an SPF include costs against the 10-lookup limit, read DMARC summaries and senders, see where a domain stands in the DMARC journey and work through remediation tasks. Palisade tells you which DNS records to publish, and you apply them at your own DNS provider.
Written by ooruby from the README of @palisadeemail/mcp 0.2.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You can ask your agent about the email authentication of your domains and get the exact DNS records to publish at your provider.
What you could do with it
- Audit the email authentication of any domain, even one not in your account, and get its posture scored.
- Check what adding an SPF include would cost against the 10-lookup limit before you publish it.
- Create a prospecting report that audits up to ten domains and returns a hosted PDF link to send a prospect.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (bin/cli.js:10)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Local stdio bridge to the Palisade MCP server (email authentication: SPF, DKIM, DMARC, MTA-STS, BIMI).
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.2.1, the file with digest sha512-SjbpBeeX/unm4OGDUK7CWp/wn74NcWSR+NgOhBZzV/kbxF2uXlLAx63dQLiLd6hnB9s2afErChrnJip72Y1Xqg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- No auth declared. Its hosted endpoint, as the official MCP registry lists it, does not say it asks for a key. That is what the listing declares, not a finding that it has no protection.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"palisade-mcp": {
"command": "npx",
"args": [
"-y",
"@palisadeemail/mcp@0.2.1"
]
}
}
}Or run it directly.
npx -y @palisadeemail/mcp@0.2.1Pinned to 0.2.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @palisadeemail/mcp
- Version read
- 0.2.1
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/palisadeemail-mcp)About this listing
- Kind
- MCP server
- Category
- Infrastructure
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.