Home / MCP server directory / io.trueinterview/trueinterview
TrueInterview
io.trueinterview/trueinterview in the official MCP registry.
Endpoint https://trueinterview.io/api/mcp.
The registry describes it as: Interview prep by company and round, plus job search and application prep, in your own agent.
We read its 40 tools on 2026-11-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 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 trueinterview https://trueinterview.io/api/mcp{
"mcpServers": {
"trueinterview": {
"url": "https://trueinterview.io/api/mcp"
}
}
}code --add-mcp '{"name":"trueinterview","type":"http","url":"https://trueinterview.io/api/mcp"}'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
get_account get_trueinterview_resource search_jobs recommend_jobs skip_job get_job get_company_intel search_questions search_site_content get_prep_plan get_my_progress list_my_conversations get_my_conversation list_context_notes save_context_note delete_context_note get_resume get_application_checklist update_resume import_resume update_application_answers update_job_search match_resume_to_job prepare_application screen_jobs report_application claim_setup_handoff report_setup_progress tailor_resume write_cover_letter generate_application_documents draft_answers list_applications track_application update_application list_contacts find_contacts update_contact get_playbook report_mcp_issue
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-22):
34181b0cc30acc79. 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/io-trueinterview-trueinterview)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. MCP tool poisoning, explained. 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 the MCP server directory.