mcp-license-header-guardian
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_license_headerA | Deterministic, network-free, read-only Tier 1 guardian. Checks .py files tracked by git to ensure the first 5 lines contain "Copyright" OR "SPDX-License-Identifier". |
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 tool's purpose is singular and clearly defined.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'check_license_header' follows a clear verb_noun pattern.
One tool is too few for the server's apparent purpose of license header management, as it only provides a read-only check without any complementary tools for fixing, updating, or managing headers across files.
The tool surface is severely incomplete for license header management, lacking essential operations such as adding, removing, or modifying headers, which are necessary for a full workflow in this domain.