# Trooth (remote · api.trooth.co)

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

- Trust score: 87/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

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

## Channel facts

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

## 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-09-21.

- **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**: 87/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).
  - Tool/resource definitions use about 655 tokens (~93/item across 7 items; 4 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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 trooth-eng-trooth-network 'https://api.trooth.co/public/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "trooth-eng-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-09-20 (score 87, +1)

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

### 2026-09-18 (score 86, +1)

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

### 2026-09-16 (score 85, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “trooth_ask” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 80 → 93
- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-06-18 → 2026-07-28

### 2026-09-15 (score 83, +1)

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

### 2026-09-13 (score 82, +1)

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

### 2026-09-10 (score 81, +1)

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

### 2026-09-08 (score 80, +1)

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

### 2026-09-06 (score 79, +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.

## MCP tools (4)

### `trooth_public_trust_profile` (~96 tokens)

Look up a company's published, witnessed Trust Profile on Trooth by domain or slug. Returns the witnessed standing, pillar summary, and evidence-chain stats for companies that publish an OS profile, or the witnessed Network standing (signed scan result) for companies listed in the public directory. Unknown companies return an honest not-found.

Input parameters:

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

Output parameters:

- `claim_url` (string): Present only when the subject has no published record and could be claimed by its owner.
- `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…
- `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.

### `trooth_outside_in_read` (~93 tokens)

Perform a live, neutral read of a domain's public security surface right now: HTTPS/TLS reachability, common security headers (HSTS, CSP, nosniff, frame protection, referrer policy), and /.well-known/security.txt. These are observations from the public internet, not witnessed evidence and not a grade.

Input parameters:

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

Output parameters:

- `claim_url` (string): Present only when the subject has no published record and could be claimed by its owner.
- `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…
- `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.

### `trooth_ask` (~77 tokens)

Ask about Trooth itself: what the Trooth Network is, what one company record carries, why a company needs one, pricing (free), and how witnessing works. The Trooth Network is Trooth's only product. Answers come from Trooth's curated knowledge base.

Input parameters:

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

Output parameters:

- `claim_url` (string): Present only when the subject has no published record and could be claimed by its owner.
- `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…
- `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.

### `trooth_verify` (~126 tokens)

Verify a Trooth Trust Ledger Token (a signed, portable trust receipt in tlt2 / tlt form, or its JTI). Re-runs both signatures independently and returns whether the token is valid, expired, revoked, or tampered - plus honest provenance: Trooth's outer signature attests only the witnessing event and the byte-for-byte payload at issuance, never the truthfulness of the declared claims. Unknown tokens return an honest not-found.

Input parameters:

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

Output parameters:

- `claim_url` (string): Present only when the subject has no published record and could be claimed by its owner.
- `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…
- `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.

## Diagnostics

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

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 83
- 2026-09-14: 82
- 2026-09-13: 82
- 2026-09-12: 81
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 77
- 2026-08-31: 76
- 2026-08-30: 76

## Common questions

### What is the Trooth MCP server?

Trooth is an MCP server listed in the public MCP registry as io.github.trooth-eng/trooth-network. Trooth is an infrastructure & 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 87 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_public_trust_profile, trooth_outside_in_read, trooth_ask, trooth_verify. Their descriptions and schemas cost roughly 392 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 21 September 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/trooth-eng-trooth-network/public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/trooth-eng-trooth-network/public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/trooth-eng-trooth-network/public-mcp