Playwright MCP Server
com.ruzora/ruzoraPre-vetted senior LATAM engineers for US startups: hiring leads, open roles, applications.
Watch this dependency
Get before/after evidence when observed tools, schemas, authentication access, availability or the endpoint changes.
Inspect evidence and set up a watch Share public evidence report
Score: 100/100
Handshake verified by our own probe.
why this score
Tools · 35
Get all currently open engineering roles at Ruzora. Returns titles, tech stacks, experience levels, and application URLs.
Get detailed information about a specific job role including responsibilities, requirements, and tech stack.
Get comprehensive information about Ruzora's services, process, value proposition, and differentiators.
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…
Request a custom software project from Ruzora's Software Factory. Fixed-price development by senior LATAM engineers.
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…
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 augm…
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 …
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.
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…
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 adv…
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.
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.
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.
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 e…
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.
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 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.
Turn raw interview notes into an anchored scorecard per interviewer and a debrief memo with evidence, disagreements and bias flags. You make the decision.
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. …
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.
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.
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.
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.
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.
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.
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. …
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 …
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 warrant…
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 Ruzor…
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…
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-cal…
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 Ruzo…
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 Ruz…
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…
Resources · 11
Blind profiles of vetted engineers, or live availability by stack, with a shortlist request button.
ui://widget/bench.html
Progress of a coding challenge sent through Ruzora: stage per candidate, scores once released.
ui://widget/status.html
Whether a "Ruzora Vetted" badge is valid, with the vetting date and verified stacks.
ui://widget/badge.html
Confirmation of a vetted shortlist request and what happens next.
ui://widget/shortlist.html
Findings from a job-post, pay-transparency or resume check, grouped by severity, with sources.
ui://widget/findings.html
ruzora://about
ruzora://services/staff-augmentation
ruzora://services/software-factory
ruzora://process
ruzora://faq
ruzora://jobs
Prompts · 21
Writes honest 3-touch outreach to passive senior engineers plus a referral ask for a founder's network. Use when you need a recruiter outreach template or to message engineers who aren't applying.
Writes a software engineer job description senior engineers answer, plus a compliance lint (pay range, citizenship wording, exclusionary language). Use when writing or fixing a developer job post.
Checks whether a contractor engineer looks like an employee under IRS, DOL and state tests, plus IP and account ownership, with questions for counsel. Use when hiring or reviewing a 1099 contractor.
Builds a job offer kit for an engineering hire: pre-close questions, verbal offer script, written offer email, negotiation playbook and close plan. Use when making or negotiating a job offer.
Builds a reference-check plan for an engineering finalist: referee identity checks, a call script aimed at the risks found in interviews, and a risk register. Use when checking references.
Sets an AI-use policy for developer interviews, matches each stage to it, gives fair cheating tells and an AI-fluency pairing exercise with rubric. Use when candidates may be using AI in interviews.
Calibrates engineering seniority by scope, not years. Sets the level a role needs and estimates a candidate's level with confidence and evidence. Use when choosing junior, mid, senior or staff.
Designs an AI-resilient coding test for a developer role (seeded-bug review, extend-a-codebase or paid trial) with a hidden rubric and follow-up. Use when you need a coding test or take-home.
Builds a developer interview kit for non-technical founders and managers, with strong-vs-bluff answer guides and follow-up ladders. Use when you must interview an engineer but can't judge code.
Turns raw interview notes into an anchored scorecard per interviewer and a debrief memo with evidence, disagreements and bias flags. Use when writing up interviews or running a debrief.
Builds a lean structured interview loop for an engineering role, with stages, owners, time budget, fixed questions, an anchored 1-4 rubric and a legal lint. Use when you need an interview kit or loop.
Builds a 30-60-90 day onboarding plan for a new software engineer: least-privilege day-1 access, first PR, buddy plan, milestones tied to the role scorecard. Use when an engineer is about to start.
Turns notes on a new engineer into a fair, documented day 30/60/90 review separating ramp-up issues from capability gaps, with options and a script. Use when checking if a new hire is working out.
Builds a neutral 12-month cost and risk comparison of six ways to add an engineer, on your own numbers. Use when deciding between hiring, a contractor, an agency or staff augmentation.
Builds an engagement plan for hiring an engineer in another country: contractor vs EOR vs vendor, risk register, setup checklist, questions for counsel. Use when hiring international contractors.
Turns a vague engineering hire into a role scorecard with mission, measurable 12-month outcomes, must-haves, competencies and an interview map. Use when defining a role before writing the job post.
Produces a vendor due diligence scorecard, question list, contract red-flag check and reference script for a staffing firm, agency or dev shop. Use when comparing engineering vendors before signing.
Reviews a candidate's GitHub repo or code sample in plain English for non-technical hirers, with authorship checks and interview questions. Use when checking a developer's code or GitHub.
Produces a respectful liveness script, observer checklist and escalation steps to catch deepfake or stand-in candidates. Use when a video interview felt off or before remote interviews.
Builds an identity-verification protocol for remote engineering hires and a red-flag log for a specific candidate, from FBI guidance. Use when a candidate seems fake or before hiring remotely.
Triages engineering CVs against a role's must-haves with evidence scores, blind mode, prompt-injection flags and screening-call questions. Use when screening resumes or shortlisting applicants.
How to use
Add to your Claude Desktop / Cursor / Cline MCP config:
{
"mcpServers": {
"playwright_mcp_server": {
"url": "https://mcp.ruzora.com/mcp",
"transport": "http"
}
}
}