# TruthTrail (npm · truthtrail)

Record the decisions your AI coding agent makes, in the repo and on the Jira or GitHub ticket.

- Trust score: 63/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `truthtrail`: 63/100 (this document), [markdown](https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail.md), [page](https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail)

## Channel facts

- Registry: `npm`
- Package: `truthtrail`
- Version: `0.4.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 758 tokens (~84/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "withdraw_decision" implies "withdraw" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the TruthTrail MCP server?

TruthTrail runs locally as an npm package, launched with npx -y truthtrail mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add truthtrail-truthtrail -- npx -y truthtrail mcp
```

### Cursor

```json
{
  "mcpServers": {
    "truthtrail-truthtrail": {
      "command": "npx",
      "args": [
        "-y",
        "truthtrail",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "truthtrail-truthtrail": {
      "command": "npx",
      "args": [
        "-y",
        "truthtrail",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add truthtrail-truthtrail -- npx -y truthtrail mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "truthtrail-truthtrail": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "truthtrail",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add truthtrail-truthtrail --command npx --arg -y --arg truthtrail --arg mcp
```

### Hermes

```yaml
mcp_servers:
  truthtrail-truthtrail:
    command: "npx"
    args: ["-y", "truthtrail", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "truthtrail-truthtrail": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "truthtrail",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add truthtrail-truthtrail -t stdio -c npx -a -y truthtrail mcp
```

### Other

```json
{
  "mcpServers": {
    "truthtrail-truthtrail": {
      "command": "npx",
      "args": [
        "-y",
        "truthtrail",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-13 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-12 (score 48)

First indexed and scored.

## MCP tools (9)

### `record_decision` (~215 tokens)

Record a product decision or assumption for the current ticket. Use it when the ticket was silent or ambiguous and the choice changes behaviour a user or QA can see, when following the ticket would break something, or when you assumed something visible (type: assumption). Not for pure implementation details.

Input parameters:

- `approver` (string): Only if the user explicitly named who approved it. Never guess.
- `body` (string): Short extra explanation
- `chosen` (string, required): What was picked
- `files` (array): Files this decision affects
- `options` (array): The choices that were considered
- `question` (string, required): What needed deciding, e.g. 'Discount before or after tax?'
- `reason` (string): Why it was chosen
- `supersedes` (array): Ids of older decisions this replaces
- `ticket` (string): Ticket key; defaults to the key in the branch name
- `type` (string): decision (default), assumption (you assumed it without asking), or impact

### `list_decisions` (~38 tokens)

List recorded decisions (optionally for one ticket). Read these before implementing or testing a ticket and follow them.

Input parameters:

- `ticket` (string)

### `why` (~45 tokens)

Explain a file or line: last commit, AI or human authorship, linked decisions and the ticket.

Input parameters:

- `target` (string, required): file or file:line, relative to the workspace

### `check_branch` (~41 tokens)

Check this branch: ticket key, decisions and assumptions recorded, AI-assisted commits, and reminders.

Input parameters:

- `base` (string): branch to compare against (default main)

### `list_pending` (~23 tokens)

Questions the user answered during this work that are not yet recorded or dismissed.

### `resolve_pending` (~202 tokens)

Resolve a pending answered question: action 'record' if it changes behaviour a user or QA can see (fields override the captured values), otherwise 'dismiss'.

Input parameters:

- `action` (string, required)
- `approver` (string): Only if the user explicitly named who approved it. Never guess.
- `body` (string): Short extra explanation
- `chosen` (string): What was picked
- `files` (array): Files this decision affects
- `index` (integer, required)
- `options` (array): The choices that were considered
- `question` (string): What needed deciding, e.g. 'Discount before or after tax?'
- `reason` (string): Why it was chosen
- `supersedes` (array): Ids of older decisions this replaces
- `ticket` (string): Ticket key; defaults to the key in the branch name
- `type` (string): decision (default), assumption (you assumed it without asking), or impact

### `set_ticket` (~71 tokens)

Remember which ticket this branch belongs to, when the branch name has no ticket key or the wrong one. Ask the user for the key first; never guess. Returns the ticket's title so you can check it matches the task.

Input parameters:

- `ticket` (string, required): Ticket key, e.g. ABC-1234

### `move_decision` (~68 tokens)

Move a decision you recorded to the right ticket (it was recorded on a wrong one). It is withdrawn on the old ticket with 'moved to <TICKET>'.

Input parameters:

- `id` (string, required): D-12 or the long id
- `ticket` (string, required): The right ticket key

### `withdraw_decision` (~55 tokens)

Withdraw a decision you recorded (for example, recorded by mistake). Needs TruthTrail login. To change a decision, record a new one with supersedes instead.

Input parameters:

- `id` (string, required): D-12 or the long id

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail#diagnostics

## Score history

- 2026-11-21: 63
- 2026-11-20: 63
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 63
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 48

## Common questions

### What is the TruthTrail MCP server?

TruthTrail is an MCP server listed in the public MCP registry as io.github.truthtrail/truthtrail. Record the decisions your AI coding agent makes, in the repo and on the Jira or GitHub ticket. This page covers its npm package (truthtrail).

### Is the TruthTrail MCP server safe to use?

TruthTrail scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TruthTrail MCP server expose?

TruthTrail exposes 9 tools: record_decision, list_decisions, why, check_branch, list_pending, and 4 more. Their descriptions and schemas cost roughly 758 tokens of context every time the server is loaded.

### Is the TruthTrail MCP server still maintained?

TruthTrail is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the TruthTrail MCP server under?

TruthTrail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the TruthTrail MCP server?

VerifyMCP ran 14 checks on TruthTrail, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about TruthTrail: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/truthtrail
- Socket report: https://socket.dev/npm/package/truthtrail
- Website: https://truthtrail.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail.xml
- Changelog JSON feed: https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail.json
- HTML version of this page: https://verifymcp.io/servers/truthtrail-truthtrail/truthtrail
