# License Header Injector and Verifier MCP for AI Agents MCP

> License Header Injector and Verifier manages copyright headers in your source files. It automates the process of checking for missing licenses, fixing formatting errors, and ensuring your templates are structurally sound to maintain legal compliance across your codebase.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_cxe57NEIQ1l7n9SKWmb1BYAMvYUxTL5s3LYfEwwx/mcp
- **Tags:** copyright, license, audit, header, verification

## Description

Managing copyright notices across thousands of files is a nightmare. You start with one template, but eventually, someone changes a space, or a new file gets added without any header at all. Instead of manually auditing every single file in your repository, you can use this MCP to handle the heavy lifting. It acts as an automated auditor for your codebase. You can point your agent at a directory and have it find exactly where your headers have drifted from the standard or simply fix files that are missing them entirely. When you connect through Vinkius, you're adding a layer of legal safety to your development workflow. It is about making sure your intellectual property is clearly marked without you having to touch a single text editor.

## Tools

### validate_template_integrity
Checks that your copyright block is a valid, usable template for files. It ensures the structure is correct before you apply it.

### apply_license_header
Prepends the required header to any file that is missing it. This fixes non-compliant files in one step.

### identify_header_drift
Finds headers that have incorrect spacing or formatting errors. It detects when a header exists but is broken.

## Prompt Examples

**Prompt:** 
```
Check if the files in /src have the correct copyright year.
```

**Response:** 
```
| File Path | Status |
| :--- | :--- |
| `/src/auth.js` | **Compliant** |
| `/src/utils.js` | **Missing Header** |
| `/src/api.js` | **Formatting Drift** |
```

**Prompt:** 
```
I have a new template for our license. Can you make sure it is valid?
```

**Response:** 
```
The structure of your provided template is valid and meets all requirements for use in your files.
```

**Prompt:** 
```
Are there any headers that do not match our standard formatting?
```

**Response:** 
```
I found **2 files** with spacing issues in the `/lib/auth` directory. They need to be updated to match your template.
```

## Capabilities

### Automate copyright enforcement
Automatically add missing headers to files that lack them.

### Detect formatting errors
Find where spacing or characters in your headers do not match the template.

### Verify template structure
Check that your copyright block is valid before you deploy it to your files.

### Audit codebase compliance
Scan directories to see which files are out of alignment with legal requirements.

## Use Cases

### New Repository Onboarding
A developer adds a new module and asks the agent to ensure all files have the correct company copyright using apply_license_header.

### Post-Refactor Cleanup
After a massive directory move, use identify_header_drift to find any headers that were accidentally altered during the process.

### Compliance Auditing
An engineer needs to generate a report of all files missing a specific license year across the entire project.

### Template Updates
When the company changes its legal name, use the agent to update every header across the entire project automatically.

## Benefits

- Eliminate manual audits by using apply_license_encoded to fix missing notices instantly.
- Maintain perfect formatting consistency with identify_header_drift.
- Prevent broken templates from being deployed using validate_template_integrity.
- Reduce legal risk by ensuring every file in your repository is properly marked.
- Save hours of manual text editing during large-scale codebase refactors.

## How It Works

The bottom line is you get an automated way to keep your legal headers consistent across every file in your project.

1. Connect this MCP to your preferred AI client via Vinkius.
2. Provide a valid copyright template for the agent to use as a reference.
3. Instruct your agent to scan specific files or directories for compliance.

## Frequently Asked Questions

**How does License Header Injector and Verifier help with legal compliance?**
It automates the process of finding and fixing missing or incorrect copyright notices in your code, making sure every file is properly marked.

**Can I use License Header Injector and Verifier to fix missing copyright notices?**
Yes. You can instruct your agent to scan your files and automatically add the correct header wherever it is missing.

**Does License Header Injector and Verifier detect formatting errors in my files?**
It specifically looks for spacing or character discrepancies that deviate from your established copyright template.

**How do I know if my license template is correct using License Header Injector and Verifier?**
You can run a validation check to ensure your template structure is valid and ready for use across your codebase.

**Is License Header Injector and Verifier compatible with Cursor or Claude?**
Yes. Any MCP-compatible client like Claude, Cursor, or Windsurf can connect to this tool through Vinkius.

**How does the tool handle different years in the copyright notice?**
The system uses Year Agnosticism to recognize valid headers even if the numerical year differs from the template.

**What happens if a header is missing?**
The `apply_license_header` tool follows the Injection Protocol to prepend the template and a newline to the file.

**Can I detect spacing errors in my header?**
Yes, `identify_header_drift` flags any deviation from the Strict Structural Match, including punctuation and spacing.