Skip to content

Trooth MCP server

co.trooth/troothtrooth.costreamable-httpv2.0.0Scanned

Every company's public record on the Trooth Network, and Semanto: a company's website, signed.

39 tools: 3 can delete or cancel things, 22 change things and 14 only read.

Tools: 3 delete, 0 irreversible, 22 write, 14 read.
  • Reads private data · 0
  • Reads text others write · 12
  • Can send data out · 3
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Trooth MCP server can do

The Trooth MCP server is published by trooth.co, a domain the MCP Registry verified. It has 39 tools. It can delete or cancel things (3 tools: trooth_hub_sync, call_write_tool and trooth_profile_publish) and create or change data (22 tools: trooth_setup, enable_toolset, call_tool, trooth_ask and 18 more). 14 tools only read.

12 tools bring in text other people can write (trooth_setup, trooth_hub_sync, call_tool and 9 more); 3 tools can send data out of your system (trooth_profile_import, trooth_profile_publish and trooth_verify).

The fixed checks matched 6 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 2.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

39 tools

Deletes or cancels 3Claude Code: deny
  • call_write_toolRuns one tool that changes something (publish, sign, send, revoke and the like) by its name with its arguments, exactly as calling it directly does: the same sign-in, scopes and ap…Reads text others writeNo findings

    Why it is in this group

    • The name "call_write_tool" says "call": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Runs one tool that changes something (publish, sign, send, revoke and the like) by its name with its arguments, exactly as calling it directly does: the same sign-in, scopes and approvals, and a person's approval where the tool asks for one. Use it for a write tool search_tools or enable_toolset named that your client does not list. A read-only tool runs through call_tool.

    Annotations the server declares

    • title: Run a write tool by name
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • trooth_hub_syncFor one hub (business_profile or merchant_center): previews what the signed facts change there, then, with approve true, sends those items, then checks the hub against the signed c…Reads text others writeNo findings

    Why it is in this group

    • The name "trooth_hub_sync" says "sync": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    For one hub (business_profile or merchant_center): previews what the signed facts change there, then, with approve true, sends those items, then checks the hub against the signed copy. Each call does the next of preview, send and check and answers next_action. Sending waits for a person's approval where the key needs one.

    Annotations the server declares

    • title: Sync one listing hub
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • trooth_profile_publishPuts the workspace's saved Trust Profile draft on its public page, which anyone can read.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "trooth_profile_publish" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "trooth_profile_publish" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Puts the workspace's saved Trust Profile draft on its public page, which anyone can read. Uses a trooth.co sign-in if the person's role may publish the page (or an agent key with profile:publish). Takes only workspace, when the person belongs to several. Success: status published with public_url. A first publish needs the domain proved: code domain_proof_required until trooth_profile_domain_start and trooth_profile_domain_check are done. Other refusals carry their code and fix.

    Annotations the server declares

    • title: Publish the workspace's Trust Profile draft
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 22Claude Code: ask
  • call_toolRuns one read-only tool by its name with its arguments, exactly as calling it directly does: the same sign-in, scopes and limits.Reads text others write1 finding

    Why it is in this group

    • The name "call_tool" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "call_tool" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "call_tool" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Runs one read-only tool by its name with its arguments, exactly as calling it directly does: the same sign-in, scopes and limits. Use it for a tool search_tools or enable_toolset named that your client does not list. A tool that changes something runs through call_write_tool.

    Annotations the server declares

    • title: Run a read-only tool by name
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • enable_toolsetAdds one toolset to what tools/list shows for this sign-in or key: developer (Developer), team (Team and governance), commerce (Commerce), reports (Reports), evidence (Evidence and…1 finding

    Why it is in this group

    • The name "enable_toolset" says "enable": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "enable_toolset" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "enable_toolset" says "enable": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Adds one toolset to what tools/list shows for this sign-in or key: developer (Developer), team (Team and governance), commerce (Commerce), reports (Reports), evidence (Evidence and monitoring), semanto_more (Semanto, every tool). Answers the group's tools. Every tool already answers by name; this only changes the list.

    Annotations the server declares

    • title: Show a toolset
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_askAnswer 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Input: one question of at most 300 characters, with no personal details; Trooth keeps no question text. 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.

    Annotations the server declares

    • title: Ask about Trooth (the Trooth Network, what a record carries, pricing, methodology)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_my_company_recordNeeds an OAuth access token for this server, for a person who has signed in to trooth.co (no scope is required; the public tools here need no token, and an agent key is not accepte…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Needs an OAuth access token for this server, for a person who has signed in to trooth.co (no scope is required; the public tools here need no token, and an agent key is not accepted), and takes no arguments: the workspace comes from the token's subject and never from an argument. Reads the company record of the Trooth workspace the signed-in person belongs to and returns its name, its slug and the address of its public page. Read only.

    Annotations the server declares

    • title: Read the caller's own workspace's company record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_profile_checklistUses a trooth.co sign-in (or an agent key with profile:read).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Uses a trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when the person belongs to several. Lists the steps left before the workspace's Trust Profile can be published, each with state done, todo or unknown and how to do it. A step that is the owner's own choice carries action_url, the trooth.co page where the owner takes it. Read only.

    Annotations the server declares

    • title: List what is left before the workspace's Trust Profile is published
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_profile_domain_checkChecks DNS now for the TXT record trooth_profile_domain_start gave.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Checks DNS now for the TXT record trooth_profile_domain_start gave. Uses the person's sign-in as owner or admin (or an agent key with profile:publish). Takes domain, and workspace when the person belongs to several. Returns confirmed true, or confirmed false with found (the TXT values at the record's name), expected (the value it needs), host and dns_host (where the domain's DNS is managed), and the fix; DNS can take minutes. Once confirmed, trooth_profile_publish can put the page live.

    Annotations the server declares

    • title: Check the company's domain proof
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trooth_profile_domain_startStarts the proof that the workspace controls its company's domain.No findings

    Why it is in this group

    • The name "trooth_profile_domain_start" says "start": a word for a change.
    Description, as the server wrote it
    Starts the proof that the workspace controls its company's domain. Uses the person's sign-in as owner or admin (or an agent key with profile:publish). Takes domain, and workspace when the person belongs to several; it states the caller acts for someone authorized to represent the company. Returns the DNS TXT record (host, value) to add with the DNS host's own API. trooth_profile_domain_check confirms it. Refusals carry code and fix.

    Annotations the server declares

    • title: Start proving the company's domain
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_profile_importUses a trooth.co sign-in (or an agent key with profile:write).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "trooth_profile_import" says "import": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Uses a trooth.co sign-in (or an agent key with profile:write). Reads one https page of the company's own website (robots.txt first) and returns the candidates, saving nothing; accept all or candidate ids saves them to the DRAFT with the page named. pages (up to ten of one site) reads each in turn and fills blank draft fields only, the website from the home page, each value with its page. Nothing is published. It states the caller may draft from those pages.

    Annotations the server declares

    • title: Import a page of the company's website into the workspace's Trust Profile draft
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trooth_profile_remediation_planUses a trooth.co sign-in (or an agent key with profile:read).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Uses a trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when the person belongs to several. Turns each open checklist item into a step: the problem, the fix, the change or call that closes it, and the source its value needs. It proposes and never applies: every proposed value is null until the caller reads it from that source and send it with trooth_profile_update. Read only.

    Annotations the server declares

    • title: Plan the changes that close the open checklist items
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_profile_updateChanges fields of the workspace's own Trust Profile DRAFT; the public page changes only on trooth_profile_publish.No findings

    Why it is in this group

    • The name "trooth_profile_update" says "update": a word for a change.
    Description, as the server wrote it
    Changes fields of the workspace's own Trust Profile DRAFT; the public page changes only on trooth_profile_publish. Uses a trooth.co sign-in if the person's role may edit the page (or an agent key with profile:write). Each change names one field by JSON Pointer (/tagline, /founders/-) with a value and its source { url, quote } from the company's own page, or state not_published with a reason. Returns each change as applied or rejected (with code and fix) and the new revision.

    Annotations the server declares

    • title: Change fields of the workspace's Trust Profile draft
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • trooth_semanto_answerOne 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 f…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Answer a question from a company's signed record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_factsThe company's signed facts as JSON-LD.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: A company's signed facts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_install_checkCheck my site.Reads text others writeNo findings

    Why it is in this group

    • The name "trooth_semanto_install_check" says "install": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check my site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Check my site
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trooth_semanto_install_guideHow to put it on the site.1 finding

    Why it is in this group

    • The name "trooth_semanto_install_guide" says "install": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "trooth_semanto_install_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "trooth_semanto_install_guide" says "install": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: How to put it on the site
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_pageOne page of a company's signed copy as markdown, by its path on the company's site.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One page of a company's signed copy as markdown, by its path on the company's site. No key needed.

    Annotations the server declares

    • title: Read one signed page
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_setup_chooseChoose Basic or the full signed copy.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Choose Basic or the full signed copy
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_setup_confirmConfirm the reviewed version.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Confirm the reviewed version. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Confirm the reviewed version
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_setup_read_againRead the website again.Reads text others write1 finding

    Why it is in this group

    • The name "trooth_semanto_setup_read_again" says "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "website": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "trooth_semanto_setup_read_again" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "trooth_semanto_setup_read_again" says "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read the website again. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Read the website again
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • trooth_semanto_signSign and publish.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Sign and publish. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Sign and publish
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • trooth_semanto_statement_checkChecks 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 sen…1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.statement), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "trooth_semanto_statement_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.statement), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a statement against the signed record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_setupRuns 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 m…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "trooth_setup" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Set up, one step at a time
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trooth_verifyCheck the two signatures on a Trust Ledger Token (tlt2.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a signed copy or a Trust Ledger Token
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 14Show 14 read-only tools
  • search_toolsSearches every tool on this server, shown or not, by name, title and description, and answers the best matches with their toolset and input schema.No findings

    Why it is in this group

    • The name "search_tools" says "search": a word for reading.
    Description, as the server wrote it
    Searches every tool on this server, shown or not, by name, title and description, and answers the best matches with their toolset and input schema. Each match answers by name.

    Annotations the server declares

    • title: Find a tool
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_ai_data_use_disclosuresRead what one company on the Trooth Network has declared about AI and customer data (whether it trains models on customer data, whether AI is in the product, which approaches), nam…No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read what one company on the Trooth Network has declared about AI and customer data (whether it trains models on customer data, whether AI is in the product, which approaches), named by its domain or its Trooth slug, matched exactly. Each row is the company's own declaration and is labeled so, with whether Trooth observed a supporting policy clause: not observed means Trooth has not read one, never that the company does not train on customer data. Read only.

    Annotations the server declares

    • title: Read a company's published AI and data-use declarations
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_company_changesList how one company's published record changed: give its domain or slug and, optionally, since (an ISO 8601 date or time).No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List how one company's published record changed: give its domain or slug and, optionally, since (an ISO 8601 date or time). Returns record versions oldest first, each with the fact keys changed, added or removed, per-fact edits (old value, new value, time, role) when the record carries them, with next_cursor for more, and the recalls the company stored or changed in Semanto, oldest first, with recall_cursor to poll for newer ones. Read only.

    Annotations the server declares

    • title: Read how a company's record changed
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_get_factRead one answer from one company's published record: give the company's domain or slug and a buyer question ID (q_ai_training and eleven more, in trooth://buyer-questions) or a fac…No findings

    Why it is in this group

    • The name "trooth_get_fact" says "get": a word for reading.
    Description, as the server wrote it
    Read one answer from one company's published record: give the company's domain or slug and a buyer question ID (q_ai_training and eleven more, in trooth://buyer-questions) or a fact ID such as security.mfa_methods. Returns the sentence, value, provenance word, date, freshness window and anchor address, or the negative that applies: no, not_published or not_read. A fact ID the record does not hold answers unknown_fact_id with the IDs it holds. Read only.

    Annotations the server declares

    • title: Read one fact or buyer question from a company's record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_list_companiesList the companies published on the Trooth Network by what they published: industry, data region, witnessed or not, and claimed (the company published its own profile) or unclaimed…No findings

    Why it is in this group

    • The name "trooth_list_companies" says "list": a word for reading.
    Description, as the server wrote it
    List the companies published on the Trooth Network by what they published: industry, data region, witnessed or not, and claimed (the company published its own profile) or unclaimed. Returns 20 entries per page in alphabetical order of record identifier with next_cursor (limit takes 1 to 200), from the first 100 matches the directory returns, so at most 100 come back; nothing is weighed or put in an order of merit. Read only.

    Annotations the server declares

    • title: List companies on the Trooth Network by published facts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_outside_in_readFetch 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,…Reads text others writeNo findings

    Why it is in this group

    • The name "trooth_outside_in_read" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "fetch" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Live read of a domain's HTTPS and response headers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trooth_profile_diffUses a trooth.co sign-in (or an agent key with profile:read).No findings

    Why it is in this group

    • The name "trooth_profile_diff" says "diff": a word for reading.
    Description, as the server wrote it
    Uses a trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when the person belongs to several. Lists, field by field, where the saved Trust Profile draft and what the public page says now differ: each such field, by JSON Pointer, with change added, removed or changed and both values. A profile never published shows every field as added. Read only.

    Annotations the server declares

    • title: Show where the workspace's Trust Profile draft and published page differ
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_profile_getUses a trooth.co sign-in (or, for an agent that runs on its own, the workspace's agent key with profile:read).No findings

    Why it is in this group

    • The name "trooth_profile_get" says "get": a word for reading.
    Description, as the server wrote it
    Uses a trooth.co sign-in (or, for an agent that runs on its own, the workspace's agent key with profile:read). Takes fields, and workspace when the person belongs to several. Returns the workspace's own Trust Profile DRAFT as saved now, its revision (send it as if_match to trooth_profile_update), whether it is published, and its public address. fields narrows the draft to the keys or JSON Pointers asked for. With no sign-in: status unauthenticated and the fix. Read only.

    Annotations the server declares

    • title: Read the workspace's Trust Profile draft
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_profile_validateUses a trooth.co sign-in (or an agent key with profile:read).No findings

    Why it is in this group

    • The name "trooth_profile_validate" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check changes and the publish rules without saving
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_public_trust_profileRead 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 c…No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Read a company's complete Trust Profile
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_resolve_companyFind 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 accepte…Reads text others writeNo findings

    Why it is in this group

    • The name "trooth_resolve_company" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a company's Trooth Network record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_search_companiesSearch the companies published on the Trooth Network by name, domain, tagline or category, optionally within one industry.No findings

    Why it is in this group

    • The name "trooth_search_companies" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the Trooth Network for companies
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_review_getThe facts to review.Reads text others writeNo findings

    Why it is in this group

    • The name "trooth_semanto_review_get" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "trooth_semanto_review_get" says "get" and "review": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    The facts to review. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: The facts to review
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trooth_semanto_statusSetup status and next step.No findings

    Why it is in this group

    • The name "trooth_semanto_status" says "status": a word for reading.
    Description, as the server wrote it
    Setup status and next step. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Setup status and next step
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:18 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
25
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.trooth.co/.well-known/oauth-protected-resource
Authorization servers
https://connect.trooth.co
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 25 tools that change things (3 destructive, 22 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.trooth.co: tools/list returned 39 tools to an anonymous client, including trooth_hub_sync (destructive), call_write_tool (destructive), trooth_profile_publish (destructive), trooth_setup (write), enable_toolset (write) and 20 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

6 warn
  • The server marks "trooth_setup" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "enable_toolset" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "enable_toolset" says "enable": a word for a change.

    What this check looks for
  • The server marks "call_tool" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "call_tool" says "call": a word for a change.

    What this check looks for
  • The server marks "trooth_semanto_setup_read_again" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "trooth_semanto_setup_read_again" says "read": a word for reading.

    What this check looks for
  • The server marks "trooth_semanto_install_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "trooth_semanto_install_guide" says "install": a word for a change.

    What this check looks for
  • The server marks "trooth_semanto_statement_check" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input takes a statement or command to run (input.statement), which can change anything it can reach.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trooth https://mcp.trooth.co
claude mcp add --transport http trooth https://mcp.trooth.co

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trooth__search_tools",
      "mcp__trooth__trooth_ai_data_use_disclosures",
      "mcp__trooth__trooth_company_changes",
      "mcp__trooth__trooth_get_fact",
      "mcp__trooth__trooth_list_companies",
      "mcp__trooth__trooth_outside_in_read",
      "mcp__trooth__trooth_profile_diff",
      "mcp__trooth__trooth_profile_get",
      "mcp__trooth__trooth_profile_validate",
      "mcp__trooth__trooth_public_trust_profile",
      "mcp__trooth__trooth_resolve_company",
      "mcp__trooth__trooth_search_companies",
      "mcp__trooth__trooth_semanto_status",
      "mcp__trooth__trooth_semanto_review_get"
    ],
    "ask": [
      "mcp__trooth__trooth_setup",
      "mcp__trooth__enable_toolset",
      "mcp__trooth__call_tool",
      "mcp__trooth__trooth_ask",
      "mcp__trooth__trooth_my_company_record",
      "mcp__trooth__trooth_profile_checklist",
      "mcp__trooth__trooth_profile_domain_check",
      "mcp__trooth__trooth_profile_domain_start",
      "mcp__trooth__trooth_profile_import",
      "mcp__trooth__trooth_profile_remediation_plan",
      "mcp__trooth__trooth_profile_update",
      "mcp__trooth__trooth_verify",
      "mcp__trooth__trooth_semanto_setup_read_again",
      "mcp__trooth__trooth_semanto_setup_choose",
      "mcp__trooth__trooth_semanto_setup_confirm",
      "mcp__trooth__trooth_semanto_sign",
      "mcp__trooth__trooth_semanto_install_guide",
      "mcp__trooth__trooth_semanto_install_check",
      "mcp__trooth__trooth_semanto_page",
      "mcp__trooth__trooth_semanto_facts",
      "mcp__trooth__trooth_semanto_answer",
      "mcp__trooth__trooth_semanto_statement_check"
    ],
    "deny": [
      "mcp__trooth__trooth_hub_sync",
      "mcp__trooth__call_write_tool",
      "mcp__trooth__trooth_profile_publish"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trooth. Review it before you use it.

Capability tags behind 13 rules
  • mcp__trooth__trooth_setup untrusted-input
  • mcp__trooth__trooth_hub_sync untrusted-input
  • mcp__trooth__call_tool untrusted-input
  • mcp__trooth__call_write_tool untrusted-input
  • mcp__trooth__trooth_outside_in_read untrusted-input
  • mcp__trooth__trooth_profile_domain_check untrusted-input
  • mcp__trooth__trooth_profile_import untrusted-input, outbound
  • mcp__trooth__trooth_profile_publish untrusted-input, outbound
  • mcp__trooth__trooth_resolve_company untrusted-input
  • mcp__trooth__trooth_verify outbound
  • mcp__trooth__trooth_semanto_setup_read_again untrusted-input
  • mcp__trooth__trooth_semanto_review_get untrusted-input
  • mcp__trooth__trooth_semanto_install_check untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.trooth/trooth/verify?hash=62d42b150bf9e30dcb5e67a7deed4f902b2b0fa8db3bfb36ea068a11e2ee1e5f" | jq -e '.changed == false'

Pinned hash 62d42b150bf9, from Nov 15, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.trooth/trooth/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.trooth/trooth
[![Anlyon Radar](https://radar.anlyon.com/badge/co.trooth/trooth.svg)](https://radar.anlyon.com/servers/co.trooth/trooth)

Source: MCP Registry. Synced Nov 15, 2026, 19:17 UTC.

Trooth MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Trooth MCP server safe?

No scan can promise that. What its definitions show: 39 tools, 25 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Trooth MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: trooth_hub_sync, call_write_tool and trooth_profile_publish.

Can the Trooth MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Trooth MCP server have?

39 tools: 3 destructive, 22 write, 14 read. trooth_hub_sync, call_write_tool, trooth_profile_publish, trooth_setup, enable_toolset, call_tool, trooth_ask, trooth_my_company_record and 31 more.

Does the Trooth MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Trooth MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): trooth_profile_import, trooth_profile_publish and trooth_verify.

Has the Trooth MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.