Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.ruzora/ruzora

REMOTE · MCP.RUZORA.COM

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

Available components

0 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Recent critical change

Authorization (7 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • 81% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4277 tokens (~92/item across 46 items; 35 tools + 11 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety92
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_pay_transparency" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 12 Nov 26 +4
    • Stability: fail → pass ▲ security
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: fail → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 81 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 13 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “create_hiring_lead” was removed ▼ security
    • Tool “request_demo” was removed ▼ security
    • Schema quality: 41 → 92 ▼ functional
    • Schema quality: 0% → 81% ▲ functional
    • The server now declares the “prompts” capability functional
    • First check of Capabilities: pass functional
    • Destructive annotations: pass → 67 functional
    • New prompt “ai-use-interview-check” functional
    • New prompt “calibrate-seniority” functional
    • New prompt “code-sample-review” functional
    • New prompt “coding-assessment-designer” functional
    • New prompt “contractor-classification-check” functional
    • New prompt “deepfake-interview-check” functional
    • New prompt “developer-interview-questions” functional
    • New prompt “engineer-hiring-cost-compare” functional
    • New prompt “engineer-onboarding-plan” functional
    • New prompt “engineer-outreach-messages” functional
    • New prompt “engineering-job-description” functional
    • New prompt “fake-candidate-check” functional
    • New prompt “international-engineer-hiring” functional
    • New prompt “interview-scorecard” functional
    • New prompt “job-offer-kit” functional
    • New prompt “new-hire-90-day-review” functional
    • New prompt “reference-check” functional
    • New prompt “resume-triage” functional
    • New prompt “role-scorecard” functional
    • New prompt “staffing-vendor-due-diligence” functional
    • New prompt “structured-interview-kit” functional
    • New resource “ruzora-badge-card” functional
    • New resource “ruzora-bench-card” functional
    • New resource “ruzora-findings-card” functional
    • New resource “ruzora-shortlist-card” functional
    • New resource “ruzora-status-card” functional
    • New tool “build_interview_kit” functional
    • New tool “build_onboarding_plan” functional
    • New tool “build_role_scorecard” functional
    • New tool “calibrate_seniority” functional
    • New tool “check_hiring_fit” functional
    • New tool “check_identity_risk” functional
    • New tool “check_market_supply” functional
    • New tool “check_pay_transparency” functional
    • New tool “compare_hiring_models” functional
    • New tool “confirm_work_email” functional
    • New tool “design_coding_assessment” functional
    • New tool “detect_resume_injection” functional
    • New tool “developer_interview_questions” functional
    • New tool “explain_ruzora_terms” functional
    • New tool “get_vetting_status” functional
    • New tool “lint_job_post” functional
    • New tool “plan_reference_check” functional
    • New tool “request_project_scoping_call” functional
    • New tool “request_vetted_shortlist” functional
    • New tool “review_code_sample” functional
    • New tool “save_role” functional
    • New tool “score_interview_notes” functional
    • New tool “search_vetted_engineers” functional
    • New tool “send_coding_challenge” functional
    • New tool “start_honest_read” functional
    • New tool “submit_honest_read” functional
    • New tool “triage_resumes” functional
    • New tool “verify_ruzora_badge” functional
    • New tool “verify_work_email” functional
    • New tool “write_job_description” functional
  • 7 Oct 26 0
    • Authorization: unverified → fail ▼ critical
    • HSTS header: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 0 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Score status: failed → scored ▲ functional
  • 4 Oct 26 0
    • TLS certificate: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 0 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.ruzora.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ruzora.com CN=YE1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA384 6acc2c53a190b693da320bc98e10eb03186
SANs: mcp.ruzora.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ruzora.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
ruzora.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ruzora.com/mcp Verified 200
http (plaintext) http://mcp.ruzora.com/mcp HTTPS enforced 301 https://mcp.ruzora.com/mcp
MCP tools · 35 exposed · ~4,113 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_interview_kit ~82

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.

NameTypeReqDescription
detailsstring–Must-haves (or a role scorecard), who can interview, any questions you already use
rolestringyesRole and level

No output schema declared.

No examples provided.

build_onboarding_plan ~89

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.

NameTypeReqDescription
detailsstring–Start date, team, systems they will touch, the role scorecard outcomes, employee or contractor
rolestringyesRole and level

No output schema declared.

No examples provided.

build_role_scorecard ~130

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.

NameTypeReqDescription
company_contextstring–Company stage, product, team today, why this hire now
role_titlestringyesWorking title, e.g. "Senior backend engineer"
stackstring–Main technologies
what_success_looks_likestring–What this person must have achieved in 6-12 months, in your words

No output schema declared.

No examples provided.

calibrate_seniority ~170

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.

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

No output schema declared.

No examples provided.

check_hiring_fit ~297

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.

NameTypeReqDescription
buyer_tokenstring–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.
companystring–Company name
full_namestringyesFull name
role_countstringyesHow many engineers
runwaystringyesCompany runway: under 6 months, 6-12, 12-18, 18+, or bootstrapped without revenue
seat_budgetstringyesMonthly budget per engineer: under $4,500, $4,500-5,999, $6,000-7,999, $8,000+, or not sure
timingstringyesWhen you need them: asap, within_month, one_to_three_months, three_plus or no_timeline
work_emailstringyesWork email
your_titlestringyesThe asker's own position: founder_ceo, cto_vp_eng, eng_manager, hr_ops_finance or other

No output schema declared.

No examples provided.

check_identity_risk ~85

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.

NameTypeReqDescription
situationstring–Where you are in the process and what made you suspicious, if anything. Do not paste ID documents.

No output schema declared.

No examples provided.

check_market_supply ~65

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.

NameTypeReqDescription
stackarray–Optional: technologies to look for, e.g. ["Go", "AWS"]

No output schema declared.

No examples provided.

check_pay_transparency ~114

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.

NameTypeReqDescription
employee_countnumber–Total employees (thresholds differ by state)
locationsarrayyesWhere the role can be filled, e.g. ["California", "New York City"] or ["remote US"]
remoteboolean–True if the role is remote

No output schema declared.

No examples provided.

compare_hiring_models ~97

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.

NameTypeReqDescription
numbersstring–Salary or quotes you have per option, location, start-by date, how long you need the person
rolestringyesRole and level

No output schema declared.

No examples provided.

confirm_work_email ~153

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.

NameTypeReqDescription
codestring–The 6-digit code from the email, exactly as the user typed it
verification_idstring–From verify_work_email: always pass it, with the code, or alone once the user clicked "Yes, this is me" in the email
work_emailstringyesThe same work email given to verify_work_email

No output schema declared.

No examples provided.

create_factory_inquiry ~91

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

NameTypeReqDescription
budgetstring–Budget range (USD)
companystringyesCompany name
descriptionstringyesWhat you want built
emailstringyesBusiness email
namestringyesContact person name
timelinestring–Desired timeline

No output schema declared.

No examples provided.

design_coding_assessment ~97

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.

NameTypeReqDescription
detailsstring–Time you can ask of candidates, your AI policy, what the job really involves
rolestringyesRole and level
stackstringyesLanguage and framework the task should use

No output schema declared.

No examples provided.

detect_resume_injection ~83

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.

NameTypeReqDescription
hidden_segmentsarray–Optional: text your PDF tool marked as white, tiny or hidden
resume_textstringyesThe resume text as extracted from the file

No output schema declared.

No examples provided.

developer_interview_questions ~78

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.

NameTypeReqDescription
detailsstring–What the person will own, and any questions you planned to ask
rolestringyesRole, level and stack

No output schema declared.

No examples provided.

explain_ruzora_terms ~89

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

NameTypeReqDescription
topicstring–Which term: all, pricing, commitment, refunds, guarantee, factory_warranty, delivery or process

No output schema declared.

No examples provided.

get_company_info ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_job_details ~49

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

NameTypeReqDescription
slugstringyesJob slug (e.g., "devops-engineer", "ai-engineer")

No output schema declared.

No examples provided.

get_vetting_status ~71

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.

NameTypeReqDescription
status_urlstringyesThe status page URL (or its token) returned when the challenge was sent

No output schema declared.

No examples provided.

lint_job_post ~97

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.

NameTypeReqDescription
employee_countnumber–Total employees
locationsarray–Where the role can be filled (for pay-range rules)
post_textstringyesThe full job post text

No output schema declared.

No examples provided.

list_open_roles ~33

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_reference_check ~86

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.

NameTypeReqDescription
candidate_summarystring–Role, the candidate's CV highlights, and the open risks from interviews
refereesstring–Who the candidate offered as references (names, companies, relationship)

No output schema declared.

No examples provided.

request_project_scoping_call ~278

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.

NameTypeReqDescription
budgetstringyesBudget: under $15K, $15-50K, $50-150K, over $150K, or not sure
buyer_tokenstring–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.
companystring–Company or business name
full_namestringyesFull name
kindstringyes"build" = new app or software; "rescue" = fix or take over a failing app or agency project
project_summarystring–One paragraph: what to build or what is broken (shown back to help you prepare the call)
timingstringyesWhen to start
work_emailstringyesEmail
your_titlestringyesThe asker's own position: founder_ceo, cto_vp_eng, eng_manager, hr_ops_finance or other

No output schema declared.

No examples provided.

request_vetted_shortlist ~300

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.

NameTypeReqDescription
buyer_tokenstring–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.
companystringyesCompany name
engineersnumber–How many engineers (default 1)
full_namestringyesHiring manager full name
notesstring–Context: what they will own, time-zone needs, the role scorecard summary
preferred_skillsarray–Nice-to-have skills (ranking only)
required_skillsarray–Must-have skills only (hard filter), e.g. ["Python", "Postgres"]
rolestringyesRole title, e.g. "Senior backend engineer"
senioritystringyesSeniority: mid (3-5 years), senior (5-8 years) or staff (8+ years, lead)
timelinestring–When they should start, e.g. "within a month"
work_emailstringyesWork email (personal inboxes are refused). The shortlist goes here.

No output schema declared.

No examples provided.

review_code_sample ~88

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.

NameTypeReqDescription
code_or_repostring–Paste the code, file excerpts, README and commit history (or describe the repo)
rolestring–Role and level you are hiring for

No output schema declared.

No examples provided.

save_role ~162

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.

NameTypeReqDescription
buyer_tokenstring–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.
notesstring–What the person will own; the scorecard summary
senioritystring–junior, mid, senior or staff
stackarray–Main technologies
titlestringyesRole title, e.g. "Senior backend engineer"
work_emailstringyesThe verified work email

No output schema declared.

No examples provided.

score_interview_notes ~75

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

NameTypeReqDescription
must_havesstring–The role's must-haves or scorecard
notesstring–Each interviewer's raw notes, labeled by interviewer and stage

No output schema declared.

No examples provided.

search_vetted_engineers ~144

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.

NameTypeReqDescription
levelstring–Optional seniority filter
min_overlap_hoursnumber–Optional minimum overlap with US working hours
pagenumber–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.
stackarrayyesTechnologies, e.g. ["React", "Node", "AWS"]

No output schema declared.

No examples provided.

send_coding_challenge ~266

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.

NameTypeReqDescription
buyer_tokenstring–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_urlstring–Optional GitHub profile URL
candidate_informedbooleanyesTrue only when the user has confirmed the candidate knows they will receive a technical assessment from Ruzora on the company's behalf.
candidate_linkedin_urlstring–Optional LinkedIn profile URL
candidate_namestringyesCandidate's name
companystringyesHiring company name
requester_namestringyesFull name of the person hiring
rolestringyesRole being hired, e.g. "Senior backend engineer"
stackstring–Main stack, e.g. "Python, Django, Postgres"
work_emailstringyesTheir WORK email (personal inboxes are refused). The report and status go here.

No output schema declared.

No examples provided.

start_honest_read ~88

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.

NameTypeReqDescription
ideastring–Optional: the idea in the user's words, to start the interview from

No output schema declared.

No examples provided.

submit_candidate_application ~136

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.

NameTypeReqDescription
emailstringyesEmail address
first_namestringyesFirst name
last_namestringyesLast name
linkedin_urlstring–LinkedIn profile URL
messagestring–Brief intro or relevant experience
phonestring–Phone number
role_categorystringyesPrimary role category

No output schema declared.

No examples provided.

submit_honest_read ~129

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.

NameTypeReqDescription
emailstringyesWhere to send the PDF (personal email is fine)
first_namestring–First name for the report
idea_read_markdownstringyesThe full Idea Read text the interview produced

No output schema declared.

No examples provided.

triage_resumes ~109

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.

NameTypeReqDescription
blind_modeboolean–Strip names, photos, schools and dates before scoring
must_havesstring–The role's must-haves (or paste a role scorecard)
resumesstring–Pasted CV text, one after another. Remove contact details, IDs and dates of birth.

No output schema declared.

No examples provided.

verify_ruzora_badge ~69

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.

NameTypeReqDescription
badgestringyesBadge ID (a UUID) or the badge/verification URL

No output schema declared.

No examples provided.

verify_work_email ~104

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.

NameTypeReqDescription
for_toolstring–Which action this verification is for (the email names it, so the user knows what they confirm)
work_emailstringyesThe user's WORK email (personal inboxes are refused)

No output schema declared.

No examples provided.

write_job_description ~81

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.

NameTypeReqDescription
detailsstring–Scorecard or notes: what they will own, stack, team, pay range, remote rules, hiring locations, benefits
role_titlestringyesRole title

No output schema declared.

No examples provided.

Install

How do I install the com.ruzora/ruzora MCP server?

com.ruzora/ruzora is a hosted endpoint at https://mcp.ruzora.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.ruzora.com

# add to Claude Code
claude mcp add --transport http com-ruzora-ruzora 'https://mcp.ruzora.com/mcp'
Common questions

What is the com.ruzora/ruzora MCP server?

com.ruzora/ruzora is an MCP server listed in the public MCP registry as com.ruzora/ruzora. Pre-vetted senior LATAM engineers for US startups: hiring leads, open roles, applications. This page covers its hosted endpoint (https://mcp.ruzora.com/mcp).

Is the com.ruzora/ruzora MCP server safe to use?

com.ruzora/ruzora scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.ruzora/ruzora MCP server expose?

com.ruzora/ruzora exposes 35 tools: list_open_roles, get_job_details, get_company_info, submit_candidate_application, create_factory_inquiry, and 30 more. Their descriptions and schemas cost roughly 4,113 tokens of context every time the server is loaded.

Does the com.ruzora/ruzora MCP server require authentication?

No. We connected to com.ruzora/ruzora without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.ruzora/ruzora MCP server still maintained?

com.ruzora/ruzora is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.ruzora/ruzora MCP server?

VerifyMCP ran 14 checks on com.ruzora/ruzora, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.