Home / MCP registry index / co.trooth/trooth
Trooth
co.trooth/trooth in the official MCP registry.
Endpoint https://mcp.trooth.co/.
The registry describes it as: Every company's public record on the Trooth Network, and Semanto: a company's website, signed.
We read its 39 tools on 2026-11-16. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http trooth https://mcp.trooth.co/{
"mcpServers": {
"trooth": {
"url": "https://mcp.trooth.co/"
}
}
}code --add-mcp '{"name":"trooth","type":"http","url":"https://mcp.trooth.co/"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
trooth_setup trooth_hub_sync enable_toolset search_tools call_tool call_write_tool 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_diff trooth_profile_domain_check trooth_profile_domain_start trooth_profile_get trooth_profile_import trooth_profile_publish trooth_profile_remediation_plan trooth_profile_update trooth_profile_validate trooth_public_trust_profile trooth_resolve_company trooth_search_companies trooth_verify trooth_semanto_status trooth_semanto_setup_read_again trooth_semanto_setup_choose trooth_semanto_review_get trooth_semanto_setup_confirm trooth_semanto_sign trooth_semanto_install_guide trooth_semanto_install_check trooth_semanto_page trooth_semanto_facts trooth_semanto_answer trooth_semanto_statement_check
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-16):
8a8fb09a6ab1979d. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/co-trooth-trooth)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.