MCP.Market

SentinelOne (Purple) MCP server

by WYRE-AI·io.github.WYRE-AI/sentinelone-mcp·v1.0.9
No reviews yet

Multitenant Streamable HTTP wrapper for the SentinelOne purple-mcp server.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed SentinelOne (Purple) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

SentinelOne (Purple) tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 12 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How SentinelOne (Purple) compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers

Release history: 3 versions in the registry since 2026-08-26, latest 2026-10-14, typically one every 41 days.

Install SentinelOne (Purple) in Claude Code, Cursor or VS Code

claude mcp add sentinelone-mcp -- docker run -i --rm ghcr.io/wyre-ai/sentinelone-mcp:v1.0.9
Add to Cursor

What the publisher says

From the SentinelOne (Purple) repository's README, as published. We do not edit it. Read it on GitHub

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:

  1. Listens on :8080 with POST /mcp and GET /health.
  2. Reads x-purplemcp-token and x-purplemcp-base-url from each incoming request.
  3. Lazily spawns one purple-mcp --mode streamable-http child per (token, base-url) tenant on a private loopback port, with the right env vars set.
  4. Proxies the request body to that child and streams the response back.
  5. Evicts idle children after 60 minutes (IDLEEVICTMS).

The result is a single container that the gateway can talk to like any other vendor MCP server.

Configuration

Request headers

The gateway must forward these headers on every /mcp request:

Build

docker build -t ghcr.io/wyre-ai/sentinelone-mcp:latest .

License

Apache-2.0. The bundled purple-mcp is MIT-licensed by SentinelOne.

Nothing above is checked by us. What we check is on the safety report.

SentinelOne (Purple): common questions

Is SentinelOne (Purple) MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the SentinelOne (Purple) safety report
How do I install SentinelOne (Purple)?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does SentinelOne (Purple) need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is SentinelOne (Purple) maintained?
The last commit was 16 days ago (2026-10-19). The latest release is v1.0.9.

More from WYRE-AI →