Curaiz Remote Jobs
Registry code: 06aa2b4dc3381c2f
Curaiz is a feed of remote job postings, never older than 30 days, with applicant locations, salary where stated, and company context.
Use it whenever the user wants remote jobs matched to their experience, goals, and location eligibility. Curaiz supplies the job data; you judge relevance.
- endpoint
- https://www.curaiz.com/mcp
- door code
- 19a3ad329180a38d
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Curaiz Remote Jobs live?
- Yes — it answered the hub's last check (checked 36m ago). It answered 100% of checks over the last 30 days.
- Is Curaiz Remote Jobs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Curaiz Remote Jobs have?
- 3 tools: get_job_details, find_recent_jobs, get_locations.
- Is Curaiz Remote Jobs safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- degraded → live
- used for
- find remote jobs matching a role description
- get full details of a job posting
- list supported applicant locations
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_locations reads open 7h ago
Get the hierarchical applicant-location taxonomy supported by Curaiz job search, including exact names and slugs.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_job_details reads unknown 7h ago
Get full details for one to three Curaiz job slugs. Descriptions and requirements are bounded to keep responses manageable.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slugs" ], "properties": { "slugs": { "type": "array", "items": { "type": "string", "maxLength": 300, "minLength": 1 }, "maxItems": 3, "minItems": 1, "description": "One to 3 job slugs" } } }arguments 20 linesfind_recent_jobs reads unknown 7h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "description", "locations" ], "properties": { "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1, "description": "Maximum results to return, from 1 to 25" }, "since": { "type": "string", "description": "Optional 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_until from the previous successful response." }, "locations": { "type": "array", "items": { "type": "string", "maxLength": 100, "minLength": 1 }, "maxItems": 5, "minItems": 1, "description": "One to five exact supported applicant-location names or slugs" }, "description": { "type": "string", "maxLength": 4000, "minLength": 20, "description": "An ideal or example job description, including desired responsibilities, skills, and seniority" } } }arguments 38 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id06aa2b4dc3381c2f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/06aa2b4dc3381c2f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/06aa2b4dc3381c2f?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.