About Apviso MCP
Apviso MCP connects MCP-compatible coding tools to the APVISO AI-powered penetration testing platform. It provides operations for targets, scans, findings, reports, schedules, and quota.
Key features
- 01Manage registered targets
- 02Verify domain ownership
- 03Create and inspect scans
- 04Review and update findings
- 05Retrieve pentest reports
- 06Manage schedules and quota
Use cases
- 01Registering and verifying a target domain
- 02Starting a penetration test and checking its status
- 03Reviewing findings and retrieving a report
- 04Checking credits and recurring scan schedules
MCP support
The MCP server exposes APVISO platform operations as tools to MCP-compatible clients, including Claude Code, Cursor, Windsurf, and Codex. It connects using an APVISO API key.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
18Saved tool list · updated 3w ago
This tool takes no parameters.
Details
From the project README@apviso/mcp
MCP server for interacting with the APVISO AI-powered penetration testing platform from Claude Code, Cursor, Windsurf, Codex, and other MCP-compatible tools.
Setup
1. Get your API key
Go to your APVISO dashboard → Settings → API Keys and create a new key.
2. Add to Claude Code
claude mcp add --transport stdio apviso \
--env APVISO_API_KEY=apvk_your_key_here \
-- npx -y @apviso/mcp
On Windows (not WSL):
claude mcp add --transport stdio apviso ^
--env APVISO_API_KEY=apvk_your_key_here ^
-- cmd /c npx -y @apviso/mcp
Alternative: manual config
Add to your .mcp.json (project-scoped) or ~/.claude.json (user-scoped):
{
"mcpServers": {
"apviso": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@apviso/mcp"],
"env": {
"APVISO_API_KEY": "apvk_your_key_here"
}
}
}
}
For team projects, use environment variable expansion in .mcp.json so each developer uses their own key:
{
"mcpServers": {
"apviso": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@apviso/mcp"],
"env": {
"APVISO_API_KEY": "${APVISO_API_KEY}"
}
}
}
}
3. Verify
Run /mcp inside Claude Code to check the server status.
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
APVISO_API_KEY | Yes | — | Your API key (starts with apvk_) |
APVISO_API_URL | No | https://apviso.com/api | API base URL |
Tools
Targets
| Tool | Description |
|---|---|
list_targets | List all registered targets |
get_target | Get target details |
create_target | Register a new domain |
verify_target | Verify domain ownership (DNS, file, or meta tag) |
get_verification_instructions | Get verification steps for a target |
delete_target | Remove a target |
Scans
| Tool | Description |
|---|---|
list_scans | List scans with optional status filter |
get_scan | Get scan details and status |
create_scan | Start a new penetration test (costs credits) |
Findings
| Tool | Description |
|---|---|
list_findings | List vulnerabilities for a scan |
update_finding_status | Mark findings as fixed, accepted risk, etc. |
Reports
| Tool | Description |
|---|---|
get_report | Get the full pentest report as markdown |
Schedules
| Tool | Description |
|---|---|
list_schedules | List recurring scan schedules |
get_schedule | Get schedule details |
create_schedule | Set up recurring scans (Business/Enterprise) |
update_schedule | Modify a schedule |
delete_schedule | Remove a schedule |
Quota
| Tool | Description |
|---|---|
get_quota | Check remaining credits and billing period |
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.