Trooth

DNS says where a company is; Trooth says who it is.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    DNS says where a company is; Trooth says who it is. One public, signed record per company.

    How to connect

    How to connect Trooth to Claude

    The server address to paste into Claude settings:

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

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Trooth to ChatGPT

    The server address to paste into ChatGPT settings:

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

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Trooth to Cursor

    The server address to paste into Cursor settings:

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

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (4)

    Raw names from tools/list. Only developers need these.

    trooth_public_trust_profileLook up a company's published, witnessed Trust Profile on Trooth by domain or slug. Returns the witnessed standing, pillar summary, and evidence-chain stats for companies that publish an OS profile, or the witnessed Network standing (signed scan result) for companies listed in the public directory. Unknown companies return an honest not-found.
    trooth_outside_in_readPerform a live, neutral read of a domain's public security surface right now: HTTPS/TLS reachability, common security headers (HSTS, CSP, nosniff, frame protection, referrer policy), and /.well-known/security.txt. These are observations from the public internet, not witnessed evidence and not a grade.
    trooth_askAsk about Trooth itself: what the Trooth Network is, what one company record carries, why a company needs one, pricing (free), and how witnessing works. The Trooth Network is Trooth's only product. Answers come from Trooth's curated knowledge base.
    trooth_verifyVerify a Trooth Trust Ledger Token (a signed, portable trust receipt in tlt2 / tlt form, or its JTI). Re-runs both signatures independently and returns whether the token is valid, expired, revoked, or tampered - plus honest provenance: Trooth's outer signature attests only the witnessing event and the byte-for-byte payload at issuance, never the truthfulness of the declared claims. Unknown tokens return an honest not-found.