MCPHub LabRegistryguacsec/trustify
guacsec

guacsec/trustify

Built by guacsec • 47 stars

What is guacsec/trustify?

A high-performance MCP server implementation for guacsec/trustify that bridges the gap between the Model Context Protocol and external services. It allows Large Language Models to interact with your data and tools with low latency and native support.

How to use guacsec/trustify?

1. Ensure you have an MCP-compatible client (like Claude Desktop) installed. 2. Configure your server with: npx @modelcontextprotocol/guacsec/trustify 3. Restart your client and verify the new tools are available in the system catalog.
🛡️ Scoped (Restricted)
npx @modelcontextprotocol/guacsec-trustify --scope restricted
🔓 Unrestricted Access
npx @modelcontextprotocol/guacsec-trustify

Key Features

Native MCP Protocol Support
High-performance Data Streaming
Type-safe Tool Definitions
Seamless Environment Integration

Optimized Use Cases

Connecting external databases to AI workflows
Automating workflow tasks via natural language
Augmenting developer productivity with specialized tools

guacsec/trustify FAQ

Q

What is an MCP server?

MCP is an open standard that enables developers to build secure, two-way integrations between AI models and local or remote data sources.

Q

Is this server ready for production?

Yes, this server follows standard MCP security patterns and tool-restricted access.

Official Documentation

View on GitHub

Trustify

CI License GitHub Release

The open-source platform for software supply chain security.

Trustify brings SBOMs, vulnerability advisories, and VEX documents into a single searchable system — so you can understand what's in your software and respond to threats in minutes, not days.

Why Trustify

Unified SBOM ManagementIngest, store, and search CycloneDX and SPDX SBOMs in one place
Vulnerability IntelligenceCross-reference SBOMs against advisories from Red Hat, GHSA, NVD, and OSV
VEX SupportReduce alert fatigue with vendor vulnerability exploitability data (CSAF/VEX)
Built-in ImportersAutomatically fetch and stay current with public vulnerability feeds
REST API & Web UIFull API with OpenAPI spec, plus a modern web interface
Single Binary DeploymentOne binary, one PostgreSQL database — no microservices to wrangle

See It In Action

<!-- TODO: Add screenshot of the Trustify dashboard showing SBOM search results --> <!-- Recommended: 1200x700px PNG, dark and light variants if possible -->

Trustify Sboms Trustify Importers

Quick Start

Option 1: Download a release

Download the latest trustd-pm binary from Releases, then:

AUTH_DISABLED=true ./trustd-pm

Option 2: Build from source

AUTH_DISABLED=true cargo run --bin trustd

This starts Trustify in "PM mode" — an embedded PostgreSQL database is created in .trustify/ in your current directory. No external setup needed.

Load sample data

cd etc/datasets && make
curl -X POST http://localhost:8080/api/v3/dataset --data-binary @ds1.zip \
  -H "Content-Type: application/zip"

Note: PM mode requires IPv6 enabled with localhost resolving to ::1.

Nightly Builds

A rolling nightly build is published from the latest main commit each day by the nightly workflow. Runs are skipped when main has not changed since the previous nightly or when CI has not passed. A manual run can rebuild unchanged main, but still requires CI to pass.

  • Binaries: Nightly release
  • Container images: ghcr.io/guacsec/trustd:nightly, ghcr.io/guacsec/xtask:nightly, and ghcr.io/guacsec/gensbom:nightly. Each build also has a date-and-commit-specific tag.

Not for production use. Nightly builds are experimental and unsupported. They may be unstable or include breaking changes, including database migrations that can make existing data incompatible. Use a stable, versioned release for production deployments.

Key Concepts

TermWhat it means in Trustify
SBOMA software bill of materials (CycloneDX or SPDX) describing the components in a software product
AdvisoryA security advisory (e.g. from NVD, Red Hat, GHSA) describing vulnerabilities in specific packages
VEXVendor exploitability exchange — a statement from a vendor about whether a vulnerability actually affects their product
pURLPackage URL — a standard way to identify a software package across ecosystems
CPECommon Platform Enumeration — an identifier for products, used in NVD advisories
CVEA unique identifier for a publicly known security vulnerability

Contributing

We welcome contributions! To get started:

  1. Install Rust
  2. Start PostgreSQL: podman-compose -f etc/deploy/compose/compose.yaml up
  3. Run the tests: cargo test

See CONVENTIONS.md for coding standards and docs/ for architecture decisions, OIDC setup, and deployment guides.

Ecosystem

RepositoryDescription
trustify-uiWeb interface
trustify-helm-chartsHelm charts for Kubernetes deployment
trustify-mcpMCP server for AI/LLM integration
trustify-load-test-runsScale test runner and results
scale-testingScale test suite
trustify-release-toolsRelease automation

Architecture

Trustify uses a modulith architecture — a single deployable binary backed by PostgreSQL.

  • REST API for ingesting and querying supply-chain data
  • Built-in importers that fetch public vulnerability feeds on a schedule
  • Extensible data model supporting SBOMs, advisories, VEX, pURLs, and CPEs
  • OIDC authentication with optional dev/test bypass

Architecture

License

Apache-2.0 — see LICENSE for details.

Global Ranking

4.7
Trust ScoreMCPHub Index

Based on codebase health & activity.

Manual Config

{ "mcpServers": { "guacsec-trustify": { "command": "npx", "args": ["guacsec-trustify"] } } }