Security & Testing

truthsignal.com

Provides tools to search, fetch, and check Truth Signal business legitimacy reports with scores and evidence.

1 endpoint3 known toolsFirst detected October 25, 2026Last detected October 25, 2026

ENDPOINT 1

https://truthsignal.com/mcp

No auth detected

MCP server metadata

Name: Truth Signal
Version: 0.1

Capabilities

tools

Server instructions

Truth Signal reports on whether a business is legitimate and trustworthy, from public evidence: the company register, reviews, domain history, email security, social profiles and breaches. Call check_business with the business's website address, for example johnlewis.com; a business nobody has asked about is checked there and then, usually within 30 seconds, else the answer says pending and when to ask again. Important context: Truth Signal weighs public evidence about this business. A high score means strong evidence that the business is established and legitimate, not a promise that it is safe to buy from or that every purchase will go well. A low score means the evidence is thin or raises concerns, not that the business is unsafe or a scam. Customer satisfaction is reported beside the truth score, not inside it. Cite a report by its citation.cite_as line and its url; the data is CC BY 4.0.

Known tools 3

check_business

Truth Signal's report on a business: is it legit and trustworthy?

Inferred read-only

search

Find the Truth Signal report for the business named in a question, for example "is johnlewis.com legit?": one result, its id the business's domain and its url the report's address.

Inferred read-only

fetch

Read a Truth Signal report by its id, the business's domain, as Markdown: the score, the legitimacy confidence, customer satisfaction, every check with its evidence, and the line to cite it by.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.truth-signal]
url = "https://truthsignal.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "truth-signal": {
      "type": "http",
      "url": "https://truthsignal.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: truth-signal
Remote MCP URL: https://truthsignal.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "truth-signal": {
      "url": "https://truthsignal.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "truth-signal": {
      "type": "http",
      "url": "https://truthsignal.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "truth-signal",
  "transport": "streamable-http",
  "url": "https://truthsignal.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.