Dradis MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRADIS_URL | Yes | Your Dradis instance URL | |
| DRADIS_API_TOKEN | Yes | Your Dradis API token | |
| DRADIS_DEFAULT_TEAM_ID | No | Default team ID for project creation (optional) | |
| DRADIS_DEFAULT_TEMPLATE_ID | No | Default template ID for project creation (optional) | |
| DRADIS_VULNERABILITY_PARAMETERS | No | Comma-separated list of vulnerability field names (optional) |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setProjectA | Set the current Dradis project context for all subsequent operations |
| getProjectDetailsA | Get detailed information about the current Dradis project including metadata, team, and settings |
| createProjectB | Create a new Dradis project with specified configuration and automatically set it as the current project context |
| createVulnerabilityA | Create a new security vulnerability finding in the current project with detailed information |
| getVulnerabilitiesA | Retrieve a paginated list of vulnerability summaries from the current project, including ID, title, and risk rating |
| getAllVulnerabilityDetailsB | Retrieve a paginated list of complete vulnerability details including all fields and metadata from the current project |
| getVulnerabilityB | Retrieve complete details for a specific vulnerability including all fields, evidence, and metadata |
| updateVulnerabilityA | Update an existing vulnerability with new information, modifying only the specified fields |
| getContentBlocksA | Retrieve all content blocks from the current project, including their IDs and field data |
| updateContentBlockA | Update a content block in the current project with new field values and content |
| getDocumentPropertiesA | Retrieve all document properties and their values for the current project configuration |
| upsertDocumentPropertyB | Create a new document property or update an existing property value in the current project |
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/LiterallyBlah/Dradis-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server