truss-agent-mcp
Truss threat intelligence via Model Context Protocol and a terminal assistant — one binary: truss-mcp.
Agenten stärken
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
https://api.truss-security.com/mcpDie Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
claude mcp add --transport http com.truss-security-truss-mcp https://api.truss-security.com/mcpRun in a terminal.
{ "mcpServers": { "com.truss-security-truss-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.truss-security.com/mcp" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Truss threat intelligence via Model Context Protocol and a terminal assistant — one binary: truss-mcp.
Query Truss threat intelligence via hosted MCP (OAuth). Growth+ plans.
Hosted MCP (OAuth, Growth+ gate, five tools) is served by the Truss API. This package ships configs, validate-remote / doctor --remote, CLI search, and optional local stdio. Community accounts cannot consent to hosted MCP.
Not on npm yet. Install from this repo (
npm install -g .). After publish:npm install -g @truss-security/truss-agent-mcp.
cd truss-agent-mcp
npm install && npm run build
npm install -g .
truss-mcp doctor --remote --strict-oauth # OAuth path hosts use
truss-mcp init # for CLI search / legacy stdio
truss-mcp search
Node.js 18+. Binary name truss-mcp avoids conflict with @truss-security/truss-sdk's truss command.
One REPL with MCP tools always connected. The assistant classifies your intent and asks before querying Truss API:
run executes confirmed filter (default 7 days)stix for STIX export; JSON summaries in-threaddetect splunk, detect falcon, detect cortex from search resultsThe assistant offers next steps explicitly: build a filter, refine it, query Truss API, export JSON/STIX, or generate SIEM/EDR hunting queries.
run 30, days 30) may use more API quotaFull REPL reference: guides/truss-cli.md
truss-mcp search uses color-coded, ASCII-bordered output:
→ search_threats on remote, or → search_products on stdio)Controls: color / color on / color off / color auto · env TRUSS_MCP_COLOR · standard NO_COLOR=1
No API key in host config. Growth+ Truss account; browser OAuth consent.
{
"mcpServers": {
"truss-mcp": {
"url": "https://api.truss-security.com/mcp"
}
}
}
Samples: config/cursor.mcp.json · config/claude_desktop_config.json · guides/client-setup-cursor.md.
{
"mcpServers": {
"truss-mcp": {
"command": "truss-mcp",
"args": ["mcp"],
"env": { "TRUSS_API_KEY": "YOUR_KEY" }
}
}
}
Use as the OAuth + MCP doctor before registry publish or release. After OAuth it requires search_threats to return at least one Truss product (id + title). The access token stays in memory for that process only unless you pass --save-token.
truss-mcp doctor --remote --strict-oauth
# or:
truss-mcp validate-remote https://api.truss-security.com/mcp --strict-oauth
After token exchange it prints an OAuth compatibility checklist (resource URI, redirects, PKCE S256, issuer match, audience vs MCP resource, truss_role), then proves MCP access with real Truss data.
Options:
truss-mcp validate-remote https://api.truss-security.com/mcp --verbose
truss-mcp validate-remote https://api.truss-security.com/mcp --strict-oauth
truss-mcp validate-remote https://api.truss-security.com/mcp --save-token /tmp/truss-mcp-token
truss-mcp validate-remote https://api.truss-security.com/mcp --token-file /tmp/truss-mcp-token
truss-mcp validate-remote https://api.truss-security.com/mcp --port 9877
truss-mcp validate-remote https://api.truss-security.com/mcp --no-open
--verbose — HTTP statuses, key headers, truncated bodies (tokens redacted)--strict-oauth — exit 2 if the OAuth checklist has WARN/FAIL (even when Truss MCP calls succeed)--save-token PATH — write the access token for local replay (mode 0600; delete after debugging)--token-file PATH — skip browser OAuth; reuse a saved token to re-check MCP access + Truss dataOptional automated OAuth data tests (saved token + TRUSS_RUN_MCP_OAUTH=1) are documented in guides/publishing.md.
Official listing: server.json (com.truss-security/truss-mcp) · Tracker: guides/registry-submission.md · Internal metadata: config/mcp-registry.json · Architecture: docs/05-hosted-mcp-oauth-architecture.md
Env load order (shell vars win): ~/.config/truss/env → ~/.truss/.env → ./.env
Full list: env.example
Guides — install, REPL, MCP clients, FilterQL examples
Reference — API contract, tools, architecture (docs/README.md — docs 01–06)
npm install && npm run build
npm test
npm run truss:search # from source without global install
Contributors / AI agents: see AGENTS.md for repo operations and conventions.
Publish: guides/publishing.md · Changes: CHANGELOG.md
MIT
Query Truss threat intelligence via hosted MCP (OAuth). Growth+ plans.
{ "mcpServers": { "com.truss-security-truss-mcp": { "url": "https://api.truss-security.com/mcp", "headers": {} } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Truss Threat Intelligence wird über HTTP erreicht.
Zuletzt geprüft: 2026-11-08. Query Truss threat intelligence via hosted MCP (OAuth). Growth+ plans.