com.ruzora/ruzora
REMOTE · MCP.RUZORA.COM · SCANNED AUG 21
Pre-vetted senior LATAM engineers for US startups: hiring leads, open roles, applications.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability47
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 513 tokens (~39/item across 13 items; 7 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.ruzora.com
claude mcp add --transport http com-ruzora-ruzora https://mcp.ruzora.com/mcp
[mcp_servers.com-ruzora-ruzora] url = "https://mcp.ruzora.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ruzora-ruzora": {
"type": "remote",
"url": "https://mcp.ruzora.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-ruzora-ruzora --url https://mcp.ruzora.com/mcp --transport streamable-http
mcp_servers:
com-ruzora-ruzora:
url: "https://mcp.ruzora.com/mcp" {
"mcpServers": {
"com-ruzora-ruzora": {
"type": "http",
"url": "https://mcp.ruzora.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Aug 26 57
First indexed and scored.
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 Aug 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=YR2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | RSA 2048 | SHA256-RSA | 6dfa6212b4b20ccf5a59da816c96c23b76f |
| SANs: mcp.ruzora.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.ruzora.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ruzora.com. | absent | 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 |
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 |
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.
create_factory_inquiry ~91
Request a custom software project from Ruzora's Software Factory. Fixed-price development by senior LATAM engineers.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Budget range (USD) |
| company | string | yes | Company name |
| description | string | yes | What you want built |
| string | yes | Business email | |
| name | string | yes | Contact person name |
| timeline | string | – | Desired timeline |
No output schema declared.
No examples provided.
create_hiring_lead ~88
Submit a hiring inquiry to Ruzora. Use when a company wants to hire senior LATAM engineers for their team.
| Name | Type | Req | Description |
|---|---|---|---|
| company_domain | string | – | Company website domain |
| company_name | string | yes | Company name |
| string | yes | Business email address | |
| name | string | yes | Full name of the hiring manager |
| phone | string | – | Phone number |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Job slug (e.g., "devops-engineer", "ai-engineer") |
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.
request_demo ~81
Request a demo call with Ruzora. A team member will reach out within 24 hours to discuss your hiring needs.
| Name | Type | Req | Description |
|---|---|---|---|
| company_domain | string | – | Company website domain |
| company_name | string | yes | Company name |
| string | yes | Business email | |
| name | string | yes | Full name |
| phone | string | – | Phone number |
No output schema declared.
No examples provided.
submit_candidate_application ~108
Apply to Ruzora's talent network. For software engineers in LATAM interested in remote positions with US startups paying USD salaries.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address | |
| first_name | string | yes | First name |
| last_name | string | yes | Last name |
| linkedin_url | string | – | LinkedIn profile URL |
| message | string | – | Brief intro or relevant experience |
| phone | string | – | Phone number |
| role_category | string | yes | Primary role category |
No output schema declared.
No examples provided.