Trooth
REMOTE · API.TROOTH.CO · SCANNED SEP 21
Trooth is an infrastructure & cybersecurity company providing Machine-Readable Trust.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 655 tokens (~93/item across 7 items; 4 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · api.trooth.co
claude mcp add --transport http trooth-eng-trooth-network 'https://api.trooth.co/public/mcp'
{
"mcpServers": {
"trooth-eng-trooth-network": {
"url": "https://api.trooth.co/public/mcp"
}
}
} {
"servers": {
"trooth-eng-trooth-network": {
"type": "http",
"url": "https://api.trooth.co/public/mcp"
}
}
} [mcp_servers.trooth-eng-trooth-network] url = "https://api.trooth.co/public/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trooth-eng-trooth-network": {
"type": "remote",
"url": "https://api.trooth.co/public/mcp",
"enabled": true
}
}
} openclaw mcp add trooth-eng-trooth-network --url 'https://api.trooth.co/public/mcp' --transport streamable-http
mcp_servers:
trooth-eng-trooth-network:
url: "https://api.trooth.co/public/mcp" {
"McpServers": {
"trooth-eng-trooth-network": {
"Transport": "http",
"Url": "https://api.trooth.co/public/mcp"
}
}
} assistant mcp add trooth-eng-trooth-network -t streamable-http -u 'https://api.trooth.co/public/mcp'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +2
- 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 security
- Schema quality: 80 → 93 ▼ functional
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
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 21 Sept 2026 · Probed https://api.trooth.co/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trooth.co | CN=YE1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 52c74f9cfc4bf6cc358093ada0e31f00a0a |
| SANs: *.trooth.co, trooth.co | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.trooth.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| trooth.co. | present | 2371 | 13 | Verified |
| api.trooth.co. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.trooth.co/public/mcp | Verified | 200 | |
| http (plaintext) | http://api.trooth.co/public/mcp | HTTPS enforced | 301 | https://api.trooth.co/public/mcp |
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 →
trooth_ask ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | A question about Trooth |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_url | string | – | Present only when the subject has no published record and could be claimed by its owner. |
| provenance | string | yes | 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 | yes | Machine-branchable outcome for this lookup. |
| subject | string | yes | The company, domain or token this answer is about. |
| summary | string | yes | The same answer as the text content, for display. |
No examples provided.
trooth_outside_in_read ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to read, e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_url | string | – | Present only when the subject has no published record and could be claimed by its owner. |
| provenance | string | yes | 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 | yes | Machine-branchable outcome for this lookup. |
| subject | string | yes | The company, domain or token this answer is about. |
| summary | string | yes | The same answer as the text content, for display. |
No examples provided.
trooth_public_trust_profile ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company domain (e.g. acme.com) or Trooth slug |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_url | string | – | Present only when the subject has no published record and could be claimed by its owner. |
| provenance | string | yes | 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 | yes | Machine-branchable outcome for this lookup. |
| subject | string | yes | The company, domain or token this answer is about. |
| summary | string | yes | The same answer as the text content, for display. |
No examples provided.
trooth_verify ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | A Trust Ledger Token (tlt2. or tlt. form) or its JTI |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_url | string | – | Present only when the subject has no published record and could be claimed by its owner. |
| provenance | string | yes | 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 | yes | Machine-branchable outcome for this lookup. |
| subject | string | yes | The company, domain or token this answer is about. |
| summary | string | yes | The same answer as the text content, for display. |
No examples provided.
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.