n0s1-mcp
An MCP server that exposes n0s1 secret-scanning capabilities as tools for AI assistants (Claude, Cursor, etc.).
Scan Jira, Confluence, Slack, GitHub, GitLab, Zendesk, Linear, Asana, Wrike, and local filesystems for leaked secrets — directly from your AI workflow.
Quickstart
No install required. Add this to your MCP client config and run via uvx:
{
"mcpServers": {
"n0s1": {
"command": "uvx",
"args": ["n0s1-mcp"]
}
}
}
For Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
For Claude Code: .claude/mcp.json in your project, or ~/.claude/mcp.json globally.
Available Tools
| Tool | Description | Required params |
|---|---|---|
scan_jira |
Scan Jira tickets | server, email, api_key |
scan_confluence |
Scan Confluence pages | server, email, api_key |
scan_slack |
Scan Slack channels | api_key |
scan_github |
Scan GitHub repositories | api_key, owner |
scan_gitlab |
Scan GitLab projects | api_key, owner |
scan_zendesk |
Scan Zendesk tickets | server, email, api_key |
scan_linear |
Scan Linear issues | api_key |
scan_asana |
Scan Asana tasks | api_key |
scan_wrike |
Scan Wrike tasks | api_key |
scan_local |
Scan local filesystem | scan_path |
get_scan_status |
Get status of a running/completed scan | report_uuid |
get_scan_findings |
Get paginated findings for a completed scan | report_uuid |
analyze_report |
Submit or advance async AI credential validation | report_uuid |
All scan_* tools accept these optional parameters:
| Parameter | Description |
|---|---|
report_uuid |
UUID to assign to the scan report. When set, overrides the auto-generated UUID written to the report JSON. |
ai_analysis |
Queue async AI credential validation after the scan (requires n0s1 Professional) |
n0s1_api_key |
n0s1 API key; overrides N0S1_TOKEN env var |
allow_secret_upload |
Allow encrypted secrets to be uploaded to the n0s1 backend (default: false) |
Pass wait_minutes to analyze_report (or directly on a scan tool alongside ai_analysis) to block until analysis completes.
Environment Variables
Credentials can be passed as tool arguments or pre-set as environment variables:
| Variable | Used by |
|---|---|
N0S1_TOKEN |
All scan tools with ai_analysis — Professional mode uploads and AI analysis |
JIRA_TOKEN |
scan_jira, scan_confluence |
JIRA_EMAIL |
scan_jira, scan_confluence |
SLACK_TOKEN |
scan_slack |
GITHUB_TOKEN |
scan_github |
GITLAB_TOKEN |
scan_gitlab |
ZENDESK_TOKEN |
scan_zendesk |
ZENDESK_EMAIL |
scan_zendesk |
LINEAR_TOKEN |
scan_linear |
ASANA_TOKEN |
scan_asana |
WRIKE_TOKEN |
scan_wrike |
Example with env vars pre-configured:
{
"mcpServers": {
"n0s1": {
"command": "uvx",
"args": ["n0s1-mcp"],
"env": {
"GITHUB_TOKEN": "ghp_...",
"JIRA_TOKEN": "ATATT..."
}
}
}
}
Usage Examples
Once connected, ask your AI assistant:
- "Scan my Jira project SEC for leaked secrets"
- "Check the GitHub org mycompany for exposed API keys"
- "Scan the /home/user/project directory for secrets"
- "Run an AI analysis on the scan report abc123"
For full parameter reference and AI analysis workflow details, see docs/ai.md.
Publishing to PyPI
pip install hatch
hatch build
hatch publish
License
GNU General Public License v3 — same as n0s1.
Metadata
Release files for n0s1-mcp 1.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| n0s1_mcp-1.1.6.tar.gz | 40.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| n0s1_mcp-1.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 74.1 kB
Release files / n0s1_mcp-1.1.6.tar.gz
| Download URL | n0s1_mcp-1.1.6.tar.gz |
|---|---|
| Size | 40.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b3434f916773379e2b5df958d4d8fb6ffa6bed65c4e79d05a310f47b025d49d
|
|
BLAKE2b-256 checksum How to use checksums |
8ad1741c363a36180942ad9da3f694b85a0cd799888c5c67583d65138a610577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / n0s1_mcp-1.1.6-py3-none-any.whl
| Download URL | n0s1_mcp-1.1.6-py3-none-any.whl |
|---|---|
| Size | 33.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e853376d63ae8de191b2bc1096d78e16ccaaca8380d47d55bc83e10942017f5
|
|
BLAKE2b-256 checksum How to use checksums |
5ada8c3ef382987123b798e0cd92dd834c2776734a345db87e0f357e0e3d99e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logSecurity for n0s1-mcp 1.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for n0s1_mcp-1.1.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.