Trooth MCP Server

by trooth-eng Your server? Claim it

answering

Trooth is answering right now. Last checked 10 min ago. It exposes 17 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 65 days of history · worst day 92%

65 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

218 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 66

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

1 Nov 4 tools changed the parameters they ask for6 times that day trooth_profile_checklist, trooth_profile_get, trooth_profile_publish and 1 more

1 Nov 3 tool descriptions were rewritten5 times that day trooth_profile_checklist, trooth_profile_get, trooth_profile_publish

1 Nov 2 tools appeared trooth_profile_domain_check, trooth_profile_domain_start

31 Oct 4 tool descriptions were rewritten trooth_profile_checklist, trooth_profile_get, trooth_profile_publish and 1 more

24 Oct a tool description was rewritten trooth_company_changes

24 Oct a tool changed the parameters it asks for trooth_company_changes

21 Oct 4 tools appeared trooth_profile_checklist, trooth_profile_get, trooth_profile_publish and 1 more

21 Oct a tool description was rewritten trooth_my_company_record

16 Oct 6 tool descriptions were rewritten trooth_ai_data_use_disclosures, trooth_ask, trooth_my_company_record and 3 more

16 Oct 4 tools appeared trooth_company_changes, trooth_get_fact, trooth_list_companies and 1 more

and 36 more, back to 3 September 2026

Trooth missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://api.trooth.co/public/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trooth

trooth_ai_data_use_disclosures

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.

trooth_ask

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; takes one question of at most 500 characters. 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.

trooth_company_changes

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.

trooth_get_fact

Read one answer from one company's published record: give the company's domain or slug and either a buyer question ID (q_ai_training, q_data_location and ten more, listed in trooth://buyer-questions) or a fact ID such as security.mfa_methods. Returns the sentence, value, provenance word (witnessed, public record, attested or declared), date, freshness window and anchor address, or the negative that applies: no, not_published or not_read. Read only.

trooth_list_companies

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, from the first 100 matches the directory returns; nothing is weighed or put in an order of merit. Read only.

trooth_my_company_record

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.

trooth_outside_in_read

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.

trooth_profile_checklist

Uses your trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when you belong 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; do each agent step yourself. A step that is the owner's own choice carries action_url: tell them in one sentence and carry on. Read only.

trooth_profile_domain_check

Checks DNS now for the TXT record trooth_profile_domain_start gave. Uses your sign-in as owner or admin (or an agent key with profile:publish). Takes domain, and workspace when you belong to several. Returns confirmed true, or confirmed false with the records found and the fix; DNS can take minutes, so check again. Once confirmed, trooth_profile_publish can put the page live.

trooth_profile_domain_start

Starts the proof that the workspace controls its company's domain. Uses your sign-in as owner or admin (or an agent key with profile:publish). Takes domain, and workspace when you belong to several; it states you act for someone authorized to represent the company. Returns the DNS TXT record (host, value) to add with the DNS host's own API. Then call trooth_profile_domain_check. Refusals carry code and fix.

trooth_profile_get

Uses your trooth.co sign-in (or, for an agent that runs on its own, the workspace's agent key with profile:read). Takes only workspace, when you belong 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. With no sign-in: status unauthenticated and the fix. Read only.

trooth_profile_publish

Puts the workspace's saved Trust Profile draft on its public page, which anyone can read. Uses your trooth.co sign-in if your role may publish the page (or an agent key with profile:publish). Takes only workspace, when you belong 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.

trooth_profile_update

Changes fields of the workspace's own Trust Profile DRAFT; the public page changes only on trooth_profile_publish. Uses your trooth.co sign-in if your 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.

trooth_public_trust_profile

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.

trooth_resolve_company

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.

trooth_search_companies

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 in slug order with next_cursor for the next page (the first 100 matches can be paged), 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.

trooth_verify

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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

trooth_compare_companies

removed 15 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://api.trooth.co/public/mcp	streamable-http	answering	80 ms	10 min ago

Alternatives to Trooth

same job, measured the same way

MCP Guardian

by rudraneel93

Security, cost, and health governance proxy for MCP infrastructure

199 installs/wk local only

Architect

by hirosecure

Security reviews for coding agents: diffs checked against your org policy and live infrastructure.

answering

Accelerators

by s2tconsulting

36 tools for AWS infrastructure, security compliance, AI workflows, and ACI governance.

64 installs/wk local only

Memory Pulse

by t-crew

Give any agent self-improving memory you can trust in production. Built-in memory security.

1 032 installs/wk local only

Cybersim Pro

by kayembahamid

Cybersecurity training, simulation, and incident response MCP server

local only

MCP Docker Release Information

by dockersamples

MCP server providing Docker Desktop release notes and security information.

local only

Domain Intelligence

by dataleadspro

Domain overviews for security and sales: registration, infrastructure, and risk signals.

1 tools answering

Masv

by getmasv

Provides tools to use MASV API. MASV is reliable and secure large file transfer service.

60 installs/wk local only

Trooth — questions

Answers built from our own checks of this server.

What can Trooth do?

It exposes 17 tools, read directly from the server on our last check. Among them: trooth_ai_data_use_disclosures, trooth_ask, trooth_company_changes, trooth_get_fact, trooth_list_companies, trooth_my_company_record and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Trooth working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 218 ms. The bar chart above shows every period we have measured.

Did Trooth ever remove tools?

Yes. trooth_compare_companies is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

Is Trooth still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Trooth?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trooth need an API key?

No. Trooth completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Trooth?

It answers our handshake in 218 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.