1. Conduid
  2. Security
  3. Security Scan
MCP server · Security

Security Scan

by · github.com/echo-lumen/mcp-security-scan

Security scanner for MCP (Model Context Protocol) servers. Detect authentication gaps, credential exposure, SSRF risks, and misconfigurations. Maps findings to OWASP MCP Top 10.

Unclaimed last commit 7 months ago security
InstallView source
34Low

Scored 13 days ago · breakdown

About Security Scan

Security Scan is an MCP server published by echo-lumen in the Security category: security scanner for MCP (Model Context Protocol) servers. Detect authentication gaps, credential exposure, SSRF risks, and misconfigurations. Maps findings to OWASP MCP Top 10.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/echo-lumen/mcp-security-scan

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (4)

**mcp-security-scan**Yes

Parameters not published.

MCPSecNo (static)

Parameters not published.

Snyk Agent ScanYes

Parameters not published.

mcp-security-scan (cc-fuyu)No (static)

Parameters not published.

Ask AI

✦

Ask AI about Security Scan

Powered by Claude · Grounded in docs

I know everything about Security Scan. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Security Scan

How do I install Security Scan?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Security Scan safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Security Scan still maintained?

The last commit was 7 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.