Install
$ agentstack add mcp-convisoappsec-conviso-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Conviso MCP Server
This is a Model Context Protocol (MCP) server that enables Claude Desktop (or any MCP client) to interact directly with the Conviso Platform. With this connector, the AI gains full context regarding your software assets, vulnerabilities, security projects, and risk metrics.
🛠 Available Tools (Capabilities)
The server exposes the following tools to the LLM:
| Category | Tool | Description | | --- | --- | --- | | General | get_companies | List companies and associated IDs. | | General | get_company_info | Plan details, integrations, and company branding info. | | Vulnerabilities | get_issues | List vulnerabilities by company or project. | | Vulnerabilities | get_issue | Technical details, including code snippets and raw requests/responses. | | Vulnerabilities | get_top_vulnerabilities | Risk overview (vulnerability count by severity). | | Vulnerabilities | get_issues_by_asset_id | List vulnerabilities for a company filtered by a single asset ID. | | Vulnerabilities | get_issues_by_project_id | List vulnerabilities for a company filtered by a project ID. | | Management | get_projects | List active security projects. | | Management | get_project | Get specific project in Conviso Platform by project ID. | | Assets | get_assets | List assets mapped within the platform. | | Assets | get_asset | Get asset in Conviso Platform by asset ID. | | Utilities | create_issue_url | Generates a direct link to the specific issue on the Conviso Platform. | | Utilities | create_project_url | Generates a direct link to the specific project on the Conviso Platform. | | Metrics | get_mttr_over_time | Get Mean Time To Resolution (MTTR) metrics over time for a company. Returns resolution times by severity level. | | Metrics | get_overall_risk_score_history | Get overall risk score history for a company, including current score and difference from last period. |
🚀 Installation and Configuration
Prerequisites
- Python 3.10 or higher installed.
- A Conviso Platform API Key (obtained from your profile settings).
- An MCP-compatible client (e.g., Claude Desktop, Cursor, etc).
1. Server Setup
Clone this repository and configure the virtual environment to run the server locally:
Python:
git clone https://github.com/convisoappsec/conviso-mcp.git
cd conviso-mcp
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
pip install -r python/requirements.txt
Node.js:
git clone https://github.com/convisoappsec/conviso-mcp.git
cd conviso-mcp/node
npm install
2. Execution Methods
Using Docker (Recommended for isolation)
You can build and run the server using Docker to avoid local dependency conflicts.
docker build -t conviso-mcp -f python/Dockerfile python/ # For Python version
docker build -t conviso-mcp-node-image -f node/Dockerfile node/ # For Node.js version
Using uv (Python)
uv can run the server directly from the pyproject.toml without manual environment management.
Using npm (Node.js)
npm can run the server directly from the package.json without requiring virtual environments or manual dependency management.
3. Client Configuration Examples
The Conviso MCP Server can be integrated into any MCP-compatible host. Below are examples for common clients.
Example: Claude Desktop
Claude Desktop reads settings from a JSON file. Location:
- Linux:
~/.config/Claude/claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add one of the following entries based on your preferred execution method:
A. Standard Python (Local Venv)
{
"mcpServers": {
"conviso-mcp": {
"command": "/PATH/TO/YOUR/PROJECT/venv/bin/python",
"args": ["/PATH/TO/YOUR/PROJECT/python/src/conviso_mcp/server.py"],
"env": { "CONVISO_API_KEY": "your_api_key_here" }
}
}
}
B. Node.js (Local)
{
"mcpServers": {
"conviso-mcp": {
"command": "node",
"args": [
"/PATH/TO/YOUR/PROJECT/node/src/conviso_mcp/server.js"
],
"env": {
"CONVISO_API_KEY": "your_api_key_here"
}
}
}
}
C. Docker
{
"mcpServers": {
"conviso-mcp-docker": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "CONVISO_API_KEY=your_api_key_here", "conviso-mcp"]
}
}
}
Node.js:
{
"mcpServers": {
"conviso-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e",
"CONVISO_API_KEY=your_api_key_here",
"conviso-mcp-node-image"
]
}
}
}
D. uv
{
"mcpServers": {
"conviso-mcp-uv": {
"command": "uv",
"args": ["--directory", "/PATH/TO/YOUR/PROJECT", "run", "conviso-mcp"],
"env": { "CONVISO_API_KEY": "your_api_key_here" }
}
}
}
Example: Cursor
Add the following JSON file, mcp.json or equivalent configuration, to the .cursor folder:
{
"mcpServers": {
"conviso-mcp": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/src/conviso_mcp",
"run",
"conviso-mcp"
],
"env": {
"CONVISO_API_KEY": "your_api_key_here"
}
}
}
}
> Warning: Always use absolute paths for commands and arguments.
4. Verification
After configuring your chosen client:
- Restart the application.
- Look for the MCP connection status (in Claude, this is the plug icon).
- Ensure the
conviso-mcpstatus is active/green.
🛡 Security and Privacy
This connector handles sensitive security data (vulnerabilities).
- Scope: The server operates using the permissions assigned to the provided API Key.
- Code Snippets: The
get_issuetool may return vulnerable code snippets if explicitly requested for AI analysis. - Logs: Error logs are directed to
stderrto prevent interference with the MCP communication protocol.
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: convisoappsec
- Source: convisoappsec/conviso-mcp
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.