mcpField
A
Apviso MCP

Apviso MCP

Local
github.com/apvisoDeveloper Tools0Updated 30w ago

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

  1. 01Manage registered targets
  2. 02Verify domain ownership
  3. 03Create and inspect scans
  4. 04Review and update findings
  5. 05Retrieve pentest reports
  6. 06Manage schedules and quota

Use cases

  1. 01Registering and verifying a target domain
  2. 02Starting a penetration test and checking its status
  3. 03Reviewing findings and retrieving a report
  4. 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.

mcp.json · Universal config
{
"mcpServers": {
"apviso": {
"command": "npx",
"args": [
"-y",
"@apviso/mcp"
],
"env": {
"APVISO_API_KEY": "<APVISO_API_KEY>"
}
}
}
}
Run commandnpx -y @apviso/mcp
Environment variables to set
APVISO_API_KEYSecret

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@apviso/mcp

Tools

18

Saved 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

VariableRequiredDefaultDescription
APVISO_API_KEYYes—Your API key (starts with apvk_)
APVISO_API_URLNohttps://apviso.com/apiAPI base URL

Tools

Targets
ToolDescription
list_targetsList all registered targets
get_targetGet target details
create_targetRegister a new domain
verify_targetVerify domain ownership (DNS, file, or meta tag)
get_verification_instructionsGet verification steps for a target
delete_targetRemove a target
Scans
ToolDescription
list_scansList scans with optional status filter
get_scanGet scan details and status
create_scanStart a new penetration test (costs credits)
Findings
ToolDescription
list_findingsList vulnerabilities for a scan
update_finding_statusMark findings as fixed, accepted risk, etc.
Reports
ToolDescription
get_reportGet the full pentest report as markdown
Schedules
ToolDescription
list_schedulesList recurring scan schedules
get_scheduleGet schedule details
create_scheduleSet up recurring scans (Business/Enterprise)
update_scheduleModify a schedule
delete_scheduleRemove a schedule
Quota
ToolDescription
get_quotaCheck remaining credits and billing period

License

MIT

Comments

Markdown supported

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.