email.palisade/palisade MCP server
Checked 2026-09-07. Alive: yes. Handshake: gated.
Category: security. API and field schema.
Facts
| id | palisadeemail--palisade-mcp |
| name | email.palisade/palisade |
| registry_name | email.palisade/palisade |
| repo_url | https://github.com/palisadeemail/palisade-mcp |
| endpoint_url | https://api.palisade.email/mcp |
| transport | mixed |
| alive | yes |
| liveness_reason | not available |
| check_reachable | yes |
| check_recent_commit | yes |
| check_installable | yes |
| handshake_status | gated |
| handshake_checked_at | 2026-09-07T18:09:20Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | Bearer resource_metadata="https://api.palisade.email/.well-known/oauth-protected-resource" |
| handshake_auth_discoverable | resource_metadata |
| handshake_failure_layer | none |
| handshake_latency_ms | 2202 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | active |
| last_commit_at | 2026-09-04T16:20:06Z |
| category | security |
| license_spdx | MIT |
How to install or connect
Connect your MCP client to https://api.palisade.email/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.