n0s1-mcp@1.1.6
VERIFIED· not startedPublisher claims: "MCP server for n0s1 — scan Jira, Confluence, Slack, GitHub, GitLab, Zendesk, Linear, Asana, Wrike, and local files for leaked secrets" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
ASANA_TOKENGITHUB_TOKENGITLAB_TOKENJIRA_TOKENLINEAR_TOKENN0S1_TOKENSLACK_TOKENWRIKE_TOKENZENDESK_TOKENConfiguration, not credentials: JIRA_EMAIL, RUNNER_ENV, ZENDESK_EMAIL- Where it talks to
- no vendor host named in the codeAlso atlassian.net — 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names atlassian.net as well as its own vendor. The guard injects ASANA_TOKEN, GITHUB_TOKEN, GITLAB_TOKEN, JIRA_TOKEN, LINEAR_TOKEN, N0S1_TOKEN, SLACK_TOKEN, WRIKE_TOKEN, ZENDESK_TOKEN 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; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 84/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
"Auth: requires JIRA_TOKEN and JIRA_EMAIL env vars, or pass api_key/email directly. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."(falls back to JIRA_EMAIL) env vars, or pass api_key/email directly. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."set GITLAB_TOKEN env var or pass api_key directly. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.sudo mv mcp-publisher /usr/local/bin/Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."set GITHUB_TOKEN env var or pass api_key directly. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."set SLACK_TOKEN env var or pass api_key directly. "Fix: 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 n0s1-mcp@1.1.6 as of 38 h ago. This is the package itself, not its dependencies.