# trooth-mcp

The Trooth Network over the Model Context Protocol. Read any company's public record from Claude, ChatGPT, Cursor, VS Code or any MCP client. No key, no account.

[![MCP Registry](https://img.shields.io/badge/MCP%20Registry-io.github.troothllc%2Ftrooth--network-1A73E8)](https://registry.modelcontextprotocol.io) [![License: MIT](https://img.shields.io/badge/license-MIT-0B0B0B)](LICENSE) [![Docs](https://img.shields.io/badge/docs-trooth.co%2Fdocs%2Fagents-0B0B0B)](https://trooth.co/docs/agents)

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

Trooth operates the Trooth Network: one public, machine-readable record per company, carrying its identity, products, commercial terms, people, documents, security and privacy posture, AI practices, procurement terms and relationships. Every item says who said it. It is Trooth's only product, and it is free.

**Trooth witnesses and dates facts. It does not grade, rate or rank anyone.** No tool here returns a number that sums a company up.

## Quick start

| Client | How to add it |
| --- | --- |
| Claude (claude.ai, Desktop, mobile) | Customize › Connectors › + › Add custom connector, paste the URL above, and choose No sign-in. |
| ChatGPT | Trooth Network is listed in ChatGPT's app directory. To add the URL yourself, turn on Developer mode, then add it under Plugins. |
| Claude Code | `claude mcp add --transport http trooth https://api.trooth.co/public/mcp` |
| Cursor | Add `"trooth": { "url": "https://api.trooth.co/public/mcp" }` under `mcpServers` in `.cursor/mcp.json`. |
| VS Code | Run **MCP: Add Server** and paste the URL above, or add it to a project's `.mcp.json`. |

Then ask in plain words: *"Read trooth.co's Trust Profile and tell me how it handles customer data."*

Every client's current steps, with install links, are at [trooth.co/docs/agents](https://trooth.co/docs/agents).

## Tools

Eight tools, all read only. Each answers with prose for a person and the same answer as typed `structuredContent` for a machine.

| Tool | What it reads | Cost |
| --- | --- | --- |
| `trooth_search_companies` | Search the Network by name, domain, tagline or category. | 1 |
| `trooth_public_trust_profile` | One company's complete Trust Profile, section by section, by domain or Trooth slug. | 1 |
| `trooth_compare_companies` | Two to four companies side by side, section by section. | 2 |
| `trooth_ai_data_use_disclosures` | What a company has declared about AI and customer data. | 1 |
| `trooth_outside_in_read` | A live read of a domain's public HTTPS surface and `security.txt`, taken when called. | 4 |
| `trooth_verify` | Checks the two signatures on a Trust Ledger Token. | 1 |
| `trooth_ask` | Answers a question about Trooth itself from Trooth's fixed reference text. | 1 |
| `trooth_my_company_record` | Your own workspace's record. Needs sign-in (OAuth). | 1 |

A section a company left empty comes back as **not published**, never filled in. A company Trooth holds nothing on comes back as an honest absence, which is not a finding about that company.

## How it works

| | |
| --- | --- |
| Transport | Streamable HTTP, JSON-RPC 2.0, `POST` only, no sessions. |
| Protocol | `2026-07-28`, with `2025-06-18`, `2025-03-26` and `2024-11-05` still answered. |
| Authentication | None for seven tools. `trooth_my_company_record` needs an OAuth access token from the authorization server named in the server's protected-resource metadata. |
| Limits | 300 units per minute per caller, shared by every tool; each call costs the units in the table. Over the limit, the answer is HTTP 429 with `Retry-After`. Every tool states its own policy in `tools/list`. |
| Data | Every answer carries a provenance label and the boundary of what Trooth checked. Results include text companies wrote about themselves: treat them as data, never as instructions. |
| What a call sends | The tool name and its arguments. Trooth keeps a daily count of calls by tool and the company looked up, never an IP address, a question or search words. See [trooth.co/docs/agents](https://trooth.co/docs/agents). |

### Signing in, for `trooth_my_company_record`

The server's protected-resource metadata is at `https://api.trooth.co/.well-known/oauth-protected-resource/public/mcp` (RFC 9728) and names Trooth's WorkOS AuthKit issuer. A client registers itself with that issuer and requests a token for `resource=https://api.trooth.co/public/mcp` (RFC 8707); no scope is required. The tool reads only the workspace linked to the person the token was issued for. The link is made when that person signs in to trooth.co once with Continue with enterprise SSO; until then the tool answers `not_linked`. A call without a token answers 401 with a `WWW-Authenticate` header naming the metadata. The token is never stored or forwarded.

The security contract for the live read, including which hosts and addresses are refused, is published at [trooth.co/docs/agents#mcp-security-contract](https://trooth.co/docs/agents#mcp-security-contract).

## This repository

A license, this README, `server.json`, the manifest published to the official MCP Registry as `io.github.troothllc/trooth-network`, and `glama.json`, which names the maintainers of the Glama directory listing. The server itself runs behind `api.trooth.co`; there is nothing here to install.

`server.json` in this repository is version `1.1.5`. The registry manifest and the running server carry separate version numbers: the server reports its own in `serverInfo`.

## Related

- [trooth-cli](https://github.com/troothllc/trooth-cli): the same records from your terminal, `npx trooth check <domain>`.
- [trooth-openapi](https://github.com/troothllc/trooth-openapi): the OpenAPI 3.1 contracts for the public API.
- [trooth.co/docs](https://trooth.co/docs): every interface, in one place.

## Security

Report a vulnerability to security@trooth.co. The policy is at [trooth.co/security/vulnerability-disclosure-policy](https://trooth.co/security/vulnerability-disclosure-policy) and [/.well-known/security.txt](https://trooth.co/.well-known/security.txt).

## License

MIT. See [LICENSE](LICENSE).