Tracecat Mcp Community MCP Server

tracecat-mcp-community npm v1.0.0

Published by adrojis — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Tracecat SOAR platform — 49 tools for workflows, actions, cases, secrets, tables, and more

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([tracecat_get_secret]) and tools that can send data out ([tracecat_create_webhook_key]) are exposed together. An agent can move private data to the sink.

Evidence: sources [tracecat_get_secret] → sinks [tracecat_create_webhook_key]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow tracecat_get_secret → tracecat_create_webhook_key

Tools 61

Each tool and what it can reach — statically extracted from the published source.

  • tracecat_create_webhook_keynetwork egress
  • tracecat_get_secretreads sensitive data
  • pingno sensitive capability
  • tracecat_add_commentno sensitive capability
  • tracecat_add_edgesno sensitive capability
  • tracecat_autofix_workflowno sensitive capability
  • tracecat_batch_insert_rowsno sensitive capability
  • tracecat_cancel_executionno sensitive capability
  • tracecat_create_actionno sensitive capability
  • tracecat_create_caseno sensitive capability
Show 51 more tools ↓
  • tracecat_create_columnno sensitive capability
  • tracecat_create_scheduleno sensitive capability
  • tracecat_create_secretno sensitive capability
  • tracecat_create_tableno sensitive capability
  • tracecat_create_workflowno sensitive capability
  • tracecat_delete_actionno sensitive capability
  • tracecat_delete_caseno sensitive capability
  • tracecat_delete_columnno sensitive capability
  • tracecat_delete_edgesno sensitive capability
  • tracecat_delete_rowno sensitive capability
  • tracecat_delete_scheduleno sensitive capability
  • tracecat_delete_secretno sensitive capability
  • tracecat_delete_tableno sensitive capability
  • tracecat_delete_workflowno sensitive capability
  • tracecat_deploy_workflowno sensitive capability
  • tracecat_docsno sensitive capability
  • tracecat_export_workflowno sensitive capability
  • tracecat_get_actionno sensitive capability
  • tracecat_get_caseno sensitive capability
  • tracecat_get_executionno sensitive capability
  • tracecat_get_execution_compactno sensitive capability
  • tracecat_get_graphno sensitive capability
  • tracecat_get_rowno sensitive capability
  • tracecat_get_scheduleno sensitive capability
  • tracecat_get_tableno sensitive capability
  • tracecat_get_templateno sensitive capability
  • tracecat_get_workflowno sensitive capability
  • tracecat_health_checkno sensitive capability
  • tracecat_insert_rowno sensitive capability
  • tracecat_list_actionsno sensitive capability
  • tracecat_list_casesno sensitive capability
  • tracecat_list_commentsno sensitive capability
  • tracecat_list_executionsno sensitive capability
  • tracecat_list_rowsno sensitive capability
  • tracecat_list_schedulesno sensitive capability
  • tracecat_list_tablesno sensitive capability
  • tracecat_list_templatesno sensitive capability
  • tracecat_list_workflowsno sensitive capability
  • tracecat_move_nodesno sensitive capability
  • tracecat_run_workflowno sensitive capability
  • tracecat_search_secretsno sensitive capability
  • tracecat_tools_documentationno sensitive capability
  • tracecat_update_actionno sensitive capability
  • tracecat_update_caseno sensitive capability
  • tracecat_update_rowno sensitive capability
  • tracecat_update_scheduleno sensitive capability
  • tracecat_update_secretno sensitive capability
  • tracecat_update_tableno sensitive capability
  • tracecat_update_trigger_positionno sensitive capability
  • tracecat_update_workflowno sensitive capability
  • tracecat_validate_workflowno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 93/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/tracecat-mcp-community/badge.svg)](https://mcptrustchecker.com/registry/tracecat-mcp-community)
HTML
<a href="https://mcptrustchecker.com/registry/tracecat-mcp-community"><img src="https://mcptrustchecker.com/registry/tracecat-mcp-community/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/tracecat-mcp-community/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan tracecat-mcp-community --online

Use the free API → How scoring works

More in Security & Testing