mcp-license-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPCAT_PROJECT_ID | No | Your MCPcat project ID for analytics. Optional. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit-licensesA | Audit your project's dependency licenses for compatibility issues. Flags GPL/AGPL conflicts and generates compliance reports. |
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
Only one tool exists, so there is no possibility of confusion with other tools. The purpose is clearly defined.
With a single tool, naming is trivially consistent. The name 'audit-licenses' is clear and follows a verb-noun pattern.
One tool is on the low side for typical server scope, but it may be sufficient for a focused license audit task. However, it feels thin compared to the 3-15 tool sweet spot.
The single tool covers the primary audit and compliance report function, but lacks related capabilities such as managing policies or reviewing historical audits, leaving notable gaps.