Compatible with every major AI agent and IDE
What is the FOSSA (License Compliance) MCP Server?
Connect your FOSSA account to any AI agent to automate open-source license compliance and security auditing through natural language.
What you can do
- Project Overview — List all projects in your organization with support for filtering and pagination.
- Revision Tracking — Access specific project revisions and fetch detailed metadata for any version locator.
- Dependency Analysis — Deep-dive into the dependency tree of any revision to understand your software bill of materials (SBOM).
- Impact Assessment — Identify every parent project that contains a specific vulnerable or non-compliant dependency.
- Vulnerability Scanning — Check for security vulnerabilities across multiple dependency locators in a single query.
How it works
- Subscribe to this server
- Enter your FOSSA API Token
- Start auditing your software supply chain from Claude, Cursor, or any MCP client
Who is this for?
- Security Engineers — quickly identify where vulnerable packages are used across the entire organization.
- Legal & Compliance Teams — audit project revisions for license compliance without manually navigating the FOSSA UI.
- DevOps & Architects — verify dependency trees and project metadata directly from the terminal or code editor.
Built-in capabilities (6)
Uses a POST request but only reads data. Check vulnerabilities by dependency locators
Get parent projects containing a dependency
Get details for a specific revision
Get dependencies for a specific revision
Supports filtering and pagination. List all projects in your organization
List revisions of a project
Why Cursor?
Cursor's Agent mode turns FOSSA (License Compliance) into an in-editor superpower. Ask Cursor to generate code using live data from FOSSA (License Compliance) and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
FOSSA (License Compliance) in Cursor
FOSSA (License Compliance) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect FOSSA (License Compliance) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FOSSA (License Compliance) in Cursor
The FOSSA (License Compliance) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FOSSA (License Compliance) for Cursor
Every tool call from Cursor to the FOSSA (License Compliance) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I find which projects are affected by a specific vulnerable package?
Yes. Use the get_parent_projects tool with the dependency locator (e.g., npm+coa$2.0.2) to see every project in your organization that includes that specific dependency.
How do I check for security vulnerabilities in a list of dependencies?
You can use the check_vulnerabilities tool by providing an array of dependency locators. The agent will return any known security issues impacting those specific versions.
Can I see the full dependency list for a specific project version?
Absolutely. By using get_revision_dependencies with a revision locator, you can retrieve the complete list of dependencies identified by FOSSA for that specific build or release.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Landbot
8 toolsEmpower your AI to generate, route, and interact with conversational chatbots and customers naturally.

Mirakl (Enterprise Marketplace Platform)
10 toolsManage your enterprise marketplace via Mirakl — list global offers, track multi-vendor orders, and audit seller shops.

Eventbrite
12 toolsCreate events, sell tickets, and manage attendees with the world largest self-service ticketing platform for any occasion.

Pipedream
7 toolsManage Pipedream serverless workflows, sources, webhooks, and raw event data natively via AI agents.
