Scancode License Analysis Tool for MCP
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 |
|---|---|
| mcp_ScancodeMCP_analyze_license_fileA | Clause-by-clause legal analysis of all licenses detected in a file, including obligations, risks, and compatibility. |
| mcp_ScancodeMCP_summarize_license_risksB | Lists all files with high-risk/problematic licenses and provides a legal risk summary for each license type. |
| mcp_ScancodeMCP_compare_license_compatibilityB | Legal compatibility verdict and explanation for two license types (e.g., MIT vs GPLv3). |
| mcp_ScancodeMCP_list_high_risk_filesA | Lists all files with copyleft, unknown, or commercial-unfriendly licenses, with a legal warning for each. |
| mcp_ScancodeMCP_get_license_clause_summaryB | Clause-by-clause legal summary of a license (obligations, risks, compatibility, etc). |
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 5 tools
Most tools have distinct purposes: analyze_license_file examines a specific file's licenses, compare_license_compatibility checks two licenses, get_license_clause_summary details a single license, and list_high_risk_files and summarize_license_risks both identify high-risk files but with slightly different focuses (listing vs. summarizing). The overlap between list_high_risk_files and summarize_license_risks could cause minor confusion, but descriptions clarify their nuances.
All tool names follow a consistent pattern with the prefix 'mcp_ScancodeMCP_' and use snake_case for the action-object structure (e.g., analyze_license_file, compare_license_compatibility). This uniformity makes the set predictable and easy to navigate, with no deviations in naming conventions.
With 5 tools, the server is well-scoped for license analysis, covering key operations like analysis, comparison, summarization, and risk identification. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain's complexity and typical use cases.
The tool set covers core aspects of license analysis, including detailed examination, compatibility checks, and risk assessment. A minor gap exists in lacking tools for broader actions like batch processing multiple files or managing license databases, but agents can work around this with the provided tools for most workflows.