Give your agent a dated paper trail
Trusty's public MCP connection exposes supported US business records. Start with the exact business and keep the source, dates and limits in the answer. Public records and private paid reads are separate products.
Endpoint: https://api.trytrusty.com/mcp using Streamable HTTP. Official Registry identity: com.trytrusty/business-records v1.0.0. Read the current tool descriptions and schemas before making a request; category support does not mean every category has the same records.
Pick your client
Codex CLI / desktop / IDE on the same host. Merge this TOML table into a chosen trusted project's .codex/config.toml, preserving existing settings. Alternatively, codex mcp add trusty --url https://api.trytrusty.com/mcp writes a server entry to your user configuration. The project file is narrower in scope. See official OpenAI MCP guidance. A configuration entry alone does not establish that a fresh session connected.
Claude Code. Merge this JSON entry into the project's .mcp.json, preserving other servers, or use claude mcp add --transport http --scope project trusty https://api.trytrusty.com/mcp. Approve the project server through the client's normal controls. The explicit "type": "http" matters; a URL-only entry is not a universal format. See Anthropic's connection reference.
A configuration file is one step. Open a fresh trusted client session, inspect its MCP connection status and confirm that Trusty exposes its tools before requesting business records. Client-specific approval and trust controls still apply.
Verify the connection before a business request
A metadata-only check initializes the Streamable HTTP connection, sends the initialized notification and lists tools. Expect check_business, compare_businesses and check_mover. Read their current input schemas; connection metadata does not establish record coverage or a completed business check. The service may identify itself as trusty-mover-check; the Registry name above is its listing identity.
For ChatGPT web, use an available Trusty plugin distribution route. These Codex and Claude Code files are for those clients; they do not install a ChatGPT web connector.
Choose a tool for the actual question
| Tool | Use | Input detail to preserve |
|---|---|---|
check_mover |
A specific mover or its identifier | The business's location, not the customer's address; exact USDOT/MC when supplied |
check_business |
A supported business category | The exact kind enum and identity fields from tools/list |
compare_businesses |
Two to five businesses in a supported category | entries plus required kind; record an evidence gap separately for each side |
Fictional input examples are schema examples only. Do not run them as customer checks. Actual use should follow a real person's requested business task and the current service/client controls. A source outage or thin coverage is a valid result to explain, not permission to retry indefinitely or change the business identity.
Carry the evidence faithfully
Read the full structured result; these fields are useful, not a replacement response schema:
| Returned field | Preserve in the consumer's answer |
|---|---|
status, identity, candidates |
Matched business or unresolved ambiguity; ask for the missing discriminator |
findings[*].source_name, source_url, date, status |
Which source supports which finding and its date/status |
findings[*].evidence when returned |
observed_at versus attempted_at, freshness, current/historical scope and limitations |
checked_at |
Time of the Trusty check, without substituting it for the source's date |
limits, sources_answered |
Missing/unavailable/thin coverage, without converting it into a zero finding |
ask_them_this, card, comparison, businesses when returned |
Relevant next question, attribution and per-business context; do not flatten asymmetric coverage into a ranking |
The tool returns evidence, not a safety certification, rating or purchase recommendation. A FINRA-related path may provide an official BrokerCheck link instead of retrieved restricted records. State-license guidance is not proof that a license was retrieved. For a paid read, hand the customer to the real website to confirm identity and availability; this public connection does not purchase or unlock private reports.
An appropriate final answer names the matched business, summarizes only supported findings, links the sources beside the claims, states dates and unresolved limits, and gives the next useful question. Do not invent sample findings or treat these input examples as completed checks. Never put private prompts or reports into campaign parameters.