io.github.troothllc/trooth-network · v1.1.5 · security
Trooth is healthy: it completed an MCP handshake in 1841 ms and exposes 8 tools.
Machine-Readable Company Profiles: search, read and compare any company's Trust Profile.
Endpoint: https://api.trooth.co/public/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 8 |
| Latency | 1841 ms |
| Last checked (UTC) | 2026-10-15T11:10:13.452Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T11:10:13.452Z | Healthy | 1841 |
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, and which approaches. The company is named by its domain or its Trooth slug, matched exactly. Each row is the company's own declaration and is |
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. Makes no outside request. A question the knowledge base does not cover returns out_of_scope; for a company's record use troo |
trooth_compare_companies | Compare two to 4 companies on the Trooth Network section by section, named by their domains or Trooth slugs separated by commas: each section's state for each company and the rows it published, side by side, with who said them. sections narrows it, e.g. security,privacy,ai. A section a company left |
trooth_my_company_record | Needs an OAuth access token for this server from the authorization server its protected-resource metadata names, for a person who has signed in to trooth.co; no scope is required, and every other tool here needs no token. Reads the company record of the Trooth workspace the signed-in person belongs |
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 an |
trooth_public_trust_profile | Read one company's published record on the Trooth Network, given its domain or Trooth slug, matched exactly (a URL is reduced to its host), never by a similar name; a name several companies share returns their candidates, not a pick. Returns its complete Trust Profile: every section with its state a |
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, 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_tru |
trooth_verify | Check the two signatures on a Trust Ledger Token (tlt2. or tlt. form, or its JTI) against Trooth's own token ledger. 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 n |