Every published company record now answers twelve buyer questions from its own fields and gives each fact an ID and a sentence that stands on its own. Trooth's Model Context Protocol (MCP) server, version 1.8.0, adds four read-only tools, two prompts and three resources, and records can now be asked about at /ask, downloaded in bulk and followed in feeds.
What changed
Every published company record now follows the shared record contract of 2026-10-16. It answers twelve buyer questions, such as whether the company trains artificial intelligence (AI) models on customer data and where customer data is stored, each from the record's own fields, with its provenance, its date and a link to that answer on the company's Trust Profile. A question the record does not hold is marked not published; nothing is worked out from other fields. Answers keep three negatives apart: no means the record holds a negative value, not published means the company has not published it, and not read means Trooth's reading did not read it. Each fact has a stable ID, such as security.mfa_methods, and a sentence that says on its own who said it, when and what. The record's summary names each check in Trooth's latest reading that did not come out as expected, with what was expected and what was observed. Controls that the company's own Trust Center lists as not yet in place are shown as the company states them. Where Trooth observed the same thing a company declares, its observation is shown beside the declaration. Declared facts carry their edit history where the record keeps one: the old value, the new value, when, and the role that made the change (owner, admin, member or Trooth), never a name. Trooth's Model Context Protocol (MCP) server is now version 1.8.0. Four read-only tools are new: trooth_resolve_company finds a company's record from a domain, web address, Trooth slug or name; trooth_get_fact reads one buyer question answer or one fact; trooth_list_companies lists companies by industry, data region, whether Trooth witnessed them and whether they published their own profile, in alphabetical order; and trooth_company_changes reads how a record changed, version by version. trooth_search_companies now returns its results a page at a time with a cursor. Two prompts are new, vendor_due_diligence and vendors_side_by_side, and three resources: trooth://provenance-glossary, trooth://buyer-questions and trooth://schema. Every tool is marked read only, and only trooth_outside_in_read, which fetches the domain you name, is marked as reaching beyond Trooth. When one of the new tools cannot answer as asked, its answer says why with an error code. Beside the server: /ask answers one of the twelve buyer questions about one company from that company's record and generates no text of its own; /api/network/bulk downloads every public record, one per line, with a manifest of versions and hashes; the Network and each company publish a machine-readable JSON Feed of record changes; /docs/query-privacy says what Trooth keeps when you or an agent ask about a company; /network/corrections lists every settled challenge to a fact on a published record, with its outcome and date; and /network/accuracy is where the results of checking answers against the records they cite are printed.
Why it changed
A buyer looking into a vendor asks the same questions every time, and an agent answering for them needs to cite one fact with who said it and when, and to keep a company that said no apart from one that has said nothing.
Who is affected
- Affected: Anyone who reads a company's record on the Trooth Network, people and agents alike, and developers who read records through /api/network/profile or the Model Context Protocol (MCP) server. Companies with a published record do not need to do anything: every answer is read from what their record already holds.
- Availability: Everyone, from today, with no account: the records, /ask, the bulk download, the feeds and every tool on the Model Context Protocol (MCP) server except the one that reads your own workspace after sign-in.
- Release stage: Available.
- Areas: Trust Profiles, Network, API, MCP server.
What to do
No action required. Nothing anyone builds on changed. The new members of /api/network/profile are added to contract 2 and remove nothing, and the seven tools the Model Context Protocol (MCP) server already had keep their names, their required arguments and the answers they mark as errors. To use the new tools, ask the server for its list of tools again.
Versions and migration
- Trooth MCP server:
1.8.0 - Record contract:
2026-10-16
Dates
- Announced: October 16, 2026, the day this entry was written. Entries are never backdated.
- Released: October 16, 2026.
What this does not fix
The record for this server in the MCP Registry, version 1.1.7, is prepared and is published separately; until it is read back from the registry, the registry lists 1.1.6. No accuracy run has been made yet, and /network/accuracy says so rather than showing a figure. Edit history appears only on facts whose record keeps one, and controls not yet in place only for companies whose Trust Center lists them.