Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.RudrenduPaul/truthroute

NPM · TRUTHROUTE-CLI · SCANNED OCT 5

Sends the same prompt to multiple LLM providers in parallel and returns a divergence score via MCP.

Available components

+3 this week 79 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 71 of 184 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 111 tokens (~111/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "compare" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.RudrenduPaul/truthroute MCP server?

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

npm · truthroute-cli

# add to Claude Code
claude mcp add rudrendupaul-truthroute -- npx -y truthroute-cli
// .cursor/mcp.json
{
  "mcpServers": {
    "rudrendupaul-truthroute": {
      "command": "npx",
      "args": [
        "-y",
        "truthroute-cli"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rudrendupaul-truthroute": {
      "command": "npx",
      "args": [
        "-y",
        "truthroute-cli"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rudrendupaul-truthroute -- npx -y truthroute-cli
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rudrendupaul-truthroute": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "truthroute-cli"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rudrendupaul-truthroute --command npx --arg -y --arg truthroute-cli
# ~/.hermes/config.yaml
mcp_servers:
  rudrendupaul-truthroute:
    command: "npx"
    args: ["-y", "truthroute-cli"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rudrendupaul-truthroute": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "truthroute-cli"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rudrendupaul-truthroute -t stdio -c npx -a -y truthroute-cli
// mcp.json
{
  "mcpServers": {
    "rudrendupaul-truthroute": {
      "command": "npx",
      "args": [
        "-y",
        "truthroute-cli"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 +3
    • CVE-2026-24842 no longer affects this package ▲ security
    • CVE-2026-73566 no longer affects this package ▲ security
    • CVE-2026-31802 no longer affects this package ▲ security
    • CVE-2026-53655 no longer affects this package ▲ security
    • CVE-2026-59875 no longer affects this package ▲ security
    • CVE-2026-26960 no longer affects this package ▲ security
    • CVE-2026-59873 no longer affects this package ▲ security
    • CVE-2026-59874 no longer affects this package ▲ security
    • CVE-2026-23950 no longer affects this package ▲ security
    • CVE-2026-23745 no longer affects this package ▲ security
    • CVE-2026-59871 no longer affects this package ▲ security
    • CVE-2026-29786 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
  • 1 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 30 Sept 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Oct 2026 · Analysed npm/truthroute-cli@0.1.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed patch-package

Background: Why install scripts are a supply-chain risk →

Dependencies 184 packages
Packages resolved 184
Deprecated 3
Stale 67
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~111 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare ~111

Sends the same prompt to multiple LLM providers in parallel and returns a divergence score (0.0 = identical meaning, 1.0 = maximally divergent) plus each provider's response. Refusals are excluded from scoring. Requires API keys set as environment variables (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY) for whichever providers are requested.

NameTypeReqDescription
promptstringyesThe prompt to send to all requested providers
providersarrayyesWhich providers to compare

No output schema declared.

No examples provided.

Common questions

What is the io.github.RudrenduPaul/truthroute MCP server?

io.github.RudrenduPaul/truthroute is an MCP server listed in the public MCP registry as io.github.RudrenduPaul/truthroute. Sends the same prompt to multiple LLM providers in parallel and returns a divergence score via MCP. This page covers its npm package (truthroute-cli).

Is the io.github.RudrenduPaul/truthroute MCP server safe to use?

io.github.RudrenduPaul/truthroute scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 October 2026. 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 io.github.RudrenduPaul/truthroute MCP server expose?

io.github.RudrenduPaul/truthroute exposes 1 tool: compare. Their descriptions and schemas cost roughly 111 tokens of context every time the server is loaded.

Is the io.github.RudrenduPaul/truthroute MCP server still maintained?

io.github.RudrenduPaul/truthroute is still listed as active in the MCP registry. We last reached this channel on 5 October 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 io.github.RudrenduPaul/truthroute MCP server under?

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