Trooth
REMOTE · MCP.TROOTH.CO
Read any company's record on the Trooth Network, each fact labeled with who said it and when.
Available components
Last scanned (12 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Now co.trooth/trooth, the one Trooth MCP server at https://mcp.trooth.co.
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (trooth_hub_sync). See how to fix → View diagnostics → Fail
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6717 tokens (~134/item across 50 items; 42 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 11 days we've observed: 14 tool removals, 1 breaking changes, 0 auth/transport breaks, 17 additions. See how to fix → Fail
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 (64% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 44 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 18 Nov 26 0
- New tool “trooth_api_details” functional
- New tool “trooth_api_search” functional
- New tool “trooth_inspect” functional
- 16 Nov 26 0
- Tool “trooth_profile_domain_check” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_domain_start” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_publish” rewrote its description, which is the text the model reads security
- First check of Capabilities: pass functional
- New resource “Semanto fact card” functional
- 15 Nov 26 0
- A breaking change shipped without a version bump: still 1.8.0 ▼ security
- Tool “trooth_semanto_guide” was removed ▼ security
- Tool “trooth_semanto_pages_changed” was removed ▼ security
- Tool “trooth_semanto_verify” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “call_write_tool”, which the server declares destructive security
- Tool “call_tool” rewrote its description, which is the text the model reads security
- Tool “trooth_semanto_facts” rewrote its description, which is the text the model reads security
- Tool “call_tool” no longer declares itself destructive security
- Tool coverage: 51% → 62% ▲ functional
- Tool “enable_toolset” now declares an output schema ▲ functional
- Tool “search_tools” now declares an output schema ▲ functional
- Tool “trooth_hub_sync” now declares an output schema ▲ functional
- Tool “trooth_setup” now declares an output schema ▲ functional
- New tool “trooth_semanto_answer” functional
- New tool “trooth_semanto_statement_check” functional
- “trooth_semanto_facts” added an optional parameter “cursor” cosmetic
- “trooth_semanto_facts” added an optional parameter “page_size” cosmetic
- Tool “call_tool” changed its title: Run any tool on this server by name → Run a read-only tool by name cosmetic
- 14 Nov 26 −1
- A breaking change shipped without a version bump: still 1.8.0 ▼ security
- Tool “semanto_facts” was removed ▼ security
- Tool “semanto_guide” was removed ▼ security
- Tool “semanto_install_check” was removed ▼ security
- Tool “semanto_install_guide” was removed ▼ security
- Tool “semanto_page” was removed ▼ security
- Tool “semanto_pages_changed” was removed ▼ security
- Tool “semanto_review_get” was removed ▼ security
- Tool “semanto_setup_choose” was removed ▼ security
- Tool “semanto_setup_confirm” was removed ▼ security
- Tool “semanto_setup_read_again” was removed ▼ security
- Tool “semanto_sign” was removed ▼ security
- Tool “semanto_status” was removed ▼ security
- Tool “semanto_verify” was removed ▼ 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 security
- Tool “trooth_profile_checklist” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_diff” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_domain_check” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_domain_start” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_get” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_import” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_publish” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_remediation_plan” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_update” rewrote its description, which is the text the model reads security
- Tool “trooth_profile_validate” rewrote its description, which is the text the model reads security
- Tool “trooth_verify” rewrote its description, which is the text the model reads security
- Tool “trooth_verify” dropped its output schema ▼ functional
- New tool “trooth_semanto_facts” functional
- New tool “trooth_semanto_guide” functional
- New tool “trooth_semanto_install_check” functional
- New tool “trooth_semanto_install_guide” functional
- New tool “trooth_semanto_page” functional
- New tool “trooth_semanto_pages_changed” functional
- New tool “trooth_semanto_review_get” functional
- New tool “trooth_semanto_setup_choose” functional
- New tool “trooth_semanto_setup_confirm” functional
- New tool “trooth_semanto_setup_read_again” functional
- New tool “trooth_semanto_sign” functional
- New tool “trooth_semanto_status” functional
- New tool “trooth_semanto_verify” functional
- “trooth_verify” added an optional parameter “hash” cosmetic
- “trooth_verify” added an optional parameter “url” cosmetic
- “search_tools” reworded the description of “query” cosmetic
- “trooth_profile_checklist” reworded the description of “workspace” cosmetic
- “trooth_profile_diff” reworded the description of “workspace” cosmetic
- “trooth_profile_domain_check” reworded the description of “workspace” cosmetic
- “trooth_profile_domain_start” reworded the description of “workspace” cosmetic
- “trooth_profile_get” reworded the description of “workspace” cosmetic
- “trooth_profile_import” reworded the description of “workspace” cosmetic
- “trooth_profile_publish” reworded the description of “workspace” cosmetic
- “trooth_profile_remediation_plan” reworded the description of “workspace” cosmetic
- “trooth_profile_update” reworded the description of “expected_revision” cosmetic
- “trooth_profile_update” reworded the description of “idempotency_key” cosmetic
- “trooth_profile_update” reworded the description of “if_match” cosmetic
- “trooth_profile_update” reworded the description of “workspace” cosmetic
- “trooth_profile_validate” reworded the description of “expected_revision” cosmetic
- “trooth_profile_validate” reworded the description of “workspace” cosmetic
- “trooth_verify” reworded the description of “token” cosmetic
- “trooth_verify” made “token” optional cosmetic
- Tool “trooth_my_company_record” changed its title: Read your own workspace's company record → Read the caller's own workspace's company record cosmetic
- Tool “trooth_profile_checklist” changed its title: List what is left before your Trust Profile is published → List what is left before the workspace's Trust Profile is published cosmetic
- Tool “trooth_profile_diff” changed its title: Show where your Trust Profile draft and published page differ → Show where the workspace's Trust Profile draft and published page differ cosmetic
- Tool “trooth_profile_domain_check” changed its title: Check your company's domain proof → Check the company's domain proof cosmetic
- Tool “trooth_profile_domain_start” changed its title: Start proving your company's domain → Start proving the company's domain cosmetic
- Tool “trooth_profile_get” changed its title: Read your Trust Profile draft → Read the workspace's Trust Profile draft cosmetic
- Tool “trooth_profile_import” changed its title: Import a page of your website into your Trust Profile draft → Import a page of the company's website into the workspace's Trust Profile draft cosmetic
- Tool “trooth_profile_publish” changed its title: Publish your Trust Profile draft → Publish the workspace's Trust Profile draft cosmetic
- Tool “trooth_profile_remediation_plan” changed its title: Plan the changes that close your open checklist items → Plan the changes that close the open checklist items cosmetic
- Tool “trooth_profile_update” changed its title: Change fields of your Trust Profile draft → Change fields of the workspace's Trust Profile draft cosmetic
- Tool “trooth_verify” changed its title: Check the signatures on a Trust Ledger Token → Check a signed copy or a Trust Ledger Token cosmetic
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 4.
- 11 Nov 26 −1
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.8.0 ▼ security
- Tool “semanto_whoami” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “call_tool”, which the server declares destructive security
- Tool “trooth_profile_import” rewrote its description, which is the text the model reads security
- “trooth_profile_import” added an optional parameter “pages” cosmetic
- “trooth_profile_import” reworded the description of “url” cosmetic
- “trooth_profile_import” made “url” optional cosmetic
- 10 Nov 26 69
First indexed and scored.
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 Nov 2026 · Probed https://mcp.trooth.co
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=WE1,O=Google Trust Services,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 4311f86c789cf86f0e82664f0a5dcf25 |
| SANs: trooth.co, mcp.trooth.co, *.mcp.trooth.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.trooth.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| trooth.co. | DS published | 2371 | 13 | Verified |
| mcp.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=31536000; 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://mcp.trooth.co | Verified | 200 | |
| http (plaintext) | http://mcp.trooth.co | HTTPS enforced | 301 | https://mcp.trooth.co/ |
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_profile_validate Check changes and the publish rules without saving ~222
Uses a trooth.co sign-in (or an agent key with profile:read). Takes changes (optional, as trooth_profile_update takes them), expected_revision and workspace. Runs the checks of trooth_profile_update with dry_run and of a publish (name, domain proof, transcripts, agent publishing permission, instructions to a model) and saves nothing. Returns each check with its code and fix, and would_publish. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | – | Optional. The changes to check, as trooth_profile_update takes them. Leave it out to check the draft as it is saved now. |
| expected_revision | string | – | Optional. The revision the caller read with trooth_profile_get. When the draft changed since, the answer is code revision_changed with the new revision. |
| workspace | string | – | With the person's sign-in only: the workspace to act on when the person belongs to more than one, by its trooth.co key (Settings, Organizations). Leave it out for the caller's own workspace or the ca… |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of. |
| approval | object | – | status approval_required: the request a person approves (id, action, status, expires_at). |
| assurance_boundary | object | yes | What this answer does and does not establish (audit 2026-10-12, F-04). The same statement every Trooth surface carries. |
| content_trust | object | yes | Which fields of this answer carry text Trooth did not write (audit 2026-10-12, F-06). company_supplied: the company's own words and links; externally_fetched: bytes read from the named domain at answ… |
| error | object | – | Present when the call did not complete as asked. For a refusal from trooth.co, code, title, fix and action_url are trooth.co's own, copied unchanged from its problem+json (the whole of which is in re… |
| http_status | integer|null | – | The HTTP status trooth.co answered with; null when it did not answer. |
| idempotency_key | string|null | – | trooth_profile_update, not a dry run: the Idempotency-Key sent with the write (yours, or one this server made). To retry the same write, send the same changes with this key. |
| next_cursor | string|null | – | trooth_buyer_activity and trooth_following: send it back as cursor for the next page; null on the last page. |
| people | array | – | trooth_team_on_page: the people the draft shows, each with name, title and location in the company's own words. |
| provenance | string | yes | agent_key_workspace: trooth.co answered for the workspace the agent key belongs to. input_error: nothing was sent (no agent key, or an argument could not be used). read_failed: trooth.co did not answ… |
| replayed | boolean | – | true when trooth.co answered from an earlier call with the same Idempotency-Key and made no second write. |
| request | object | – | What this server sent, and where: the method and address. The agent key went in the Authorization header and is never echoed. |
| response | object | – | The JSON trooth.co answered, exactly as it answered it: the draft, the change results, the checklist, the publish answer, or the problem+json of a refusal. |
| retry_after_seconds | integer | – | status busy only: seconds to wait before trying trooth_outside_in_read again. |
| revision | string|null | – | The draft's revision as trooth.co stated it (in the body or the ETag). Send it as if_match or expected_revision on trooth_profile_update. |
| source | object | yes | 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 | yes | Machine-branchable outcome for this call. not_linked: an OpenAI Apps SDK client called with no sign-in; nothing was sent, and _meta carries the sign-in challenge. approval_required: an agent key aske… |
| subject | string | yes | The company, domain or token this answer is about. |
| summary | string | yes | The same answer as the text content, for display. Bounded; a longer answer is cut and says where the rest is. |
| untrusted_text | object | – | A10. present: this answer carries text Trooth did not write, in the fields content_trust lists (a company's own words, a provider's answer, bytes read from a website). flagged: the exact paths of tho… |
No examples provided.
trooth_public_trust_profile Read a company's complete Trust Profile ~245
Read one company's published record on the Trooth Network, given its domain or Trooth slug, matched exactly, never by a similar name; a name several companies share returns their candidates, not a pick. Returns a status and a provenance label with the complete Trust Profile (detail full, the default) or a short answer (detail summary, the better first call). A record is keyed by its domain and does not by itself say which legal entity, subsidiary or product the domain belongs to. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company domain (e.g. acme.com) or Trooth slug; a URL is reduced to its host |
| detail | string | – | full (default): the complete profile, section by section. summary: the short answer, the contract summary members and where the record is; ask for it first. |
| sections | string | – | Optional. Comma-separated section names to return, from: overview, identity, history, funding, product, pricing, stack, security, privacy, ai, hosting, infrastructure, procurement, relationships, pro… |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of. |
| assurance_boundary | object | yes | What this answer does and does not establish (audit 2026-10-12, F-04). The same statement every Trooth surface carries. |
| buyer_questions | array | – | trooth_public_trust_profile, when the record serves it: one entry per buyer question ID with answer_state (answered, no, not_published, not_read), answer, sentence, provenance, as_of, anchor_url and… |
| 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). |
| company_words | object | – | The company's own name, tagline and categories as the record or listing carries them: its words, not Trooth's, and never repeated in the summary. A member the record did not serve is null or empty. |
| content_trust | object | yes | Which fields of this answer carry text Trooth did not write (audit 2026-10-12, F-06). company_supplied: the company's own words and links; externally_fetched: bytes read from the named domain at answ… |
| controls_not_in_place | array | – | trooth_public_trust_profile, when the record serves it: { control, status_note, source_url } from the company's own Trust Center data. |
| disclosures | object | – | trooth_ai_data_use_disclosures only, on a published record: the company's AI and data-use declarations exactly as published, and what Trooth has itself observed in the company's policies. A declarati… |
| error | object | – | Present when the call did not complete as asked. not_found: no published record answers. ambiguous: several records match and none was chosen (see candidates). invalid_input: an argument could not be… |
| 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… |
| identity | object | – | trooth_public_trust_profile, when the record serves it (contract member identity): legal_name, domain, registry_identifier, canonical_url and note. |
| next_cursor | string|null | – | The list tools: send it back as cursor, with the same other arguments, for the next page; null on the last page. |
| outside_in | object | – | trooth_outside_in_read only, with status observed: what this one read observed, field by field, the same observations as the summary. Each header and security.txt state is an observation of the respo… |
| page | object | – | One page in a fixed, documented order. next_cursor is opaque: send it back as cursor with the same arguments, or null on the last page. |
| profile | object | – | trooth_public_trust_profile with detail full, on a published record: the complete Trust Profile (format trooth.company-profile.v1), every section in the page's order or the sections asked for. Each s… |
| 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… |
| record_summary | object | – | trooth_public_trust_profile, when the record serves it (contract member record_summary): record_version, last_witnessed_at, counts_by_provenance, sections_not_published, sections_on_request, checks_r… |
| results | array | – | trooth_search_companies only: the published records that match, in the Network's own order. The `standing` field is Witnessed, Self-published or Unavailable (the witnessed feed did not answer; not a… |
| retry_after_seconds | integer | – | status busy only: seconds to wait before trying trooth_outside_in_read again. |
| source | object | yes | 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 | 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. Bounded; a longer answer is cut and says where the rest is. |
| token | object | – | trooth_verify only: what the token and the ledger carry that Trooth did not write. key_id is the key id the token names; revoked_reason is the revoker's words; declared holds the issuing company's ow… |
| untrusted_text | object | – | A10. present: this answer carries text Trooth did not write, in the fields content_trust lists (a company's own words, a provider's answer, bytes read from a website). flagged: the exact paths of tho… |
No examples provided.
trooth_resolve_company Find a company's Trooth Network record ~163
Find the published Trooth Network record for a company given a domain, web address, Trooth slug or name; a company-register identifier, Crunchbase address or Wikidata ID is accepted and answered not_found, because Trooth keeps no lookup by them. Returns the record ID, its canonical https address and why it matched, or every candidate with why each matched (status ambiguous, none chosen), or not_found. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | A domain, web address, Trooth slug, legal or trading name, company-register identifier, Crunchbase address or Wikidata ID |
| kind | string | – | Optional. What the identifier is; read from its form when omitted. A register identifier is read as a name unless kind says otherwise. |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of. |
| assurance_boundary | object | yes | What this answer does and does not establish (audit 2026-10-12, F-04). The same statement every Trooth surface carries. |
| 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. |
| content_trust | object | yes | Which fields of this answer carry text Trooth did not write (audit 2026-10-12, F-06). company_supplied: the company's own words and links; externally_fetched: bytes read from the named domain at answ… |
| error | object | – | Present when the call did not complete as asked. not_found: no published record answers. ambiguous: several records match and none was chosen (see candidates). invalid_input: an argument could not be… |
| identity | object | – | trooth_public_trust_profile, when the record serves it (contract member identity): legal_name, domain, registry_identifier, canonical_url and note. |
| 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… |
| resolution | object | – | resolved: record_id (the Trooth slug), canonical_url, domain, select (what the other tools read) and matched_on. ambiguous: every candidate with why it matched; none is chosen. |
| retry_after_seconds | integer | – | status busy only: seconds to wait before trying trooth_outside_in_read again. |
| source | object | yes | 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 | yes | Machine-branchable outcome for this call. |
| subject | string | yes | The company, domain or token this answer is about. |
| summary | string | yes | The same answer as the text content, for display. Bounded; a longer answer is cut and says where the rest is. |
| untrusted_text | object | – | A10. present: this answer carries text Trooth did not write, in the fields content_trust lists (a company's own words, a provider's answer, bytes read from a website). flagged: the exact paths of tho… |
No examples provided.
trooth_search_companies Search the Trooth Network for companies ~212
Search the companies published on the Trooth Network by name, domain, tagline or category, optionally within one industry. Returns up to 10 entries per page (limit takes 1 to 200) in slug order with next_cursor; only the first 100 matches are read, so at most 100 come back, each with its name and tagline in the company's own words, whether Trooth witnessed it, and the identifier that reads its record with trooth_public_trust_profile. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional. The next_cursor (also at page.next_cursor) of the previous answer, sent with the same query and industry. |
| industry | string | – | Optional. Only companies in this industry, e.g. Fintech |
| limit | integer | – | Optional. How many entries per page, 1 to 200 (default 10). |
| query | string | yes | Words to match: a company name, a domain, a category such as payroll or observability |
| Name | Type | Req | Description |
|---|---|---|---|
| answered_at | string | yes | When this server produced this answer (UTC, ISO 8601). It is not the date of the facts: that is source.as_of. |
| assurance_boundary | object | yes | What this answer does and does not establish (audit 2026-10-12, F-04). The same statement every Trooth surface carries. |
| buyer_questions | array | – | trooth_public_trust_profile, when the record serves it: one entry per buyer question ID with answer_state (answered, no, not_published, not_read), answer, sentence, provenance, as_of, anchor_url and… |
| 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). |
| company_words | object | – | The company's own name, tagline and categories as the record or listing carries them: its words, not Trooth's, and never repeated in the summary. A member the record did not serve is null or empty. |
| content_trust | object | yes | Which fields of this answer carry text Trooth did not write (audit 2026-10-12, F-06). company_supplied: the company's own words and links; externally_fetched: bytes read from the named domain at answ… |
| controls_not_in_place | array | – | trooth_public_trust_profile, when the record serves it: { control, status_note, source_url } from the company's own Trust Center data. |
| disclosures | object | – | trooth_ai_data_use_disclosures only, on a published record: the company's AI and data-use declarations exactly as published, and what Trooth has itself observed in the company's policies. A declarati… |
| error | object | – | Present when the call did not complete as asked. not_found: no published record answers. ambiguous: several records match and none was chosen (see candidates). invalid_input: an argument could not be… |
| 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… |
| identity | object | – | trooth_public_trust_profile, when the record serves it (contract member identity): legal_name, domain, registry_identifier, canonical_url and note. |
| next_cursor | string|null | – | The list tools: send it back as cursor, with the same other arguments, for the next page; null on the last page. |
| outside_in | object | – | trooth_outside_in_read only, with status observed: what this one read observed, field by field, the same observations as the summary. Each header and security.txt state is an observation of the respo… |
| page | object | – | One page in a fixed, documented order. next_cursor is opaque: send it back as cursor with the same arguments, or null on the last page. |
| profile | object | – | trooth_public_trust_profile with detail full, on a published record: the complete Trust Profile (format trooth.company-profile.v1), every section in the page's order or the sections asked for. Each s… |
| 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… |
| record_summary | object | – | trooth_public_trust_profile, when the record serves it (contract member record_summary): record_version, last_witnessed_at, counts_by_provenance, sections_not_published, sections_on_request, checks_r… |
| results | array | – | trooth_search_companies only: the published records that match, in the Network's own order. The `standing` field is Witnessed, Self-published or Unavailable (the witnessed feed did not answer; not a… |
| retry_after_seconds | integer | – | status busy only: seconds to wait before trying trooth_outside_in_read again. |
| source | object | yes | 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 | 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. Bounded; a longer answer is cut and says where the rest is. |
| token | object | – | trooth_verify only: what the token and the ledger carry that Trooth did not write. key_id is the key id the token names; revoked_reason is the revoker's words; declared holds the issuing company's ow… |
| untrusted_text | object | – | A10. present: this answer carries text Trooth did not write, in the fields content_trust lists (a company's own words, a provider's answer, bytes read from a website). flagged: the exact paths of tho… |
No examples provided.
trooth_semanto_answer Answer a question from a company's signed record ~185
One answer from the company's signed record: the signed sentence word for word, its value in standard form, its conditions, when it was signed, who stated it, the check link, the fact ID and the version hash. The question is matched in a fixed order (fact ID, the record's question map, words that name a fact type, word overlap) and matched_by names the step. More than one fitting fact, or a name two companies share, returns the candidates and picks none; nothing fitting returns not_published, never a nearby fact. No generated text. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | The company: its Trooth ID, its domain or its name. |
| fact_id | string | – | Optional: a fact ID instead of a question. |
| question | string | – | Optional: the question, at most 300 characters. |
No output schema declared.
No examples provided.
trooth_semanto_facts A company's signed facts ~98
The company's signed facts as JSON-LD. For a large record, send page_size for one page of facts at a time and next_cursor back as cursor. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional: the next_cursor of the page before. |
| page_size | integer | – | Optional: 1 to 1,000 facts a page. |
| trooth_id | string | yes | The company's Trooth ID. |
No output schema declared.
No examples provided.
trooth_semanto_install_check Check my site ~38
Check my site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_install_guide How to put it on the site ~43
How to put it on the site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_page Read one signed page ~63
One page of a company's signed copy as markdown, by its path on the company's site. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The page's path, for example /pricing. |
| trooth_id | string | yes | The company's Trooth ID. |
No output schema declared.
No examples provided.
trooth_semanto_review_get The facts to review ~39
The facts to review. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_setup_choose Choose Basic or the full signed copy ~42
Choose Basic or the full signed copy. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_setup_confirm Confirm the reviewed version ~39
Confirm the reviewed version. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_setup_read_again Read the website again ~40
Read the website again. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_sign Sign and publish ~37
Sign and publish. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_semanto_statement_check Check a statement against the signed record ~191
Checks a statement about a company, sentence by sentence, against its current signed record by fixed rules with no model: supported (with the fact ID), differs (with the signed sentence), not_in_record, or not_checked for a sentence with no value a rule reads. It is meant for a price, an hour, a phone number or a date before it is repeated. To check one value before stating it, send fact_id and value instead: the answer is matches or differs by rule alone. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| fact_id | string | – | Check by value: the fact's ID. |
| statement | string | – | The text to check, up to 4,000 characters. |
| trooth_id | string | yes | The company's Trooth ID. |
| value | string | – | Check by value: the value as it will be stated, up to 1,000 characters. |
No output schema declared.
No examples provided.
trooth_semanto_status Setup status and next step ~39
Setup status and next step. Sign in to Trooth, or send an agent key, to see what it takes and to use it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trooth_setup Set up Semanto and the Trust Profile, one step at a time ~127
Runs the whole guide, proving the domain, reading the site, reviewing and signing the facts, putting the signed copy on the site and checking it, and answers the one next call to make: next_action names the tool and its arguments. Each answer reflects the steps already done. A step only a person may take answers its trooth.co page.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The company's bare domain, when setup does not know it yet. |
| trooth_id | string | – | The company's trooth_id. Leave it out to use the one your key or sign-in acts for. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| next_action | object | – | The one next call: tool (null when a person acts), arguments, label, and url where a page does it. |
| status | string | – | Set on a refusal: invalid_request, read_only, task_risk_detected or unavailable. |
| trust_profile | string | – | – |
No examples provided.
trooth_verify Check a signed copy or a Trust Ledger Token ~247
Check the two signatures on a Trust Ledger Token (tlt2. or tlt. form, or its JTI) against Trooth's own token ledger. A Trust Ledger Token is a signed token a company issues through Trooth about its own declared claims: the company signs the claims and Trooth signs the event of issuing it. 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. With url in place of token, it checks a page Semanto signs against its signed copy: matches, differs or not signed, with the version, the signer and the proof address. It takes token or url, one of the two.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | – | With url: the sha256: digest of the markdown the caller was served, compared in place of a fetch. |
| token | string | – | A Trust Ledger Token (tlt2. or tlt. form) or its JTI. |
| url | string | – | A page Semanto signs (https), to check it against its signed copy. |
No output schema declared.
No examples provided.
How do I install the Trooth MCP server?
Trooth is a hosted endpoint at https://mcp.trooth.co/, 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 · mcp.trooth.co
claude mcp add --transport http troothllc-trooth-network 'https://mcp.trooth.co/'
What is the Trooth MCP server?
Trooth is an MCP server listed in the public MCP registry as io.github.troothllc/trooth-network. Read any company's record on the Trooth Network, each fact labeled with who said it and when. This page covers its hosted endpoint (https://mcp.trooth.co).
Is the Trooth MCP server safe to use?
Trooth scores 68 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 42 tools: trooth_setup, trooth_hub_sync, enable_toolset, search_tools, call_tool, and 37 more. Their descriptions and schemas cost roughly 6,120 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 marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Trooth MCP server?
VerifyMCP ran 14 checks on Trooth, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.