ZenMode
REMOTE · WWW.ZEN-MODE.IO
Read LinkedIn outreach campaigns, contacts and replies, and manage campaign leads and targeting.
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 →
No category breakdown is available for this channel yet.
How do I install the ZenMode MCP server?
ZenMode is a hosted endpoint at https://www.zen-mode.io/api/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 · www.zen-mode.io
claude mcp add --transport http zenmode87-zenmode 'https://www.zen-mode.io/api/mcp'
{
"mcpServers": {
"zenmode87-zenmode": {
"url": "https://www.zen-mode.io/api/mcp"
}
}
} {
"servers": {
"zenmode87-zenmode": {
"type": "http",
"url": "https://www.zen-mode.io/api/mcp"
}
}
} [mcp_servers.zenmode87-zenmode] url = "https://www.zen-mode.io/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zenmode87-zenmode": {
"type": "remote",
"url": "https://www.zen-mode.io/api/mcp",
"enabled": true
}
}
} openclaw mcp add zenmode87-zenmode --url 'https://www.zen-mode.io/api/mcp' --transport streamable-http
mcp_servers:
zenmode87-zenmode:
url: "https://www.zen-mode.io/api/mcp" {
"McpServers": {
"zenmode87-zenmode": {
"Transport": "http",
"Url": "https://www.zen-mode.io/api/mcp"
}
}
} assistant mcp add zenmode87-zenmode -t streamable-http -u 'https://www.zen-mode.io/api/mcp'
{
"mcpServers": {
"zenmode87-zenmode": {
"type": "http",
"url": "https://www.zen-mode.io/api/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.
We have not recorded any changes for this component yet
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 8 Oct 2026 · Probed https://www.zen-mode.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.zen-mode.io | CN=YR2,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 543f7b8142936f7f4a09434bafe77647478 |
| SANs: www.zen-mode.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.zen-mode.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| zen-mode.io. | present | 2371 | 13 | Verified |
| www.zen-mode.io. | Verified address RRset verified with the apex keys |
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://www.zen-mode.io/.well-known/oauth-protected-resource/api/mcp"
Bearer resource_metadata="https://www.zen-mode.io/.well-known/oauth-protected-resource/api/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer resource_metadata="https://www.zen-mode.io/.well-known/oauth-protected-resource/api/mcp" |
Protected resource metadata
| Document | https://www.zen-mode.io/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.zen-mode.io/api/mcp |
| Authorisation server | https://www.zen-mode.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.zen-mode.io/api/mcp | Auth required | 401 | |
| http (plaintext) | http://www.zen-mode.io/api/mcp | HTTPS enforced | 308 | https://www.zen-mode.io/api/mcp |
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.