mcp-web-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auditPackageB | 审计前端工程的所有直接和间接依赖，得到安全审计结果。支持本地工程的审计，也支持远程仓库的审计。审计结果为标准格式的markdown字符串，不用修改，直接用于展示即可。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'auditPackage' has a clearly defined and distinct purpose focused on auditing dependencies.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'auditPackage' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a server named 'mcp-web-audit', which suggests a broader scope for web auditing. The tool only covers dependency auditing, leaving gaps for other potential web audit functions like performance checks or accessibility testing.
The tool set is severely incomplete for the inferred domain of web auditing. It only provides dependency auditing, missing obvious operations such as security scanning, performance analysis, or compliance checks, which are typical in web audit workflows.