Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Ruzora is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
35
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Pre-vetted senior LATAM engineers for US startups: hiring leads, open roles, applications.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ruzora-mcp https://mcp.ruzora.com/mcp
# 2 — ask your agent for something these tools do
# list_open_roles, get_job_details, get_company_info and 32 more
Ruzora costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RUAll 1 server
ruzora1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ruzora-mcp https://mcp.ruzora.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
35 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get all currently open engineering roles at Ruzora. Returns titles, tech stacks, experience levels, and application URLs.
No parameter schema on file.
Get detailed information about a specific job role including responsibilities, requirements, and tech stack.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Job slug (e.g., "devops-engineer", "ai-engineer") |
Get comprehensive information about Ruzora's services, process, value proposition, and differentiators.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first_name | string | yes | First name |
| last_name | string | yes | Last name |
| string | yes | Email address | |
| phone | string | no | Phone number |
| linkedin_url | string | no | LinkedIn profile URL |
| role_category | string | yes | Primary role category |
| message | string | no | Brief intro or relevant experience |
Request a custom software project from Ruzora's Software Factory. Fixed-price development by senior LATAM engineers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Contact person name |
| string | yes | Business email | |
| company | string | yes | Company name |
| description | string | yes | What you want built |
| budget | string | no | Budget range (USD) |
| timeline | string | no | Desired timeline |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role_title | string | yes | Working title, e.g. "Senior backend engineer" |
| company_context | string | no | Company stage, product, team today, why this hire now |
| what_success_looks_like | string | no | What this person must have achieved in 6-12 months, in your words |
| stack | string | no | Main technologies |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | Role and level |
| numbers | string | no | Salary or quotes you have per option, location, start-by date, how long you need the person |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | yes | "role" = what level do I need; "candidate" = what level is this person |
| role_description | string | no | The work: what they will own, who reviews them, how vague the goals are (or paste a role scorecard) |
| candidate_evidence | string | no | CV text, interview notes, an interview scorecard or an assessment report (remove contact details, IDs and dates of birth) |
| company_size | string | no | Your company size and stage, e.g. "8 people, seed" |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role_title | string | yes | Role title |
| details | string | no | Scorecard or notes: what they will own, stack, team, pay range, remote rules, hiring locations, benefits |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_text | string | yes | The full job post text |
| locations | array | no | Where the role can be filled (for pay-range rules) |
| employee_count | number | no | Total employees |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locations | array | yes | Where the role can be filled, e.g. ["California", "New York City"] or ["remote US"] |
| employee_count | number | no | Total employees (thresholds differ by state) |
| remote | boolean | no | True if the role is remote |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| must_haves | string | no | The role's must-haves (or paste a role scorecard) |
| resumes | string | no | Pasted CV text, one after another. Remove contact details, IDs and dates of birth. |
| blind_mode | boolean | no | Strip names, photos, schools and dates before scoring |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| resume_text | string | yes | The resume text as extracted from the file |
| hidden_segments | array | no | Optional: text your PDF tool marked as white, tiny or hidden |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code_or_repo | string | no | Paste the code, file excerpts, README and commit history (or describe the repo) |
| role | string | no | Role and level you are hiring for |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| situation | string | no | Where you are in the process and what made you suspicious, if anything. Do not paste ID documents. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | Role and level |
| details | string | no | Must-haves (or a role scorecard), who can interview, any questions you already use |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | Role, level and stack |
| details | string | no | What the person will own, and any questions you planned to ask |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | Role and level |
| stack | string | yes | Language and framework the task should use |
| details | string | no | Time you can ask of candidates, your AI policy, what the job really involves |
Turn raw interview notes into an anchored scorecard per interviewer and a debrief memo with evidence, disagreements and bias flags. You make the decision.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| must_haves | string | no | The role's must-haves or scorecard |
| notes | string | no | Each interviewer's raw notes, labeled by interviewer and stage |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requester_name | string | yes | Full name of the person hiring |
| work_email | string | yes | Their WORK email (personal inboxes are refused). The report and status go here. |
| company | string | yes | Hiring company name |
| role | string | yes | Role being hired, e.g. "Senior backend engineer" |
| stack | string | no | Main stack, e.g. "Python, Django, Postgres" |
| candidate_name | string | yes | Candidate's name |
| candidate_github_url | string | no | Optional GitHub profile URL |
| candidate_linkedin_url | string | no | Optional LinkedIn profile URL |
| candidate_informed | boolean | yes | True only when the user has confirmed the candidate knows they will receive a technical assessment from Ruzora on the company's behalf. |
| buyer_token | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status_url | string | yes | The status page URL (or its token) returned when the challenge was sent |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| candidate_summary | string | no | Role, the candidate's CV highlights, and the open risks from interviews |
| referees | string | no | Who the candidate offered as references (names, companies, relationship) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | Role and level |
| details | string | no | Start date, team, systems they will touch, the role scorecard outcomes, employee or contractor |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| badge | string | yes | Badge ID (a UUID) or the badge/verification 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stack | array | yes | Technologies, e.g. ["React", "Node", "AWS"] |
| level | string | no | Optional seniority filter |
| min_overlap_hours | number | no | Optional minimum overlap with US working hours |
| page | number | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stack | array | no | Optional: technologies to look for, e.g. ["Go", "AWS"] |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| full_name | string | yes | Hiring manager full name |
| work_email | string | yes | Work email (personal inboxes are refused). The shortlist goes here. |
| company | string | yes | Company name |
| role | string | yes | Role title, e.g. "Senior backend engineer" |
| seniority | string | yes | Seniority: mid (3-5 years), senior (5-8 years) or staff (8+ years, lead) |
| required_skills | array | no | Must-have skills only (hard filter), e.g. ["Python", "Postgres"] |
| preferred_skills | array | no | Nice-to-have skills (ranking only) |
| engineers | number | no | How many engineers (default 1) |
| timeline | string | no | When they should start, e.g. "within a month" |
| notes | string | no | Context: what they will own, time-zone needs, the role scorecard summary |
| buyer_token | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| full_name | string | yes | Full name |
| work_email | string | yes | Work email |
| company | string | no | Company name |
| your_title | string | yes | The asker's own position: founder_ceo, cto_vp_eng, eng_manager, hr_ops_finance or other |
| role_count | string | yes | How many engineers |
| runway | string | yes | Company runway: under 6 months, 6-12, 12-18, 18+, or bootstrapped without revenue |
| seat_budget | string | yes | Monthly budget per engineer: under $4,500, $4,500-5,999, $6,000-7,999, $8,000+, or not sure |
| timing | string | yes | When you need them: asap, within_month, one_to_three_months, three_plus or no_timeline |
| buyer_token | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which term: all, pricing, commitment, refunds, guarantee, factory_warranty, delivery or process |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idea | string | no | Optional: the idea in the user's words, to start the interview from |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Where to send the PDF (personal email is fine) | |
| first_name | string | no | First name for the report |
| idea_read_markdown | string | yes | The full Idea Read text the interview produced |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| full_name | string | yes | Full name |
| work_email | string | yes | |
| company | string | no | Company or business name |
| kind | string | yes | "build" = new app or software; "rescue" = fix or take over a failing app or agency project |
| budget | string | yes | Budget: under $15K, $15-50K, $50-150K, over $150K, or not sure |
| timing | string | yes | When to start |
| your_title | string | yes | The asker's own position: founder_ceo, cto_vp_eng, eng_manager, hr_ops_finance or other |
| project_summary | string | no | One paragraph: what to build or what is broken (shown back to help you prepare the call) |
| buyer_token | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| work_email | string | yes | The user's WORK email (personal inboxes are refused) |
| for_tool | string | no | Which action this verification is for (the email names it, so the user knows what they confirm) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| work_email | string | yes | The same work email given to verify_work_email |
| code | string | no | The 6-digit code from the email, exactly as the user typed it |
| verification_id | string | no | From verify_work_email: always pass it, with the code, or alone once the user clicked "Yes, this is me" in the email |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| work_email | string | yes | The verified work email |
| title | string | yes | Role title, e.g. "Senior backend engineer" |
| seniority | string | no | junior, mid, senior or staff |
| stack | array | no | Main technologies |
| notes | string | no | What the person will own; the scorecard summary |
| buyer_token | string | no | 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ruzora or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ruzora can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.