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.

Curaiz Remote Jobs

REMOTE · WWW.CURAIZ.COM · SCANNED SEP 21

Find fresh remote jobs matched to a person's experience, goals, and eligible locations.

Available components

+4 this week 87 Trust /100
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 Security80
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 422 tokens (~140/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the Curaiz Remote Jobs MCP server?

Curaiz Remote Jobs is a hosted endpoint at https://www.curaiz.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 · www.curaiz.com

# add to Claude Code
claude mcp add --transport http com-curaiz-remote-jobs 'https://www.curaiz.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-curaiz-remote-jobs": {
      "url": "https://www.curaiz.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-curaiz-remote-jobs": {
      "type": "http",
      "url": "https://www.curaiz.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-curaiz-remote-jobs]
url = "https://www.curaiz.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-curaiz-remote-jobs": {
      "type": "remote",
      "url": "https://www.curaiz.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-curaiz-remote-jobs --url 'https://www.curaiz.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-curaiz-remote-jobs:
    url: "https://www.curaiz.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-curaiz-remote-jobs": {
      "Transport": "http",
      "Url": "https://www.curaiz.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-curaiz-remote-jobs -t streamable-http -u 'https://www.curaiz.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-curaiz-remote-jobs": {
      "type": "http",
      "url": "https://www.curaiz.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

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 Sept 2026 · Probed https://www.curaiz.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.curaiz.com CN=YR2,O=Let's Encrypt,C=US 23 Aug 2026 21 Nov 2026 RSA 2048 SHA256-RSA 6f9f391ae7e1cbccb430ca3b3ce84c080dc
SANs: www.curaiz.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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.curaiz.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
curaiz.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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.curaiz.com/mcp Verified 200
http (plaintext) http://www.curaiz.com/mcp HTTPS enforced 308 https://www.curaiz.com/mcp
MCP tools · 3 exposed · ~247 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
find_recent_jobs ~171

Find remote jobs ordered by semantic similarity to an ideal job description. Omit since to search the full available corpus; for an incremental search, pass searched_until from the previous successful response as since. Results are compact and never include full job descriptions.

NameTypeReqDescription
descriptionstringyesAn ideal or example job description, including desired responsibilities, skills, and seniority
limitintegerMaximum results to return, from 1 to 25
locationsarrayyesOne to five exact supported applicant-location names or slugs
sincestringOptional inclusive discovery-time lower bound as an ISO 8601 timestamp with a timezone, at most 31 days old. Omit it to search the full available corpus. For an incremental search, pass searched_unti…
NameTypeReqDescription
jobsarrayyes
result_countintegeryes
searched_sincestringyesInclusive discovery-time lower bound used for this search
searched_untilstringyesExclusive discovery-time upper bound captured for this search. Pass this value as since to continue with an incremental search.
truncatedbooleanyes

No examples provided.

get_job_details ~48

Get full details for one to three Curaiz job slugs. Descriptions and requirements are bounded to keep responses manageable.

NameTypeReqDescription
slugsarrayyesOne to 3 job slugs
NameTypeReqDescription
jobsarrayyes
not_foundarrayyes

No examples provided.

get_locations ~28

Get the hierarchical applicant-location taxonomy supported by Curaiz job search, including exact names and slugs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
locationsarrayyes

No examples provided.

Common questions

What is the Curaiz Remote Jobs MCP server?

Curaiz Remote Jobs is an MCP server listed in the public MCP registry as com.curaiz/remote-jobs. Find fresh remote jobs matched to a person's experience, goals, and eligible locations. This page covers its hosted endpoint (https://www.curaiz.com/mcp).

Is the Curaiz Remote Jobs MCP server safe to use?

Curaiz Remote Jobs scores 87 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 Curaiz Remote Jobs MCP server expose?

Curaiz Remote Jobs exposes 3 tools: find_recent_jobs, get_job_details, get_locations. Their descriptions and schemas cost roughly 247 tokens of context every time the server is loaded.

Does the Curaiz Remote Jobs MCP server require authentication?

No. We connected to Curaiz Remote Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Curaiz Remote Jobs MCP server still maintained?

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