4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
FOSSA (License Compliance) MCP Server

Bring Open Source
to Claude Desktop

Learn how to connect FOSSA (License Compliance) to Claude Desktop 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 Claude Desktop?

Claude Desktop is the definitive way to connect FOSSA (License Compliance) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

FOSSA (License Compliance) in Claude Desktop

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 Claude Desktop 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 Claude Desktop

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 Claude Desktop 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 Claude Desktop

Every tool call from Claude Desktop 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

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →