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 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_jiraB | Scan Jira tickets for leaked secrets |
| scan_confluenceC | Scan Confluence pages for leaked secrets |
| scan_slackB | Scan Slack channels for leaked secrets |
| scan_githubB | Scan GitHub repositories for leaked secrets |
| scan_gitlabB | Scan GitLab projects for leaked secrets |
| scan_zendeskB | Scan Zendesk tickets for leaked secrets |
| scan_linearB | Scan Linear issues for leaked secrets |
| scan_asanaB | Scan Asana tasks for leaked secrets |
| scan_wrikeB | Scan Wrike tasks for leaked secrets |
| scan_localB | Scan a local filesystem path for leaked secrets |
| get_scan_statusB | Return the current status of a previously started scan |
| get_scan_findingsA | Return a paginated list of findings for a completed scan |
| analyze_reportA | Submit or advance async AI analysis for a previously uploaded report. Call once after a scan to queue analysis, then call again periodically until ai_analysis_status is 'complete' or 'failed'. Pass report_file when the status is 'waiting_client' so real credentials can be injected into the HTTP validator requests. |
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
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