This server exposes secret-scanning capabilities as MCP tools, allowing AI assistants to scan various platforms and filesystems for leaked credentials and secrets.

Scanning

• Jira — Scan tickets for leaked secrets, with JQL query scoping and optional auto-posting of warning comments

• Confluence — Scan pages using CQL query scoping

• Slack — Scan channels using a bot token

• GitHub — Scan repositories with optional branch/repo filtering

• GitLab — Scan projects, including self-hosted instances

• Zendesk — Scan tickets for leaked secrets

• Linear — Scan issues for leaked secrets

• Asana — Scan tasks with optional workspace/project scoping

• Wrike — Scan tasks with optional folder/space scoping

• Local filesystem — Scan a local path, with support for custom regex rules

Monitoring & Analysis

• Check scan status — Monitor progress of a running scan via its UUID

• Get scan findings — Retrieve paginated, severity-filterable findings from completed scans

• Analyze reports — Queue async AI-powered credential validation on scan results (requires n0s1 Professional)

Other features: Multiple report formats (n0s1, sarif, gitlab), credentials passable as tool arguments or environment variables, and custom UUID assignment for scan reports.

Scan Asana tasks for leaked secrets, including task details and attachments.

Scan Confluence pages for leaked secrets, including page content and attachments.

Scan GitHub repositories for leaked secrets, including code, issues, and pull requests.

Scan GitLab projects for leaked secrets, including code, issues, and merge requests.

Scan Jira tickets for leaked secrets using the n0s1 engine, including ticket contents and metadata.

Scan Linear issues for leaked secrets, including issue descriptions and comments.

Scan Slack channels for leaked secrets, including messages and files.

Scan Zendesk tickets for leaked secrets, including ticket comments and attachments.

1. Click on "Install Server".

2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.

3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@n0s1-mcp Scan the GitHub org mycompany for exposed API keys"

That's it! The server will respond to your query, and you can continue using it as needed.

Here is a step-by-step guide with screenshots.

{
 "mcpServers": {
 "n0s1": {
 "command": "uvx",
 "args": ["n0s1-mcp"]
 }
 }
}

{
 "mcpServers": {
 "n0s1": {
 "command": "uvx",
 "args": ["n0s1-mcp"],
 "env": {
 "GITHUB_TOKEN": "ghp_...",
 "JIRA_TOKEN": "ATATT..."
 }
 }
 }
}

pip install hatch
hatch build
hatch publish