Trooth MCP server

trooth-mcp

The Trooth Network over the Model Context Protocol. Four read-only tools, public data, no key.

Trooth operates the Trooth Network: one public, signed, machine-readable record per company, carrying its identity, products and demos, commercial terms, domain and marketing links, people, documents, security and privacy posture, AI practices, procurement terms and relationships. It is Trooth's only product and it is free.

DNS says where a company is. A TLS certificate says the connection is authentic. The Trooth Network says who the company is and what it does with your data.

Trooth witnesses and dates facts. It does not grade, rate or rank anyone. No tool here returns a number that sums a company up, and no such number exists. An agent that wants one is being asked to invent it.

What is in this repository

A license, this README and server.json. There is no server code here, and there is nothing to install.

The server runs in the Worker behind api.trooth.co, which is a different repository. server.json is the manifest published to the official MCP Registry. What this repository is, therefore, is the registry record plus the description of a surface that lives somewhere else, and the honest thing to do is say which of the two any given fact came from.

Everything below was read from a committed file. The lines marked live were observed against the endpoint itself on 2026-09-24 by Trooth's verification script (scripts/verify-public-mcp.mjs in the site repository, not in this one), which writes its report to docs/rebuild-package/PUBLICMCPVERIFICATION.md there. In that run nothing failed: the report lists 85 results that matched what was expected and 11 informational readings. That run is anonymous, from one network location, and says nothing about a later time.

The endpoint

2026-07-28 removed protocol-level sessions and the initialize handshake and added a required server/discover RPC. Which era a request belongs to is decided by the presence of the reserved meta key, not by the version value, so an unknown future version is refused rather than quietly served as an old one. Live:** a 2026-07-28 request that omits the MCP-Protocol-Version header is refused with -32020, and so is an Mcp-Method header that contradicts the body.

An older client is not stranded. Live: initialize asking for 2025-06-18 gets 2025-06-18 back, asking for 2024-11-05 gets 2024-11-05, and an unrecognized version falls back to 2025-06-18 rather than failing.

The four tools

Shortened. The full README is on GitHub.