Skip to main content
Glama
darthzen

fossa-mcp

by darthzen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to fossa-mcp

No user-submitted related servers found.

    Related Servers

    • XFA MCP

      gl-ventures
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query an organization's device posture, compliance, policies, and software/CVE status through a remote, read-only, OAuth-secured MCP endpoint.
      MIT

    • OpenObserve MCP Server

      mdfranz
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to query and explore your OpenObserve observability data. Provides read-only access to logs, metrics, and traces for analysis and troubleshooting.
      5
      MIT

    • SonarQube MCP Server

      anggakawa
      F
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that provides AI assistants with structured access to SonarQube projects, issues, metrics, and rules. It enables safe analysis of code quality and security findings through a set of validated, safety-first tools.
      6
      -

    • platform-mcp-server

      kamroy
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.
      6
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 137 tools

    Disambiguation2/5

    With 137 tools, many share closely related purposes—there are multiple attribution report tools (get, render, email, create-public, release-group variants), numerous export tools with subtle differences (inline vs. emailed vs. queued), and several dependency/package listing tools. The descriptions are individually thorough, but the sheer volume and overlapping names make it hard for an agent to reliably select the right tool without reading every description carefully.

    Naming Consistency4/5

    The vast majority of tools follow a consistent fossa_<verb>_<noun> pattern with clear verbs like list, get, create, update, delete. Minor deviations exist: 'manage' tools bundle multiple actions (fossa_manage_team_group, fossa_manage_role), and a few nouns are plural where singular might be expected (fossa_get_projects_summary, fossa_delete_projects), but the overall convention is strong and predictable.

    Tool Count1/5

    At 137 tools, this far exceeds any reasonable MCP server scope—the calibration guide classifies 50+ as an extreme mismatch. While FOSSA is a broad platform, this tool set tries to expose nearly every API endpoint, resulting in a surface too large for an agent to navigate effectively.

    Completeness4/5

    The tool set covers an enormous range of FOSSA functionality: projects, revisions, dependencies, issues, release groups, teams, roles, users, labels, OIDC, SAML, SBOM sharing, audit logs, and more, with CRUD coverage for most resources. However, there are documented gaps and dead ends, such as no way to poll export jobs, no API to list security policies, and no direct project creation outside of component uploads.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources