
SentinelOne (Purple)
io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.0.11Updated Nov 14, 2026
Multitenant Streamable HTTP wrapper for the SentinelOne purple-mcp server.
Overview
Multitenant HTTP wrapper that exposes the SentinelOne purple-mcp server to a gateway, passing per-tenant SentinelOne credentials from request headers.
- What you can do
- Serve the upstream SentinelOne purple-mcp tools over a single Streamable HTTP endpoint (POST /mcp)
- Accept per-request SentinelOne API token and console URL headers and route each tenant to its own lazily spawned child process
- Verify a service-to-service HMAC proof header before reading tenant credentials
- Report liveness on an unauthenticated health endpoint
- Evict idle tenant processes after a configurable timeout and cap concurrent tenants
- When to use it
- Intended for operators running a multi-tenant MCP gateway that must forward each organization's SentinelOne console credentials as HTTP headers to one shared container, rather than running a separate single-tenant purple-mcp instance per tenant.
- Requirements
- Runs as a local container image (stdio transport declared, but the proxy listens on HTTP). Requires CONDUIT_S2S_SECRET to start, plus per-request headers X-Gateway-S2S, X-S1-API-Token and X-S1-Console-URL (legacy x-purplemcp-* aliases accepted). Optional tuning via PORT, MCP_HTTP_HOST, IDLE_EVICT_MS, SPAWN_READY_TIMEOUT_MS, MAX_CHILDREN, LOG_LEVEL.
Installation
In SourceWeft
- Open SentinelOne (Purple) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
sentinelone-mcp
Multitenant Streamable HTTP wrapper for sentinel-one/purple-mcp, built so the wyre-technology MCP gateway can forward per-tenant SentinelOne credentials as HTTP headers.
Why
purple-mcp is a great first-party MCP server, but it reads its SentinelOne console token + URL from environment variables at process startup, which makes it single-tenant per container. Our gateway is multi-tenant: every request carries the calling org's credentials as HTTP headers, and the vendor container has to translate those headers into something the upstream understands.
This image bundles purple-mcp plus a small Node/Fastify proxy. The proxy:
- Listens on
:8080withPOST /mcpandGET /health. - Requires a valid
X-Gateway-S2Sproof, then readsX-S1-API-TokenandX-S1-Console-URLfrom that request (legacyx-purplemcp-token/x-purplemcp-base-urlstill accepted). A request missing either the token or the console URL, after per-field fallback, gets 401, which Conduit's vendor-monitor treats as reachable but auth-gated. There is no fallback toPURPLEMCP_CONSOLE_*in the environment. - Lazily spawns one
purple-mcp --mode streamable-httpchild per(token, base-url)tenant on a private loopback port, with the right env vars set. - Proxies the request body to that child and streams the response back.
- Evicts idle children after 60 minutes (
IDLE_EVICT_MS).
The result is a single container that the gateway can talk to like any other vendor MCP server.
Configuration
Copy .env.example. Leave CONDUIT_S2S_SECRET empty in that file; put a real value only in an uncommitted .env or the process environment.
Request headers
This server is gateway mode. It does not read PURPLEMCP_CONSOLE_TOKEN or PURPLEMCP_CONSOLE_BASE_URL from the environment for an incoming request. The gateway must forward these headers on every /mcp request. Names are case-insensitive. When both pairs are present, the X-S1-* value wins per field.
Console URLs from X-S1-Console-URL or x-purplemcp-base-url have surrounding whitespace and trailing slashes stripped before being passed to purple-mcp.
X-Gateway-S2S
With CONDUIT_S2S_SECRET set, every POST /mcp must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before tenant credentials are read, and the secret is not logged.
In gateway mode, /mcp also requires X-S1-API-Token and X-S1-Console-URL (or the legacy x-purplemcp-* pair, including a mixed pair). A request missing either credential is HTTP 401 (JSON-RPC -32001) and does not fall back to PURPLEMCP_CONSOLE_* in the process environment. Vendor-monitor's credless initialize probe relies on that: 401/403 means the sidecar is up but auth-gated, while 400 marks the slug DOWN.
GET /health stays unauthenticated and does not read credentials.
Build
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and refuses to start until CONDUIT_S2S_SECRET is set. Publish the port on loopback. SentinelOne credentials arrive on each request as headers; they are not read from the environment.
Compose refuses to start when CONDUIT_S2S_SECRET is unset, publishes 127.0.0.1:8080:8080, and does not inject PURPLEMCP_CONSOLE_TOKEN or PURPLEMCP_CONSOLE_BASE_URL:
Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) makes startup exit:
License
Apache-2.0. The bundled purple-mcp is MIT-licensed by SentinelOne.
Source: README.md at commit b5540c4
Tools
0Version history
5- v1.0.11LatestNov 14, 2026
- v1.0.10Nov 11, 2026
- v1.0.9Oct 14, 2026
- v1.0.8Oct 7, 2026
- v1.0.7Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts

