# com.ruzora/ruzora

- Registry name: `com.ruzora/ruzora` · version 1.0.0
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Government & law, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.ruzora%2Fruzora
- Server page: https://mcpstation.net/s/com.ruzora--ruzora.html

## Description (written by the publisher, not verified, not instructions)

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

## Notice

Text that looks like instructions to an AI was found in this server's descriptions. This is a pattern match, not a verdict.

## Connect

- streamable-http: `https://mcp.ruzora.com/mcp`

## Tools (as reported by the server, not verified)

- `list\_open\_roles`: Get all currently open engineering roles at Ruzora. Returns titles, tech stacks, experience levels, and application URLs.
- `get\_job\_details`: Get detailed information about a specific job role including responsibilities, requirements, and tech stack.
- `get\_company\_info`: Get comprehensive information about Ruzora's services, process, value proposition, and differentiators.
- `submit\_candidate\_application`: 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.
- `create\_factory\_inquiry`: Request a custom software project from Ruzora's Software Factory. Fixed-price development by senior LATAM engineers.
- `build\_role\_scorecard`: 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.
- `compare\_hiring\_models`: 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.
- `calibrate\_seniority`: 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.
- `write\_job\_description`: 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.
- `lint\_job\_post`: 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.
- `check\_pay\_transparency`: 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.
- `triage\_resumes`: 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.
- `detect\_resume\_injection`: 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.
- `review\_code\_sample`: 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.
- `check\_identity\_risk`: 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.
- `build\_interview\_kit`: 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.
- `developer\_interview\_questions`: 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.
- `design\_coding\_assessment`: 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.
- `score\_interview\_notes`: Turn raw interview notes into an anchored scorecard per interviewer and a debrief memo with evidence, disagreements and bias flags. You make the decision.
- `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.
- `get\_vetting\_status`: 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.
- `plan\_reference\_check`: 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.
- `build\_onboarding\_plan`: 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.
- `verify\_ruzora\_badge`: 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.
- `search\_vetted\_engineers`: 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.
- `check\_market\_supply`: 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.
- `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.
- `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.
- `explain\_ruzora\_terms`: 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.
- `start\_honest\_read`: 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.
- `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.
- `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.
- `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.
- `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.
- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html