Mcp Server Security Audit

io.github.joepangalloPublished by GitHub account joepangallov1.0.3Updated Oct 24, 2026

Scan websites for security vulnerabilities, headers, TLS, and email security.

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant scan websites for security vulnerabilities, HTTP headers, TLS configuration and email security.

What you can do
Scan websites for security vulnerabilities, HTTP headers, TLS configuration and email security. The manifest lists no individual tools, so the exact operations are not documented; the stated scope is website security auditing. It runs as a local process on the user's machine over stdio.
When to use it
Useful when you want an assistant to check a site's security posture — headers, TLS and email security settings — during a review or before deployment. It is a narrow auditing helper rather than a general web tool.
Requirements
Runs as a local process over stdio, installed from the npm package mcp-server-security-audit, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Network access to the target websites is implied by the scanning purpose.
Before you install
The server scans third-party websites; only scan sites you own or are authorized to test. No credentials or secrets are declared, and no write actions are described, but the manifest lists no tools, so review the package before running it locally.

Installation

In SourceWeft

  1. Open Mcp Server Security Audit 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. v1.0.3LatestSep 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.

Other Audit integrations