n0s1-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | No | Email for Jira/Confluence authentication | |
| JIRA_TOKEN | No | Token for Jira/Confluence authentication | |
| ASANA_TOKEN | No | Token for Asana authentication | |
| SLACK_TOKEN | No | Token for Slack authentication | |
| WRIKE_TOKEN | No | Token for Wrike authentication | |
| GITHUB_TOKEN | No | Token for GitHub authentication | |
| GITLAB_TOKEN | No | Token for GitLab authentication | |
| LINEAR_TOKEN | No | Token for Linear authentication | |
| ZENDESK_EMAIL | No | Email for Zendesk authentication | |
| ZENDESK_TOKEN | No | Token for Zendesk authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_jiraA | Read Jira tickets and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Jira — no comments are posted, no tickets are changed. Auth: requires JIRA_TOKEN and JIRA_EMAIL env vars, or pass api_key/email directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Jira API rate limits. |
| scan_confluenceA | Read Confluence pages and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Confluence — no pages or comments are written. Auth: requires CONFLUENCE_TOKEN (falls back to JIRA_TOKEN) and CONFLUENCE_EMAIL (falls back to JIRA_EMAIL) env vars, or pass api_key/email directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Confluence API rate limits. |
| scan_slackA | Read Slack messages to detect leaked secrets (API keys, tokens, passwords). Never modifies Slack — no messages are posted or edited. Auth: requires a bot token with channels:history and channels:read scopes; set SLACK_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Slack API rate limits. |
| scan_githubA | Read GitHub repository code, issues, and pull requests to detect leaked secrets. Never modifies GitHub — no commits, comments, or PRs are created. Auth: requires a personal access token with repo (or public_repo) scope; set GITHUB_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to GitHub API rate limits (5,000 req/hr authenticated). |
| scan_gitlabA | Read GitLab project code, issues, and merge requests to detect leaked secrets. Never modifies GitLab — no commits, comments, or MRs are created. Auth: requires a personal access token with read_api scope; set GITLAB_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to GitLab API rate limits. |
| scan_zendeskA | Read Zendesk tickets and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Zendesk — no tickets or comments are written. Auth: requires ZENDESK_TOKEN, ZENDESK_EMAIL, and ZENDESK_SERVER env vars, or pass server/email/api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Zendesk API rate limits. |
| scan_linearA | Read Linear issues and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Linear — no issues or comments are written. Auth: requires a Linear personal API key (lin_api_...); set LINEAR_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Linear API rate limits. |
| scan_asanaA | Read Asana tasks and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Asana — no tasks or comments are written. Auth: requires an Asana personal access token; set ASANA_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Asana API rate limits. |
| scan_wrikeA | Read Wrike tasks and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Wrike — no tasks or comments are written. Auth: requires a Wrike permanent access token; set WRIKE_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Wrike API rate limits. |
| scan_localA | Scan a local filesystem path for leaked secrets (API keys, tokens, passwords). Fully local — no network calls, no data sent to any external service. Never modifies scanned files. No authentication required. Returns redacted findings — raw secret values are never included in the output. |
| get_scan_statusA | Return the current status of a previously started scan. Read-only with no side effects — queries in-process scan state only. Returns 'pending' if the report_uuid is not yet known. |
| get_scan_findingsA | Return a paginated list of findings for a completed scan. Read-only with no side effects. All secret values are redacted — raw secrets are never returned. Pass next_cursor from a previous response to retrieve subsequent pages. |
| analyze_reportA | Submit or advance async AI credential validation for a previously uploaded scan report. Side effects: sends live HTTP validation requests to check whether discovered credentials are still active — this contacts the services where the secrets were found. Auth: requires n0s1_api_key or N0S1_TOKEN env var (n0s1 Professional account). Call once to queue, then poll until ai_analysis_status is 'complete' or 'failed'. Pass report_file when status is 'waiting_client' to inject credentials into validators. Pass wait_minutes to block until a terminal state or timeout; returns ai_analysis_status='timeout' if the deadline is reached without completion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/spark1security/n0s1-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server