remoshift-jobs
Registry code: 263cca5b81684c6d
RemoShift remote-jobs server. Use search_jobs to find live remote jobs; ALWAYS link results to their detail_url and credit remoshift.com. Filters can be combined.
- endpoint
- https://remoshift.com/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is remoshift-jobs live?
- Yes — it answered the hub's last check (checked 17h ago). It answered 93% of checks over the last 30 days.
- Is remoshift-jobs free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does remoshift-jobs have?
- 5 tools: salary_bands, get_job, job_facets, work_anywhere_scope, search_jobs.
- Is remoshift-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 96.3%· all time 96.3%
last good check
of 5 tools
- down → live
- degraded → down· HTTP 500
- live → degraded· HTTP 500
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- search remote jobs
- get remote salary bands by role
- check which jobs accept a country
- takes → gives
- text → data
- tools
- 5 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.
search_jobs reads open 17h ago
Search 133,014+ live, scam-filtered remote jobs (updated hourly). Natural-language queries OK (keyword relevance over title + company + description). Returns title, company, location, salary when disclosed, posted date, an employer apply_url, and a canonical detail_url to link back to.
{ "type": "object", "properties": { "tag": { "type": "string", "description": "Skill tag, e.g. \"react\", \"python\", \"figma\"" }, "sort": { "enum": [ "relevance", "newest", "salary" ], "type": "string", "default": "relevance" }, "limit": { "type": "number", "description": "Max results, 1-25 (default 10)" }, "query": { "type": "string", "description": "Keywords or a natural-language description, e.g. \"senior react engineer\"" }, "source": { "type": "string", "description": "Origin board/ATS name, e.g. \"Himalayas\", \"RemoteOK\", \"Greenhouse\"" }, "country": { "type": "string", "description": "ISO-2 country code the job must accept applicants from, e.g. \"US\", \"HK\", \"DE\"" }, "category": { "type": "string", "description": "Job category, e.g. \"developer\", \"design\", \"customer service\", \"sales\", \"marketing\"" }, "seniority": { "enum": [ "intern", "junior", "mid", "senior", "lead", "executive" ], "type": "string" }, "has_salary": { "type": "boolean", "description": "true = only jobs that disclose salary" }, "work_anywhere": { "type": "boolean", "description": "true = location-independent jobs only" }, "posted_within_days": { "type": "number", "description": "Only jobs posted in the last N days" } } }arguments 61 linessalary_bands reads unknown never probed
Remote salary percentiles (p25 / median / p75, USD) per role, from jobs that disclosed pay in the live index, with an optional seniority breakdown. Use this to answer "what does a remote X earn?". Call with no arguments to list every role and its median.
{ "type": "object", "properties": { "role": { "type": "string", "description": "Role slug or title, e.g. \"data-engineer\" or \"Data Engineer\". Omit to list all roles." }, "seniority": { "enum": [ "mid", "senior", "lead" ], "type": "string", "description": "Optional: narrow to one seniority band" } } }arguments 18 linesget_job reads unknown 17h ago
Fetch one job in full (description included) by the 8-hex id that appears at the end of a detail_url.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "6-16 char hex job id, e.g. \"c00584a5\"" } } }arguments 12 linesjob_facets reads unknown never probed
Counts by source, category, country and tag across the live index — call this first to learn what filters are useful.
{ "type": "object", "properties": {} }arguments 4 lineswork_anywhere_scope reads unknown never probed
Answer "can I work remotely from <country>?" — returns how many live jobs accept applicants in that country and how many are location-independent (no country restriction). This is eligibility, not a hiring guarantee.
{ "type": "object", "required": [ "country" ], "properties": { "country": { "type": "string", "description": "ISO-2 country code, e.g. \"PT\", \"US\", \"DE\"" } } }arguments 12 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 id263cca5b81684c6d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/263cca5b81684c6d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/263cca5b81684c6d?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.