Enables AI assistants to search vendor trust centers, analyze SOC 2 reports, and request access to security documentation.
Also known as trustlists/trustlists-plugin, mcp, @trustlists/mcp
- Stars
- 0
- Tools
- 6
- Downloads, 30 days
- —
- Latest version
- 0.4.1
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is trustlists MCP?
trustlists enables AI assistants to search vendor trust centers, analyze SOC 2 reports, and request access to security documentation. It exposes 6 tools, such as trustlists_search, trustlists_lookup, trustlists_browse.
Summary generated from the project's README
About trustlists MCP server
Automating vendor security research and documentation requests from within your AI coding environment is what this server enables. Developers and security teams can use it to search thousands of vendor trust centers by name or domain or filter them by specific frameworks and CSA STAR levels. It works locally via npx through clients like Claude Desktop or Cursor.
Users can perform deeper security tasks by signing in with a device code to access account-based tools. This allows for analyzing local SOC 2 PDF files or requesting access to vendor portals like SafeBase and Vanta. The server also includes a specialized tool to map project manifests from languages like Python, Go, Rust, and JavaScript to their corresponding public vendor trust centers.
While free tools allow for searching and browsing, advanced features like batch access requests for up to five vendors require an account. The system manages credentials locally in an auth.json file to maintain session state during security audits and documentation workflows.
What you can do with it
- 1Audit project dependencies for securityMap your project's manifest files to their respective vendor trust centers to check security status.
- 2Analyze SOC 2 compliance documentsReview and analyze local SOC 2 PDF reports to extract security insights.
- 3Request vendor security documentationSubmit access requests to platforms like SafeBase or Vanta for specific vendors.
- 4Search for vendor trust centersFind security information for a specific company using their domain name.
Written from the project's README. Every use case is checked against a quote from it.
How to install trustlists MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall trustlists MCP in Claude Code
$ claude mcp add mcp -- npx -y @trustlists/mcpInstall trustlists MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@trustlists/mcp"
]
}
}
}Install trustlists MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@trustlists/mcp"
]
}
}
}Install trustlists MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@trustlists/mcp"]}'Install trustlists MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@trustlists/mcp"
]
}
}
}Install trustlists MCP in Codex
$ codex mcp add mcp -- npx -y @trustlists/mcpInstall trustlists MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@trustlists/mcp"]
Install trustlists MCP in Gemini CLI
$ gemini mcp add -s user mcp npx -- -y @trustlists/mcpInstall trustlists MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@trustlists/mcp"
]
}
}
}trustlists MCP tools 6
Detected from the READMEtrustlists_searchtrustlists_lookuptrustlists_browsetrustlists_audit_dependenciestrustlists_requester_profiletrustlists_access_request_batch
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachabletrustlists/trustlists-plugin is public and reachablegithub.com/trustlists/trustlists-plugin ↗Pass
- Package names this repository as its source@trustlists/mcp names trustlists/trustlists-plugin as sourcenpmjs.com/package/@trustlists/mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @trustlists/mcpnpmjs.com/package/@trustlists/mcp/v/0.3.0#provenance ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-03github.com/trustlists/trustlists-plugin ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @trustlists/mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@trustlists/mcp
MCP server that gives AI assistants access to the public trustlists directory, plus signed-in SOC 2 analysis and trust-center access requests.
This npm package powers the trustlists_ plugin for Cursor, Claude Code, and other Model Context Protocol clients.
Installation
You don't install this package directly. It is spawned by your MCP-aware AI client.
Cursor
The trustlists_ plugin handles installation. Or add it manually to
~/.cursor/mcp.json:
{
"mcpServers": {
"trustlists": {
"command": "npx",
"args": ["-y", "@trustlists/mcp"]
}
}
}
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"trustlists": {
"command": "npx",
"args": ["-y", "@trustlists/mcp"]
}
}
}
Tools
Free (no account)
| Tool | Description |
|---|---|
trustlists_search |
Search thousands of trust centers by name or domain |
trustlists_lookup |
Look up a single vendor by exact domain |
trustlists_browse |
Filter by platform, listed framework, or CSA STAR level |
trustlists_audit_dependencies |
Map project manifests to public vendor trust centers |
Account
Sign in with trustlists_login (device code). Credentials are stored in
~/.trustlists/auth.json on this machine. The hosted endpoint at
mcp.trustlists.org/mcp serves these tools after an OAuth sign-in instead, with
SOC 2 uploads in the trustlists app (trustlists_soc2_upload) in place of local
PDF paths.
| Tool | Description |
|---|---|
trustlists_login / logout / whoami |
Device-code sign-in and session |
trustlists_soc2_analyze / status / report |
Analyze local SOC 2 PDFs (preview, then confirmCredits) |
trustlists_requester_profile |
Identity used on vendor access forms |
trustlists_access_request / status / continue |
Request SafeBase/Vanta access (preview, then confirm) |
trustlists_access_request_batch |
Same, up to 5 vendors, one confirm |
Directory labels show what a public record lists. They do not independently prove certification scope, validity, legal compliance, or security quality.
Supported manifest formats (audit tool)
package.json(npm/yarn/pnpm)requirements.txt,pyproject.toml,Pipfile(Python)go.mod(Go)Cargo.toml(Rust)Gemfile(Ruby)composer.json(PHP)
License
Apache 2.0. See LICENSE and NOTICE.
Links
trustlists MCP questions
How do I add trustlists MCP to Claude Code?
Run claude mcp add mcp -- npx -y @trustlists/mcp in your terminal. Add --scope user to make it available in every project.
How do I add trustlists MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does trustlists MCP provide?
It exposes 6 tools, including trustlists_search, trustlists_lookup, trustlists_browse, trustlists_audit_dependencies, trustlists_requester_profile.
Which programming language manifest formats are supported for dependency auditing?
The tool supports package.json (npm/yarn/pnpm), Python (requirements.txt, pyproject.toml, Pipfile), Go (go.mod), Rust (Cargo.toml), Ruby (Gemfile), and PHP (composer.json).
How do I sign in to access account-based tools?
You can sign in using the trustlists_login tool via device code, and credentials will be stored locally in ~/.trustlists/auth.json.