Apviso MCP Server

MCP server for interacting with APVISO penetration testing platform

Local serverstdioGo

What is the Apviso MCP MCP server?

Connect Apviso MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for interacting with APVISO penetration testing platform. The apviso mcp mcp server is what makes that connection.

What the server does

MCP server for interacting with the APVISO AI-powered penetration testing platform from Claude Code, Cursor, Windsurf, Codex, and other MCP-compatible tools.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Targets — The Targets tool exposed by this server
  • Scans — The Scans tool exposed by this server
  • Findings — The Findings tool exposed by this server
  • Reports — The Reports tool exposed by this server
  • Schedules — The Schedules tool exposed by this server
  • Quota — The Quota tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: APVISO_API_KEY, APVISO_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as @apviso/mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Apviso MCP's toolset — Targets, Scans, Findings and 3 more — is a fair guide to whether it matches your workflow. It is maintained by apviso; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
TargetsThe Targets tool exposed by this server.
ScansThe Scans tool exposed by this server.
FindingsThe Findings tool exposed by this server.
ReportsThe Reports tool exposed by this server.
SchedulesThe Schedules tool exposed by this server.
QuotaThe Quota tool exposed by this server.

How to install the Apviso MCP MCP server

{
  "mcpServers": {
    "apviso": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@apviso/mcp"],
      "env": {
        "APVISO_API_KEY": "apvk_your_key_here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
APVISO_API_KEYCredential the server authenticates with.Yes
APVISO_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Apviso MCP to Targets.
  • Use Apviso MCP to Scans.
  • Use Apviso MCP to Findings.

Frequently asked questions

It connects Apviso MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Targets, Scans, Findings, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Apviso MCP directly.