Skip to content
Back to the index

mcpsecscan

PyPIInfrastructure

PulseGate's liveness check found it on 8 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 8 Aug 2026. How this is checked

mcpsecscan is an open-source security scanner for Model Context Protocol servers. It detects tool poisoning, over-privileged tools, hidden instructions, and prompt-injection surfaces for developers and security teams.

Inferred · not functionally tested

Open SourceMITCLISelf-hosted
Visit PyPI
1alternative
5features
2026since

Overview

5 features

Purpose: Identifying security risks and prompt-injection surfaces in MCP servers before deployment.

Inferred · not functionally tested

Audience: developers and application security teams

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

mcpsecscan is an AI & LLM security project. Inferred · not functionally tested: It focuses on identifying security risks and prompt-injection surfaces in MCP servers before deployment. Inferred · not functionally tested: mcpsecscan is an open-source project aimed at developers and application security teams. Basis unknown · not verified: mcpsecscan is open source under the MIT license. Basis unknown · not verified: mcpsecscan is available on the command line, and it can be self-hosted.

Behind mcpsecscan is nadirzhon, and it first shipped in 2026. Development happens publicly on GitHub with 6 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include tool poisoning detection, privilege analysis, and hidden instruction detection. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Tool poisoning detection
  • Privilege analysis
  • Hidden instruction detection
  • Injection surface scanning
  • MCP server scanning

Topics: Inferred · not functionally tested

Tags
mcp-securitytool-poisoningprompt-injectionappsecllm-security

JSON profile · Text profile · Access guide

Built with & integrations

Connectors
MCPgithub
Runs on
CLISelf-hosted

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceFree tierGitHubActive maintenance

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed8 Aug · 21:45 UTC
    mcpsecscan seen via PyPI Bulk Enumerator
    Source: PyPI Bulk Enumerator · Open

Frequently asked questions about mcpsecscan

What is mcpsecscan?
Inferred · not functionally tested: Mcpsecscan focuses on identifying security risks and prompt-injection surfaces in MCP servers before deployment. It is catalogued under AI & LLM security on PulseGate.
Who is mcpsecscan for?
Inferred · not functionally tested: mcpsecscan is an open-source project built for developers and application security teams.
Does mcpsecscan have a free plan?
Basis unknown · not verified: Yes — mcpsecscan is open source under the MIT license and free to use.
What platforms does mcpsecscan run on?
Basis unknown · not verified: mcpsecscan runs on the command line. It can also be self-hosted.
Is mcpsecscan still active?
PulseGate's liveness check found it on 8 Oct 2026. Its GitHub repository shows 6 commits in the last 90 days.
What projects are similar to mcpsecscan?
Similar projects tracked by PulseGate include mcp-security-scan, mcp-safety, and mcpsec.mcp-security-scanmcp-safetymcpsec
Who makes mcpsecscan?
mcpsecscan is developed by nadirzhon.
When did mcpsecscan launch?
mcpsecscan first shipped in 2026.

Similar projects

Closest matches by what these projects do