sophos-central-mcp-server@0.13.2
VERIFIED· startup onlyPublisher claims: "MCP server for the Sophos Fusion (formerly Sophos Central) APIs - SOC monitoring, endpoint management, admin automation, XDR investigation, and Fusion GraphQL cases" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MCP_HTTP_TOKENSOPHOS_CLIENT_SECRETConfiguration, not credentials: CHARACTER_LIMIT, MCP_ALLOWED_ORIGINS, MCP_HTTP_HOST, SOPHOS_CLASSIC_MIGRATION_CHECK, SOPHOS_CLIENT_ID, SOPHOS_FUSION_GRAPHQL_URL, SOPHOS_TENANT_ID, SUMMARY_KEY_FINDINGS_CHARS, TRANSPORT- Where it talks to
- no vendor host named in the codeAlso sophos.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names sophos.com as well as its own vendor. The guard injects MCP_HTTP_TOKEN, SOPHOS_CLIENT_SECRET only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 26 s · 2 scenarios · 0 deviationsStatic findings
* "https://inspector.example.com,http://10.0.0.5:6274". Each entry is reducedFix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.* from a .env in the working directory, which for a stdio server is whateverFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* "https://inspector.example.com,http://10.0.0.5:6274". Each entry is reducedFix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.* from a .env in the working directory, which for a stdio server is whateverFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for sophos-central-mcp-server@0.13.2 as of 5d ago. This is the package itself, not its dependencies.