com.ruzora/ruzora

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Pre-vetted senior LATAM engineers for US startups: hiring leads, open roles, applications.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "ruzora": {
      "url": "https://mcp.ruzora.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (35)

• list_open_roles read-only

  Get all currently open engineering roles at Ruzora. Returns titles, tech stacks, experience levels, and application URLs.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_job_details read-only

  Get detailed information about a specific job role including responsibilities, requirements, and tech stack.

  Parameters:

  • slug (required) — string — Job slug (e.g., "devops-engineer", "ai-engineer")

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_company_info read-only

  Get comprehensive information about Ruzora's services, process, value proposition, and differentiators.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• submit_candidate_application destructive

  Apply to Ruzora's talent network. For software engineers in LATAM interested in remote positions with US startups paying USD salaries. Consent: submitting sends these details to Ruzora (US-hosted) for recruiting. See https://www.ruzora.com/privacy.

  Parameters:

  • first_name (required) — string — First name
  • last_name (required) — string — Last name
  • email (required) — string — Email address
  • role_category (required) — string — Primary role category
  • phone — string — Phone number
  • message — string — Brief intro or relevant experience
  • linkedin_url — string — LinkedIn profile URL

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• create_factory_inquiry

  Request a custom software project from Ruzora's Software Factory. Fixed-price development by senior LATAM engineers.

  Parameters:

  • name (required) — string — Contact person name
  • email (required) — string — Business email
  • company (required) — string — Company name
  • description (required) — string — What you want built
  • budget — string — Budget range (USD)
  • timeline — string — Desired timeline

  Hints: read-only no · destructive no · idempotent no · open-world yes

• build_role_scorecard read-only

  Turn a vague engineering hire ("we need a senior full-stack dev") into a role scorecard: mission, measurable 12-month outcomes, must-haves, competencies and an interview map. Start here before writing a job post.

  Parameters:

  • role_title (required) — string — Working title, e.g. "Senior backend engineer"
  • stack — string — Main technologies
  • company_context — string — Company stage, product, team today, why this hire now
  • what_success_looks_like — string — What this person must have achieved in 6-12 months, in your words

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• compare_hiring_models read-only

  Neutral 12-month cost and risk comparison of US employee, US contractor, freelancer, agency, staff augmentation and international contractor/EOR, on your own numbers. Published by Ruzora, a staff augmentation firm; every option uses the same formula.

  Parameters:

  • role (required) — string — Role and level
  • numbers — string — Salary or quotes you have per option, location, start-by date, how long you need the person

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• calibrate_seniority read-only

  Work out what level a role really needs (by scope, not years), or what level a candidate really is from a CV, interview notes or an assessment report. Flags title inflation and gives 3 questions that separate adjacent levels.

  Parameters:

  • mode (required) — string — "role" = what level do I need; "candidate" = what level is this person
  • company_size — string — Your company size and stage, e.g. "8 people, seed"
  • role_description — string — The work: what they will own, who reviews them, how vague the goals are (or paste a role scorecard)
  • candidate_evidence — string — CV text, interview notes, an interview scorecard or an assessment report (remove contact details, IDs and dates of birth)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• write_job_description read-only

  Write a software engineer job post senior engineers answer, plus a compliance check: pay range rules by location, citizenship wording, exclusionary language and requirement inflation.

  Parameters:

  • role_title (required) — string — Role title
  • details — string — Scorecard or notes: what they will own, stack, team, pay range, remote rules, hiring locations, benefits

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• lint_job_post read-only

  Paste any engineering job post and get a fix list: missing pay range where required, "US citizens only", age/gender/origin-coded words, salary-history asks, too many must-haves. Deterministic; nothing stored.

  Parameters:

  • post_text (required) — string — The full job post text
  • locations — array — Where the role can be filled (for pay-range rules)
  • employee_count — number — Total employees

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_pay_transparency read-only

  Which US state and city pay-transparency laws apply to a job post (pay range, benefits, close date), by hiring location, company size and remote status, with the statute for each. Dated; not legal advice.

  Parameters:

  • locations (required) — array — Where the role can be filled, e.g. ["California", "New York City"] or ["remote US"]
  • remote — boolean — True if the role is remote
  • employee_count — number — Total employees (thresholds differ by state)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• triage_resumes read-only

  Screen engineering CVs against your must-haves with evidence scores, blind mode, hidden-text flags and screening-call questions. Organizes evidence; never rejects anyone for you.

  Parameters:

  • resumes — string — Pasted CV text, one after another. Remove contact details, IDs and dates of birth.
  • blind_mode — boolean — Strip names, photos, schools and dates before scoring
  • must_haves — string — The role's must-haves (or paste a role scorecard)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• detect_resume_injection read-only

  Check resume text for hidden instructions aimed at AI screeners ("ignore previous instructions", invisible characters, keyword stuffing) before any AI reads it. Flags for a human; never rejects.

  Parameters:

  • resume_text (required) — string — The resume text as extracted from the file
  • hidden_segments — array — Optional: text your PDF tool marked as white, tiny or hidden

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• review_code_sample read-only

  Plain-English review of a candidate's GitHub repo or code sample for non-technical hirers: quality signals, authorship checks, a risky-function trace and questions that reveal who really wrote it.

  Parameters:

  • role — string — Role and level you are hiring for
  • code_or_repo — string — Paste the code, file excerpts, README and commit history (or describe the repo)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_identity_risk read-only

  Identity-verification protocol for remote engineering hires (fake candidates, stand-ins, North Korean IT worker schemes per FBI guidance) and a red-flag log for a specific candidate. Same checks for every finalist; never based on origin or accent.

  Parameters:

  • situation — string — Where you are in the process and what made you suspicious, if anything. Do not paste ID documents.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• build_interview_kit read-only

  A lean structured interview loop for an engineering role: stages, owners, time budget, fixed questions, an anchored 1-4 rubric and a legal check of your questions.

  Parameters:

  • role (required) — string — Role and level
  • details — string — Must-haves (or a role scorecard), who can interview, any questions you already use

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• developer_interview_questions read-only

  An interview kit for founders and managers who are not engineers: questions, what a strong answer and a bluff sound like, and follow-up ladders tailored to the stack and level.

  Parameters:

  • role (required) — string — Role, level and stack
  • details — string — What the person will own, and any questions you planned to ask

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• design_coding_assessment read-only

  Design a coding test that still works when candidates have AI: seeded-bug review, extend-a-codebase or a paid trial, with a hidden rubric and the follow-up conversation that tests understanding.

  Parameters:

  • role (required) — string — Role and level
  • stack (required) — string — Language and framework the task should use
  • details — string — Time you can ask of candidates, your AI policy, what the job really involves

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• score_interview_notes read-only

  Turn raw interview notes into an anchored scorecard per interviewer and a debrief memo with evidence, disagreements and bias flags. You make the decision.

  Parameters:

  • notes — string — Each interviewer's raw notes, labeled by interviewer and stage
  • must_haves — string — The role's must-haves or scorecard

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• send_coding_challenge

  Runs Ruzora's coding challenge + technical questions (~25 min, free) on a candidate the user found; returns a candidate link and a status link. Needs the user's confirmation that the candidate knows. Sends both names, the email, company and profile links to Ruzora.

  Parameters:

  • requester_name (required) — string — Full name of the person hiring
  • work_email (required) — string — Their WORK email (personal inboxes are refused). The report and status go here.
  • company (required) — string — Hiring company name
  • role (required) — string — Role being hired, e.g. "Senior backend engineer"
  • candidate_name (required) — string — Candidate's name
  • candidate_informed (required) — boolean — True only when the user has confirmed the candidate knows they will receive a technical assessment from Ruzora on the company's behalf.
  • stack — string — Main stack, e.g. "Python, Django, Postgres"
  • buyer_token — string — Proof the user verified this work email: the buyer_token from confirm_work_email (valid 7 days). No token yet? Call verify_work_email first.
  • candidate_github_url — string — Optional GitHub profile URL
  • candidate_linkedin_url — string — Optional LinkedIn profile URL

  Hints: read-only no · destructive no · idempotent no · open-world yes

• get_vetting_status read-only

  Check progress on a coding challenge you sent through Ruzora: not started, in progress, finished, or expired, and scores once the report is delivered. Pass the status page URL.

  Parameters:

  • status_url (required) — string — The status page URL (or its token) returned when the challenge was sent

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• plan_reference_check read-only

  A reference-check plan for an engineering finalist: verify the referees are real, a call script aimed at the risks found in interviews, and a risk register for the answers.

  Parameters:

  • referees — string — Who the candidate offered as references (names, companies, relationship)
  • candidate_summary — string — Role, the candidate's CV highlights, and the open risks from interviews

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• build_onboarding_plan read-only

  A 30-60-90 day plan for a new software engineer: least-privilege day-1 access, first PR in week one, a buddy plan, and milestones tied to the role scorecard.

  Parameters:

  • role (required) — string — Role and level
  • details — string — Start date, team, systems they will touch, the role scorecard outcomes, employee or contractor

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• verify_ruzora_badge read-only

  Check that a candidate's "Ruzora Vetted" badge is real and current, which stacks it covers, and when the vetting happened. Pass the badge ID or badge URL.

  Parameters:

  • badge (required) — string — Badge ID (a UUID) or the badge/verification URL

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• search_vetted_engineers read-only

  See blind profiles of senior engineers in Latin America who already passed Ruzora's coding and interview vetting and are available now, filtered by stack, level and US-hours overlap.

  Parameters:

  • stack (required) — array — Technologies, e.g. ["React", "Node", "AWS"]
  • page — number — Optional page of results: 1 (default) is the best matches. Send 2, 3... only when the user asks to see more engineers for the same search; the previous result names the next page.
  • level — string — Optional seniority filter
  • min_overlap_hours — number — Optional minimum overlap with US working hours

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_market_supply read-only

  Whether Ruzora has vetted senior engineers in Latin America available now for a stack: each stack reads Available or On request. Words only: no counts, no profiles.

  Parameters:

  • stack — array — Optional: technologies to look for, e.g. ["Go", "AWS"]

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• request_vetted_shortlist

  Ask Ruzora for a shortlist of vetted senior engineers in Latin America for a role (ideally from a role scorecard). A vetted shortlist within 72 hours; profiles are blind until an agreement is signed. Needs a work email. Sends the name, email and company given to Ruzora.

  Parameters:

  • full_name (required) — string — Hiring manager full name
  • work_email (required) — string — Work email (personal inboxes are refused). The shortlist goes here.
  • company (required) — string — Company name
  • role (required) — string — Role title, e.g. "Senior backend engineer"
  • seniority (required) — string — Seniority: mid (3-5 years), senior (5-8 years) or staff (8+ years, lead)
  • notes — string — Context: what they will own, time-zone needs, the role scorecard summary
  • timeline — string — When they should start, e.g. "within a month"
  • engineers — number — How many engineers (default 1)
  • buyer_token — string — Proof the user verified this work email: the buyer_token from confirm_work_email (valid 7 days). No token yet? Call verify_work_email first.
  • required_skills — array — Must-have skills only (hard filter), e.g. ["Python", "Postgres"]
  • preferred_skills — array — Nice-to-have skills (ranking only)

  Hints: read-only no · destructive no · idempotent no · open-world yes

• check_hiring_fit

  Answer Ruzora's 5 quick questions (roles, runway, budget per engineer, timing) to see whether a quote makes sense and the next step to it: usually a 15-minute call with the founder. Explains the flat monthly pricing; no price list. Sends the name, email and company given to Ruzora.

  Parameters:

  • full_name (required) — string — Full name
  • work_email (required) — string — Work email
  • your_title (required) — string — The asker's own position: founder_ceo, cto_vp_eng, eng_manager, hr_ops_finance or other
  • role_count (required) — string — How many engineers
  • runway (required) — string — Company runway: under 6 months, 6-12, 12-18, 18+, or bootstrapped without revenue
  • seat_budget (required) — string — Monthly budget per engineer: under $4,500, $4,500-5,999, $6,000-7,999, $8,000+, or not sure
  • timing (required) — string — When you need them: asap, within_month, one_to_three_months, three_plus or no_timeline
  • company — string — Company name
  • buyer_token — string — Proof the user verified this work email: the buyer_token from confirm_work_email (valid 7 days). No token yet? Call verify_work_email first.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• explain_ruzora_terms read-only

  Ruzora's standard terms in plain words, from the published terms: pricing model, the 90-day initial commitment and notice, the 60-day replacement guarantee and its limits, refunds, the factory warranty, speed, and how an engagement starts.

  Parameters:

  • topic — string — Which term: all, pricing, commitment, refunds, guarantee, factory_warranty, delivery or process

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• start_honest_read read-only

  Ruzora's free scoping interview for an app or software idea: returns the interview your AI runs with the user, producing an Idea Read (what to build first, hard parts, build-or-buy verdict) that Ruzora can turn into a verdict and a PDF.

  Parameters:

  • idea — string — Optional: the idea in the user's words, to start the interview from

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• submit_honest_read

  Send the Idea Read your AI wrote (from start_honest_read) to Ruzora to get a verdict (keep going yourself, one developer, or a small team) and the PDF by email. Any email works. Sends the email, first name and Idea Read given here to Ruzora, which uses them to send the report.

  Parameters:

  • email (required) — string — Where to send the PDF (personal email is fine)
  • idea_read_markdown (required) — string — The full Idea Read text the interview produced
  • first_name — string — First name for the report

  Hints: read-only no · destructive no · idempotent no · open-world yes

• request_project_scoping_call

  For anyone who wants an app or software built, or a failing app or agency project rescued, by Ruzora's Software Factory (fixed price, milestones). Checks fit (budget, timing) and returns a scoping-call booking link when it fits. Sends the name, email and company given to Ruzora.

  Parameters:

  • full_name (required) — string — Full name
  • work_email (required) — string — Email
  • kind (required) — string — "build" = new app or software; "rescue" = fix or take over a failing app or agency project
  • budget (required) — string — Budget: under $15K, $15-50K, $50-150K, over $150K, or not sure
  • timing (required) — string — When to start
  • your_title (required) — string — The asker's own position: founder_ceo, cto_vp_eng, eng_manager, hr_ops_finance or other
  • company — string — Company or business name
  • buyer_token — string — Proof the user verified this work email: the buyer_token from confirm_work_email (valid 7 days). No token yet? Call verify_work_email first.
  • project_summary — string — One paragraph: what to build or what is broken (shown back to help you prepare the call)

  Hints: read-only no · destructive no · idempotent no · open-world yes

• verify_work_email

  Step 1 before a Ruzora action that needs a verified buyer: emails the user a 6-digit code and a confirm link. The user reads the code back; confirm_work_email takes it. Sends the email address to Ruzora.

  Parameters:

  • work_email (required) — string — The user's WORK email (personal inboxes are refused)
  • for_tool — string — Which action this verification is for (the email names it, so the user knows what they confirm)

  Hints: read-only no · destructive no · idempotent no · open-world yes

• confirm_work_email

  Step 2: the 6-digit code the user read from the email, with the verification_id from verify_work_email (or the verification_id alone once they clicked the link), becomes a buyer_token for verified Ruzora actions, valid 7 days, and opens their Sol account. Sends the email and code to Ruzora.

  Parameters:

  • work_email (required) — string — The same work email given to verify_work_email
  • code — string — The 6-digit code from the email, exactly as the user typed it
  • verification_id — string — From verify_work_email: always pass it, with the code, or alone once the user clicked "Yes, this is me" in the email

  Hints: read-only no · destructive no · idempotent no · open-world yes

• save_role

  Save the role being hired for in the user's Sol workspace (Ruzora's hiring agent), where shortlists and documents for it collect. Needs a buyer_token from confirm_work_email. Sends the role details to Ruzora.

  Parameters:

  • work_email (required) — string — The verified work email
  • title (required) — string — Role title, e.g. "Senior backend engineer"
  • notes — string — What the person will own; the scorecard summary
  • stack — array — Main technologies
  • seniority — string — junior, mid, senior or staff
  • buyer_token — string — Proof the user verified this work email: the buyer_token from confirm_work_email (valid 7 days). No token yet? Call verify_work_email first.

  Hints: read-only no · destructive no · idempotent no · open-world yes

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.