Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

审计 MCP server 项目的安全风险:命令注入、越权文件读写、敏感信息泄露、危险权限、tool 描述面的 prompt injection。

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_mcp_serverB

审计一个 MCP server 项目(本地路径)的安全风险,返回结构化风险清单

scan_public_repoA

扫描公开仓库(github.com / gitlab.com / gitee.com)里的 MCP server 安全风险。只读克隆,扫描后立即删除。

list_rulesA

列出扫描器的全部规则(规则 id、严重度、说明、修复建议),用于判断这套扫描覆盖什么

scan_to_sarifA

扫描本地路径或公开仓库并直接返回 SARIF 2.1.0 文档(可上传 GitHub code scanning)

explain_ruleB

查询单条规则的严重度、含义与修复建议

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

The three scan tools have some overlap because scan_to_sarif accepts local paths and public repos, overlapping scan_mcp_server and scan_public_repo. However, their outputs and targets are described clearly enough that an agent can distinguish them: SARIF export versus structured risk lists versus public-repo scanning.

Naming Consistency4/5

All tool names use snake_case and begin with a verb: list_rules, explain_rule, scan_mcp_server, and scan_public_repo follow a clear verb_noun pattern. scan_to_sarif is a minor deviation because it names an output format rather than a target object, but it remains predictable.

Tool Count5/5

Five tools are well scoped for a focused MCP security-audit server: rule discovery, rule explanation, local scanning, public-repo scanning, and SARIF export. Each tool has a clear role and the set does not feel padded.

Completeness4/5

The set covers the core workflow: inspect rules, explain a rule, scan local MCP servers, scan public repos, and export SARIF. Minor gaps remain, such as no rule filtering/configuration, no batch or history view, and no result comparison, but the main audit lifecycle is present.

Maintenance

ActivityActive
ResponsivenessNo recent community issues