
SentinelOne (Purple)
io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.0.11更新於 Nov 14, 2026
Multitenant Streamable HTTP wrapper for the SentinelOne purple-mcp server.
概覽
多租戶 HTTP 封裝層,把 SentinelOne purple-mcp 伺服器提供給閘道,並從請求標頭傳入各租戶的 SentinelOne 憑證。
- 可以做什麼
- 透過單一 Streamable HTTP 端點(POST /mcp)提供上游 SentinelOne purple-mcp 的工具
- 依請求讀取 SentinelOne API 權杖與主控台 URL 標頭,為每個租戶視需要啟動獨立子程序並轉送請求
- 在讀取租戶憑證前驗證服務對服務的 HMAC 證明標頭
- 透過免驗證的健康檢查端點回報存活狀態
- 依可設定的逾時回收閒置租戶程序,並限制同時存在的租戶數量
- 適用情境
- 適合維運多租戶 MCP 閘道的人員:需要把各組織的 SentinelOne 主控台憑證以 HTTP 標頭形式轉送給同一個共用容器,而不是為每個租戶各跑一個單租戶 purple-mcp 實例。
- 執行需求
- 以本機容器映像執行(清單宣告 stdio,但代理實際監聽 HTTP)。啟動必須設定 CONDUIT_S2S_SECRET,每個請求需帶 X-Gateway-S2S、X-S1-API-Token 與 X-S1-Console-URL 標頭(也接受舊版 x-purplemcp-* 別名)。可用 PORT、MCP_HTTP_HOST、IDLE_EVICT_MS、SPAWN_READY_TIMEOUT_MS、MAX_CHILDREN、LOG_LEVEL 調整。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 SentinelOne (Purple),將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
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.
來源:README.md,提交 b5540c4
工具
0版本歷史
5- v1.0.11最新Nov 14, 2026
- v1.0.10Nov 11, 2026
- v1.0.9Oct 14, 2026
- v1.0.8Oct 7, 2026
- v1.0.7Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分

