4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
FOSSA (License Compliance) MCP Server

Bring Open Source
to VS Code Copilot

Learn how to connect FOSSA (License Compliance) to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Check VulnerabilitiesGet Parent ProjectsGet RevisionGet Revision DependenciesList ProjectsList Revisions

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
FOSSA (License Compliance)

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

  1. Subscribe to this server
  2. Enter your FOSSA API Token
  3. 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)

check_vulnerabilities

Uses a POST request but only reads data. Check vulnerabilities by dependency locators

get_parent_projects

Get parent projects containing a dependency

get_revision

Get details for a specific revision

get_revision_dependencies

Get dependencies for a specific revision

list_projects

Supports filtering and pagination. List all projects in your organization

list_revisions

List revisions of a project

Why VS Code Copilot?

GitHub Copilot Agent mode brings FOSSA (License Compliance) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

FOSSA (License Compliance) in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

FOSSA (License Compliance) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect FOSSA (License Compliance) to VS Code Copilot 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for FOSSA (License Compliance) in VS Code Copilot

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 VS Code Copilot 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.

FOSSA (License Compliance)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures FOSSA (License Compliance) for VS Code Copilot

Every tool call from VS Code Copilot to the FOSSA (License Compliance) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →