Agent Security Scanner

io.github.MikehzpPublished by GitHub account Mikehzpv0.4.2Updated Oct 24, 2026

Scan AI agents for tool-calling vulnerabilities: prompt leaks, hijacking, injections, and more.

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

Scans AI agents for tool-calling vulnerabilities such as prompt leaks, hijacking, and injections.

What you can do
Agent Security Scanner is a local MCP server that lets an assistant run security scans against AI agents, focusing on tool-calling weaknesses. According to its description, it checks for prompt leaks, hijacking, injections, and similar issues. No individual tools are listed in the manifest, so the exact commands and outputs are not documented here.
When to use it
Consider it when you are building or testing an AI agent that calls tools and want a quick way to probe for prompt leakage, hijacking, or injection weaknesses. It is aimed at security review of agent behavior rather than general application scanning.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package agentvuln over stdio. It is desktop only and has no web executable. No authentication, environment variables, or headers are declared, so no credentials appear to be needed.
Before you install
The manifest declares no credentials, payments, or write access, and no tools are listed, so the scope of what it does to a target agent is unclear. Because it is a security testing tool, only point it at agents you own or are authorized to test, and review the package before running it locally.

Installation

In SourceWeft

  1. Open Agent Security Scanner 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.

Tools

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

Version history

1
  1. v0.4.2LatestSep 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.