Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Trooth Network is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Check any company's witnessed trust record on the Trooth Network, live and read-only.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trooth-network-mcp https://api.trooth.co/public/mcp
# 2 — ask your agent for something these tools do
# trooth_ai_data_use_disclosures, trooth_ask, trooth_company_changes and 12 more
Trooth Network costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http trooth-network-mcp https://api.trooth.co/public/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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, which approaches), named by its domain or its Trooth slug, matched exactly. Each row is the company's own declaration and is labeled so, with whether Trooth observed a supporting policy clause: not observed means Trooth has not read one, neve
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company domain (e.g. acme.com) or Trooth slug |
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; takes one question of at most 500 characters. Makes no outside request. A question the knowledge base does not cover returns out_of_scope; for a company's record use trooth_public_trust_profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | A question about Trooth |
List how one company's published record changed: give its domain or slug and, optionally, since (an ISO 8601 date or time). Returns record versions oldest first, each with the fact keys changed, added or removed, per-fact edits (old value, new value, time, role) when the record carries them, with next_cursor for more, and the recalls the company stored or changed in Semanto, oldest first, with rec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company domain (e.g. acme.com) or Trooth slug |
| since | string | no | Optional. Only changes at or after this ISO 8601 date or time, e.g. 2026-10-01 |
| cursor | string | no | Optional. The changes.next_cursor of the previous answer, sent with the same company and since. |
| recall_cursor | string | no | Optional. The changes.recall_cursor of the previous answer: only recalls recorded after it are returned. |
Read one answer from one company's published record: give the company's domain or slug and either a buyer question ID (q_ai_training, q_data_location and ten more, listed in trooth://buyer-questions) or a fact ID such as security.mfa_methods. Returns the sentence, value, provenance word (witnessed, public record, attested or declared), date, freshness window and anchor address, or the negative tha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company domain (e.g. acme.com) or Trooth slug |
| question | string | no | A buyer question ID, e.g. q_ai_training. Give this or fact. |
| fact | string | no | A fact ID, <section>.<field>, e.g. security.mfa_methods. Give this or question. |
List the companies published on the Trooth Network by what they published: industry, data region, witnessed or not, and claimed (the company published its own profile) or unclaimed. Returns 20 entries per page in alphabetical order of record identifier with next_cursor, from the first 100 matches the directory returns; nothing is weighed or put in an order of merit. Read only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| industry | string | no | Optional. Only companies in this industry, e.g. Fintech |
| data_region | string | no | Optional. Only companies that publish this data residency region, e.g. EU |
| witnessed | boolean | no | Optional. true for companies Trooth witnessed, false for those it has not |
| claimed | boolean | no | Optional. true for companies that published their own profile, false for listed domains with none |
| cursor | string | no | Optional. The page.next_cursor of the previous answer, sent with the same filters. |
Needs an OAuth access token for this server, for a person who has signed in to trooth.co (no scope is required; the public tools here need no token, and an agent key is not accepted), and takes no arguments: the workspace comes from the token's subject and never from an argument. Reads the company record of the Trooth workspace the signed-in person belongs to and returns its name, its slug and the
Takes no parameters.
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 and names resolving to private, loopback or link-local addresses are refused; redirects are reported,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain to read, e.g. example.com |
Needs the workspace's agent key (permission profile:read). Takes no arguments. Lists the steps left before the workspace's Trust Profile can be published, each marked for the agent or for a person, with state done, todo or unknown and how to do it. A person's step carries action_url: give that address to the person in one sentence and carry on with your own steps. Read only.
Takes no parameters.
Needs the workspace's agent key (header Authorization: Bearer tra_... on this MCP connection; permission profile:read). Takes no arguments. Returns the workspace's own Trust Profile DRAFT as saved now, its revision (send it as if_match to trooth_profile_update), whether it is published, and its public address. With no key: status unauthenticated and the fix. Read only.
Takes no parameters.
Puts the workspace's saved Trust Profile draft on its public page, which anyone can read. Needs the agent key with profile:publish. Takes no arguments. Success: status published with public_url. A first publish needs a person to prove the company's domain: the answer is then code human_action_required with an action_url to give that person; the draft stays saved. Every other refusal carries trooth
Takes no parameters.
Changes fields of the workspace's own Trust Profile DRAFT; the public page changes only on trooth_profile_publish. Needs the agent key with profile:write. Each change names one field by JSON Pointer (/tagline, /founders/-) with a value and its source { url, quote } from the company's own page, or state not_published with a reason. Returns each change as applied or rejected (with code and fix) and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changes | array | yes | The changes, applied in order; a rejected change leaves the draft as it was and the ones after it still apply. Fields and their types: https://trooth.co/api/v1/profile/schema. Fields a person keeps (t |
| if_match | string | no | Optional. The revision you read with trooth_profile_get. When someone changed the draft since, nothing is saved and the answer is code revision_changed with the new revision. |
| idempotency_key | string | no | Optional. A key of your choosing for this exact set of changes. Retrying with the same key and changes returns the first answer with no second write. When omitted, one is made and returned as idempote |
| dry_run | boolean | no | Optional. true checks every change and returns what would be kept, and saves nothing. |
Read one company's published record on the Trooth Network, given its domain or Trooth slug, matched exactly, never by a similar name; a name several companies share returns their candidates, not a pick. Returns a status and a provenance label with the complete Trust Profile (detail full, the default) or a short answer (detail summary, the better first call). A record is keyed by its domain and doe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company domain (e.g. acme.com) or Trooth slug; a URL is reduced to its host |
| detail | string | no | full (default): the complete profile, section by section. summary: the short answer, the contract summary members and where the record is; ask for it first. |
| sections | string | no | Optional. Comma-separated section names to return, from: overview, identity, history, funding, product, pricing, stack, security, privacy, ai, hosting, infrastructure, procurement, relationships, proo |
Find the published Trooth Network record for a company given a domain, web address, Trooth slug or name; a company-register identifier, Crunchbase address or Wikidata ID is accepted and answered not_found, because Trooth keeps no lookup by them. Returns the record ID, its canonical https address and why it matched, or every candidate with why each matched (status ambiguous, none chosen), or not_fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | A domain, web address, Trooth slug, legal or trading name, company-register identifier, Crunchbase address or Wikidata ID |
| kind | string | no | Optional. What the identifier is; read from its form when omitted. A register identifier is read as a name unless kind says otherwise. |
Search the companies published on the Trooth Network by name, domain, tagline or category, optionally within one industry. Returns up to 10 entries per page in slug order with next_cursor for the next page (the first 100 matches can be paged), 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_trust_pr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to match: a company name, a domain, a category such as payroll or observability |
| industry | string | no | Optional. Only companies in this industry, e.g. Fintech |
| cursor | string | no | Optional. The page.next_cursor of the previous answer, sent with the same query and industry. |
Check the two signatures on a Trust Ledger Token (tlt2. or tlt. form, or its JTI) against Trooth's own token ledger. A Trust Ledger Token is a signed token a company issues through Trooth about its own declared claims: the company signs the claims and Trooth signs the event of issuing it. Returns valid, invalid (a signature does not check out), expired or revoked, or unclaimed when no token matche
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | A Trust Ledger Token (tlt2. or tlt. form) or its JTI |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Trooth Network or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| trooth_ai_data_use_disclosures | no tags | |
| trooth_ask | no tags | |
| trooth_company_changes | no tags | |
| trooth_get_fact | no tags | |
| trooth_list_companies | no tags | |
| trooth_my_company_record | no tags | |
| trooth_outside_in_read | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| trooth_profile_checklist | no tags | |
| trooth_profile_get | no tags | |
| trooth_profile_publish | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| trooth_profile_update | state-write | state-write: declares readOnlyHint: false |
| trooth_public_trust_profile | no tags | |
| trooth_resolve_company | no tags | |
| trooth_search_companies | no tags | |
| trooth_verify | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.7.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Trooth Network can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.