Home / MCP registry index / com.ruzora/ruzora
com.ruzora/ruzora
com.ruzora/ruzora in the official MCP registry.
Endpoint https://mcp.ruzora.com/mcp.
The registry describes it as: Pre-vetted senior LATAM engineers for US startups: hiring leads, open roles, applications.
We read its 35 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
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
list_open_roles get_job_details get_company_info submit_candidate_application create_factory_inquiry build_role_scorecard compare_hiring_models calibrate_seniority write_job_description lint_job_post check_pay_transparency triage_resumes detect_resume_injection review_code_sample check_identity_risk build_interview_kit developer_interview_questions design_coding_assessment score_interview_notes send_coding_challenge get_vetting_status plan_reference_check build_onboarding_plan verify_ruzora_badge search_vetted_engineers check_market_supply request_vetted_shortlist check_hiring_fit explain_ruzora_terms start_honest_read submit_honest_read request_project_scoping_call verify_work_email confirm_work_email save_role
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-ruzora-ruzora)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.