VISO TRUST

You can run the VISO TRUST MCP Server to bridge VISO TRUST API capabilities with AI assistants through a Model Context Protocol (MCP) interface. It supports local stdio and remote HTTP/SSE usage, making it suitable for both on‑premise deployments and cloud setups. Configure the API token and base URL, then start the server and connect your MCP client to exchange prompts and responses with the VISO TRUST platform.

How to use

Choose your preferred deployment method and start the MCP Server. If you run locally for direct stdio interactions, you will typically start the server as a Java process or via a container, and then configure your MCP client to point to localhost on the specified port. If you deploy remotely, you run the server in a container or on a remote host and connect clients over HTTP/SSE or standard MCP channels.

How to install

Prerequisites you need before starting: Java 21 or newer, Gradle, and Docker (optional for containerized deployment). You may also use a local Gradle build to produce a runnable JAR.

Install via Docker (recommended for quick setup)

run -i --rm \
  -e VISOTRUST_API_TOKEN=<your-api-token> \
  -e VISOTRUST_API_BASEURL=https://app.visotrust.com \
  visotrustai/viso-mcp-server:latest

Install via Java (manual start from jar)

{"mcpServers": {
  "viso_mcp": {
    "command": "java",
    "args": ["-jar", "viso-mcp-server-<version>.jar", "--port", "8080", "--host", "localhost"],
    "env": {
      "JAVA_TOOL_OPTIONS": "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005",
      "VISOTRUST_API_TOKEN": "<your-api-token>",
      "VISOTRUST_API_BASEURL": "https://app.visotrust.com"
    }
  }
}}

Build from source and run locally

If you prefer building from source, use Gradle to assemble a runnable JAR and start it with the Java command shown above. The typical flow is to build first, then run the generated JAR with the appropriate port/host options and API credentials.

Configure API access

Set these environment variables for the MCP Server to authenticate with the VISO TRUST API and to define where the server is reachable by clients.

Remote vs local profiles

If you are deploying to a remote environment and want HTTP/SSE communication, use the remote (SSE-enabled) profile. For local development and direct stdio communication, use the default profile. Activate the remote profile when starting the server with the appropriate flag in your Java or container command.

Security and credentials

Protect your API token and base URL. Do not commit tokens to source control. Use secret management in your deployment environment and restrict API token scope to the minimum required permissions.

Notes and tips

• When running in Docker, supply VISOTRUST_API_TOKEN and VISOTRUST_API_BASEURL as environment variables. - When running from a JAR, ensure the port and host you expose match your MCP client configuration. - For remote deployments, monitor logs for connection health and ensure the remote endpoint is reachable by clients.

Additional configuration and usage details

The server exposes a comprehensive set of tools for assessments, audits, business cases, data types, queries, relationships, webhooks, intelligence reports, and user management. Each tool has a defined input model and returns detailed results. Use the MCP client to call these tools with the required parameters as you manage relationships, assess vendors, and fetch intelligence.

Available tools

get_assessment

Retrieve detailed information about a specific assessment by its ID.

create_assessment

Start a new assessment for a given relationship, including recipient details and optional documents.

get_assessment_summary

Obtain a summary for a specific assessment by its ID.

get_user_audit_log_events

Fetch audit log events for the organization within a specified date range.

get_all_business_cases

List all available business cases for the organization.

get_all_datatypes

List all data types available to the organization.

ask_trust_center

Ask questions about the AI Trust Center and receive AI-generated responses.

ask_relationship

Query information about a specific relationship using its ID.

get_all_relationships

Retrieve all relationships with their associated assessment details.

get_relationship_by_id

Get a specific relationship and its assessment details by ID.

create_relationship

Create a new relationship with a third-party vendor.

update_relationship

Update an existing relationship with new details.

partially_update_relationship

Partially update an existing relationship by changing select fields.

search_relationships

Search for relationships by domain name or vendor name.

create_tags

Create new tags for categorizing relationships.

update_third_party_contact

Update the contact details for a vendor relationship.

get_suggested_contacts

Get suggested contacts for a vendor relationship.

get_relationship_assessment_history

Retrieve the assessment history for a relationship.

create_relationship_by_domain

Create a new relationship using only the vendor domain.

get_all_webhooks

Get all webhook configurations.

get_webhook

Get a webhook configuration by ID.

create_webhook_configuration

Create a webhook configuration with URL, secret, and event types.

update_webhook_configuration

Update an existing webhook configuration.

delete_webhook_configuration

Delete a webhook configuration.

create_bitsight_intelligence_report

Create a new BitSight intelligence report for a vendor.

create_security_scorecard_intelligence_report

Create a new SecurityScorecard intelligence report for a vendor.

get_intelligence_reports_by_vendor

Get all intelligence reports for a specific vendor.

get_latest_intelligence_report

Get the latest intelligence report for a vendor from a specific source.

get_all_users

Retrieve a paginated list of users in the organization.

get_user_by_email

Get a user by email address.

create_user

Create a new user with email and name details.