N0s1 Mcp

io.github.spark1securityPublished by GitHub account spark1securityv1.1.6Updated Oct 24, 2026

Secret scanner for Slack, Jira, Confluence, Asana, Wrike, Linear, Zendesk, GitHub and GitLab

VerifiedSTDIODesktop onlySecurity & Monitoring

Server details

Identifier: io.github.spark1security/n0s1-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account spark1security for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.spark1security%2Fn0s1-mcp.svg)](https://sourceweft.com/mcp/io.github.spark1security%2Fn0s1-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant run the n0s1 secret scanner across Slack, Jira, Confluence, Asana, Wrike, Linear, Zendesk, GitHub and GitLab.

What you can do: Scan connected collaboration and code platforms for exposed secrets
Cover Slack, Jira, Confluence, Asana, Wrike, Linear, Zendesk, GitHub and GitLab
Report findings from the n0s1 scanner to the assistant
No individual tools are documented in the supplied listing, so exact operations are unconfirmed
When to use it: Useful when you want an assistant to check team chat, ticketing, wiki and repository platforms for leaked credentials or other secrets, for example during a security review or before sharing a workspace more widely.
Requirements: Runs as a local process installed from the PyPI package n0s1-mcp over stdio, on desktop only. An API key for n0s1 Professional is supplied through the N0S1_TOKEN environment variable. Access to the platforms being scanned is implied but not described.

Before you install

The server requires the N0S1_TOKEN secret, which grants access to n0s1 Professional. Scanning reads content from connected workspaces and repositories, so findings and possibly matched content may be surfaced to the assistant and its model provider. Review what data leaves your environment before scanning sensitive workspaces.

Installation

In SourceWeft

Open N0s1 Mcp 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.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.6LatestSep 16, 2026

Score

25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.