Scannd

com.scanndPublished by scannd.comv0.1.0Updated Oct 24, 2026

Trigger security scans and read reports/vulnerabilities via the hosted Scannd API. Free: 2 scans/mo.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Scannd lets an assistant start security scans and read reports and vulnerabilities through the hosted Scannd API, using a local npm MCP server.

What you can do
  • Trigger security scans through the hosted Scannd API
  • Read scan reports and the vulnerabilities they list
  • Run as a local stdio process started by the assistant on the user's desktop
When to use it
Useful when you want an assistant to kick off security scans and pull the resulting reports and vulnerability findings into a conversation without leaving the chat. The free tier allows only 2 scans per month, so it suits occasional checks rather than continuous scanning.
Requirements
A local runtime that can run the npm package scannd-mcp over stdio, on a desktop machine. A Scannd API key supplied in the SCANND_API_KEY environment variable; keys start with sk_ and are obtained from the Scannd site. Network access to the hosted Scannd API.
Before you install
The API key in SCANND_API_KEY is a secret sent to the hosted API as the X-API-Key header; keep it out of shared configs and logs. Scans and their results are processed by a third-party hosted service. Starting scans is an action that consumes the limited free quota of 2 scans per month and may incur cost on paid plans.

Installation

In SourceWeft

  1. Open Scannd in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.