Access and manage your VISO TRUST third-party risk program directly through your AI assistant.
Viso trust mcp server lets Claude, Cursor and other MCP clients work with VISO TRUST directly. Access and manage your VISO TRUST third-party risk program directly through your AI assistant.
A Model Context Protocol (MCP) server for integrating VISO TRUST API capabilities with AI assistants.
Once connected, the assistant can call these 12 tools directly:
visotrust.api.base-url — The base URL for the VISO TRUST API (default: http://localhost:8080)visotrust.api.token — Your API token from the VISO TRUST platform (required)visotrust.api.timeout — API request timeout in milliseconds (default: 30000)visotrust.api.connect-timeout — API connection timeout in milliseconds (default: 5000)Debugging — The Debugging tool exposed by this serverLint — Checks code formatting using Spotless: bash ./gradlew spotlessCheckBuild — Builds the application and creates a JAR file: bash ./gradlew buildPublish — When a new release is created: 1. Updates the project version in build.gradle to match the release tag 2. Uploads the JAR file to the GitHub release with theAssessments — The Assessments tool exposed by this serverRelationships — The Relationships tool exposed by this serverWebhooks — The Webhooks tool exposed by this serverget_all_we — The get_all_we tool exposed by this serverThe server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 4 environment variables: VISOTRUST_API_BASEURL, VISOTRUST_API_TOKEN, JAVA_TOOL_OPTIONS, DOCKERHUB_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. VISO TRUST sits in that group, and the shape of its toolset — visotrust.api.base-url, visotrust.api.token, visotrust.api.timeout among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| visotrust.api.base-url | The base URL for the VISO TRUST API (default: http://localhost:8080) |
| visotrust.api.token | Your API token from the VISO TRUST platform (required) |
| visotrust.api.timeout | API request timeout in milliseconds (default: 30000) |
| visotrust.api.connect-timeout | API connection timeout in milliseconds (default: 5000) |
| Debugging | The Debugging tool exposed by this server. |
| Lint | Checks code formatting using Spotless: bash ./gradlew spotlessCheck |
| Build | Builds the application and creates a JAR file: bash ./gradlew build |
| Publish | When a new release is created: 1. Updates the project version in build.gradle to match the release tag 2. Uploads the JAR file to the GitHub release with the version from the release tag 3. Builds and pushes the Docker i |
| Assessments | The Assessments tool exposed by this server. |
| Relationships | The Relationships tool exposed by this server. |
| Webhooks | The Webhooks tool exposed by this server. |
| get_all_we | The get_all_we tool exposed by this server. |
#### Java Configuration
```json
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| VISOTRUST_API_BASEURL | Endpoint or connection string the server talks to. | Yes |
| VISOTRUST_API_TOKEN | Credential the server authenticates with. | Yes |
| JAVA_TOOL_OPTIONS | Configuration value read at startup. | Optional |
| DOCKERHUB_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.