Home / MCP registry index / io.github.troothllc/trooth-network
Trooth
io.github.troothllc/trooth-network in the official MCP registry.
Endpoint https://api.trooth.co/public/mcp. Source: github.com/troothllc/trooth-mcp.
The registry describes it as: Machine-Readable Company Profiles: find, search and read any company's Trust Profile, fact by fact.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
trooth_ai_data_use_disclosures trooth_ask trooth_company_changes trooth_get_fact trooth_list_companies trooth_my_company_record trooth_outside_in_read trooth_profile_checklist trooth_profile_get trooth_profile_publish trooth_profile_update trooth_public_trust_profile trooth_resolve_company trooth_search_companies trooth_verify
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-troothllc-trooth-network)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.