# Trooth (remote · api.trooth.co)

Trooth is an infrastructure and cybersecurity company providing Machine-Readable Trust.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `api.trooth.co`: 80/100 (this document), [markdown](https://verifymcp.io/servers/troothllc-trooth-network/public-mcp.md), [page](https://verifymcp.io/servers/troothllc-trooth-network/public-mcp)

## Channel facts

- Endpoint: `https://api.trooth.co/public/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 972 tokens (~121/item across 8 items; 4 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

Trooth is a hosted endpoint at https://api.trooth.co/public/mcp, so there is nothing to install locally. 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 --transport http troothllc-trooth-network 'https://api.trooth.co/public/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "troothllc-trooth-network": {
      "url": "https://api.trooth.co/public/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "troothllc-trooth-network": {
      "type": "http",
      "url": "https://api.trooth.co/public/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.troothllc-trooth-network]
url = "https://api.trooth.co/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "troothllc-trooth-network": {
      "type": "remote",
      "url": "https://api.trooth.co/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add troothllc-trooth-network --url 'https://api.trooth.co/public/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  troothllc-trooth-network:
    url: "https://api.trooth.co/public/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "troothllc-trooth-network": {
      "Transport": "http",
      "Url": "https://api.trooth.co/public/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add troothllc-trooth-network -t streamable-http -u 'https://api.trooth.co/public/mcp'
```

### Other

```json
{
  "mcpServers": {
    "troothllc-trooth-network": {
      "type": "http",
      "url": "https://api.trooth.co/public/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-03 (score 80, +1)

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

### 2026-09-30 (score 79, +1)

- [security] Tool “trooth_public_trust_profile” rewrote its description, which is the text the model reads

### 2026-09-28 (score 78, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “trooth_verify” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 829 → 948
- [functional improvement] Stability: unverified → 0.03
- [functional] New resource “What each tool call sends, and what Trooth keeps”

### 2026-09-26 (score 77)

First indexed and scored.

## MCP tools (4)

### `trooth_ask` (~89 tokens)

Answer a question about Trooth itself (what the Trooth Network is, what one company record carries, pricing, how witnessing works) from Trooth's fixed, curated knowledge base. Makes no outside request. A question the knowledge base does not cover returns out_of_scope; for a company's record use trooth_public_trust_profile.

Input parameters:

- `question` (string, required): A question about Trooth

Output parameters:

- `answered_at` (string): When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of.
- `candidates` (array): trooth_public_trust_profile only, with status bad_input: a name several published companies share. No company was chosen; each entry's select is the exact identifier that reads that one company.
- `citations` (array): trooth_ask only: the entries the answer was taken from, each with where it comes from and the date it was last checked or changed.
- `claim_url` (string): Present when the subject has no published record (unclaimed or private).
- `evidence` (object): Present on a published profile. What this answer is built from, what it leaves out, and where to get the rest. The summary is a summary: the typed facts with their provenance are in the record at ful…
- `provenance` (string): Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either…
- `source` (object): What this answer was read from, which version of it, and the date that source itself carries. as_of is null when the source carries no date, never a guessed one.
- `status` (string): Machine-branchable outcome for this lookup.
- `subject` (string): The company, domain or token this answer is about.
- `summary` (string): The same answer as the text content, for display. Bounded; a longer answer is cut and says where the rest is.

### `trooth_outside_in_read` (~135 tokens)

Fetch https://<domain>/ and /.well-known/security.txt once, when called, from Trooth's server and report whether HTTPS answered, which of five response headers (HSTS, CSP, nosniff, frame protection, referrer policy) are present, and whether security.txt is published, absent or unread. IP literals and names resolving to private, loopback or link-local addresses are refused; redirects are reported, not followed; each request stops after 4 seconds. Observations, not witnessed evidence, not a grade.

Input parameters:

- `domain` (string, required): Domain to read, e.g. example.com

Output parameters:

- `answered_at` (string): When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of.
- `candidates` (array): trooth_public_trust_profile only, with status bad_input: a name several published companies share. No company was chosen; each entry's select is the exact identifier that reads that one company.
- `citations` (array): trooth_ask only: the entries the answer was taken from, each with where it comes from and the date it was last checked or changed.
- `claim_url` (string): Present when the subject has no published record (unclaimed or private).
- `evidence` (object): Present on a published profile. What this answer is built from, what it leaves out, and where to get the rest. The summary is a summary: the typed facts with their provenance are in the record at ful…
- `provenance` (string): Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either…
- `source` (object): What this answer was read from, which version of it, and the date that source itself carries. as_of is null when the source carries no date, never a guessed one.
- `status` (string): Machine-branchable outcome for this lookup.
- `subject` (string): The company, domain or token this answer is about.
- `summary` (string): The same answer as the text content, for display. Bounded; a longer answer is cut and says where the rest is.

### `trooth_public_trust_profile` (~132 tokens)

Read one company's published record on the Trooth Network, given its domain or Trooth slug. The identifier is matched exactly (a URL is reduced to its host), never by a similar name; a name several companies share returns their candidates, not a pick. A record is keyed by its domain and does not by itself say which legal entity, subsidiary or product the domain belongs to. Returns a status and a provenance label; the company's own text is labeled as its own words. Read only.

Input parameters:

- `company` (string, required): Company domain (e.g. acme.com) or Trooth slug

Output parameters:

- `answered_at` (string): When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of.
- `candidates` (array): trooth_public_trust_profile only, with status bad_input: a name several published companies share. No company was chosen; each entry's select is the exact identifier that reads that one company.
- `citations` (array): trooth_ask only: the entries the answer was taken from, each with where it comes from and the date it was last checked or changed.
- `claim_url` (string): Present when the subject has no published record (unclaimed or private).
- `evidence` (object): Present on a published profile. What this answer is built from, what it leaves out, and where to get the rest. The summary is a summary: the typed facts with their provenance are in the record at ful…
- `provenance` (string): Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either…
- `source` (object): What this answer was read from, which version of it, and the date that source itself carries. as_of is null when the source carries no date, never a guessed one.
- `status` (string): Machine-branchable outcome for this lookup.
- `subject` (string): The company, domain or token this answer is about.
- `summary` (string): The same answer as the text content, for display. Bounded; a longer answer is cut and says where the rest is.

### `trooth_verify` (~121 tokens)

Check the two signatures on a Trust Ledger Token (tlt2. or tlt. form, or its JTI) against Trooth's own token ledger. Returns valid, invalid (a signature does not check out), expired or revoked, or unclaimed when no token matches. Trooth's signature covers the signing event, not the claim bytes and not the truth of the claims; the issuing company's signature covers the payload.

Input parameters:

- `token` (string, required): A Trust Ledger Token (tlt2. or tlt. form) or its JTI

Output parameters:

- `answered_at` (string): When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of.
- `candidates` (array): trooth_public_trust_profile only, with status bad_input: a name several published companies share. No company was chosen; each entry's select is the exact identifier that reads that one company.
- `citations` (array): trooth_ask only: the entries the answer was taken from, each with where it comes from and the date it was last checked or changed.
- `claim_url` (string): Present when the subject has no published record (unclaimed or private).
- `evidence` (object): Present on a published profile. What this answer is built from, what it leaves out, and where to get the rest. The summary is a summary: the typed facts with their provenance are in the record at ful…
- `provenance` (string): Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either…
- `source` (object): What this answer was read from, which version of it, and the date that source itself carries. as_of is null when the source carries no date, never a guessed one.
- `status` (string): Machine-branchable outcome for this lookup.
- `subject` (string): The company, domain or token this answer is about.
- `summary` (string): The same answer as the text content, for display. Bounded; a longer answer is cut and says where the rest is.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/troothllc-trooth-network/public-mcp#diagnostics

## Score history

- 2026-10-03: 80
- 2026-10-02: 79
- 2026-10-01: 79
- 2026-09-30: 79
- 2026-09-29: 78
- 2026-09-28: 78
- 2026-09-27: 77
- 2026-09-26: 77

## Common questions

### What is the Trooth MCP server?

Trooth is an MCP server listed in the public MCP registry as io.github.troothllc/trooth-network. Trooth is an infrastructure and cybersecurity company providing Machine-Readable Trust. This page covers its hosted endpoint (https://api.trooth.co/public/mcp).

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

Trooth scores 80 out of 100 on VerifyMCP. 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 Trooth MCP server expose?

Trooth exposes 4 tools: trooth_ask, trooth_outside_in_read, trooth_public_trust_profile, trooth_verify. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.

### Does the Trooth MCP server require authentication?

No. We connected to Trooth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Trooth MCP server still maintained?

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

## Links

- Remote endpoint: https://api.trooth.co/public/mcp
- Repository: https://github.com/troothllc/trooth-mcp
- Website: https://trooth.co/
- Changelog RSS feed: https://verifymcp.io/servers/troothllc-trooth-network/public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/troothllc-trooth-network/public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/troothllc-trooth-network/public-mcp