MCP Server for Dependency Track

### Current Behavior

Currently, extracting analytics and performing automated actions in Dependency Track requires either:
1. Manual navigation through the UI, or
2. Writing custom scripts that hit multiple API endpoints and transform data

This creates friction for teams wanting to:
- Generate portfolio-wide reports
- Perform ad-hoc actions on DT
- Query security posture using natural language

### Proposed Behavior

Develop an MCP server that wraps Dependency Track's REST API, enabling:

**Natural language interactions** with DT data via LLM tools (Claude, etc.):
- "Show me all critical vulnerabilities in projects"
- "Generate a summary of component license risks across the portfolio / particular project/component"
- "What's the current remediation status for CVE-2024-XXXX?"

We already have a rich rest api documentation.

1. Should we create this MCP wrapper? What are the community views?
2. Are there API limitations or security concerns we should address?

- Model Context Protocol: https://modelcontextprotocol.io/

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this enhancement was already requested