_ registry / mcp streamable-http · checked 2h ago

oceanofjobs

https://oceanofjobs.com

Registry code: a4ce1b1b302d1f0a

api record

Ocean of Jobs lists open jobs read directly from each employer's own applicant tracking system (Greenhouse, Comeet, Workday and others), not from job boards. It is built for Israeli tech, but most listings are elsewhere, above all the US, so pass country (IL for Israel) when the place matters. Each job carries a lifetime: how long it has been listed and whether it is still open. Lead with it when it matters, for example a role listed for months. first_seen is when Ocean of Jobs first found the listing on the employer's own applicant tracking system. last_seen is the last time a read of that…

endpoint
https://oceanofjobs.com/mcp
protocol
streamable-http ·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 it live, free and safe measured by this hub
Is oceanofjobs live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is oceanofjobs free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does oceanofjobs have?
9 tools: search_jobs, get_job, get_company, save_job, queue_for_auto_apply, remove_from_auto_apply_queue, remove_saved_job, list_auto_apply_queue, ….
Is oceanofjobs 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
208ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
8 auth-required 1 never probed 8 of 9 classified

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_job auth-required never probed

    One job on Ocean of Jobs by its id (from search_jobs or get_company): the description as plain text, its lifetime, whether its data is verified against the employer's ATS, and both links, the Ocean of Jobs page first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The job's id, e.g. 67ff4ef965d91ef7."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_company auth-required never probed

    A company on Ocean of Jobs by name or domain: how many jobs it has open, how many are new this week, how long it has been tracked, its newest jobs, and its Ocean of Jobs page.

    mcp-tool

    {
  "type": "object",
  "required": [
    "company"
  ],
  "properties": {
    "company": {
      "type": "string",
      "description": "A name such as Wix, or a domain such as wix.com."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • save_job auth-required never probed

    Save a job to the user's Ocean of Jobs account, where it shows under Saved jobs on every device. Needs the user's personal access token. Saving the same job twice is harmless.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The job's id, e.g. 67ff4ef965d91ef7."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • queue_for_auto_apply auth-required never probed

    Queue a job for the Ocean of Jobs Chrome extension to apply to with the user's profile and CV. The extension applies to queued jobs on its next check, every 15 minutes, so the user needs the extension installed and connected. The user must also turn on "Jobs queued by my AI assistant through MCP" in their auto apply settings. For now the extension fills Greenhouse Ashby and Workable forms only (an apply_url on boards.greenhouse.io, job-boards.greenhouse.io, jobs.ashbyhq.com or apply.workable.com); a job on any other site is refused, so pick those jobs. This sends a real application, so queue a job only when the user asks for it. Needs the user's personal access token. Queueing the same job twice is harmless.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The job's id, e.g. 67ff4ef965d91ef7."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • remove_from_auto_apply_queue auth-required never probed

    Take a job out of the user's auto apply queue before the extension applies to it. Needs the user's personal access token.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The job's id."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • remove_saved_job auth-required never probed

    Take a job off the user's saved list. Needs the user's personal access token.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The job's id."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • list_auto_apply_queue auth-required 2h ago

    The jobs waiting in the user's auto apply queue, oldest first, with the same fields as search results and when each was queued. A job leaves the queue once the extension has tried it. Needs the user's personal access token.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "How many, 1 to 25. Default 10."
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • list_saved_jobs auth-required 2h ago

    The jobs saved on the user's Ocean of Jobs account, newest saved first, with the same fields as search results and when each was saved. Needs the user's personal access token.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "How many, 1 to 25. Default 10."
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • search_jobs unknown 2h ago

    Search open jobs on Ocean of Jobs. Give at least one of query, company, city or country (IL for Israel; most listings are in the US). Returns up to 25 jobs per call, best match first when there is a query, newest first otherwise, with the total number of matches. Every job includes its lifetime (days listed, first and last seen) and two links: url, the Ocean of Jobs page, to show first, and apply_url, the employer's page. How to search well: - Put one or two core title or skill words in query, such as "backend", "python" or "devops", and use the filters for place, seniority and dates. Every word in query must match, so a long description of the person returns little or nothing. - Search once. If that gives relevant candidates, do not search again for synonyms. If it gives nothing useful, change or broaden query once, keeping the same filters. - Across searches, treat the same id or the same apply_url as one job. - Open only the strongest few candidates with get_job, and read their descriptions for seniority, required skills and where the job can be done from before ranking them. - Give the number of recommendations asked for when enough jobs fit, and say so when fewer do. - Never call a listing reposted because of its age. Use lifetime.reappeared_at, and say when the tracked history is too short to tell.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "City name, e.g. Tel Aviv."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Words to search titles, companies, locations and descriptions, skills included, e.g. \"kubernetes go\". Quotes keep a phrase together."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 200,
      "minimum": 0
    },
    "company": {
      "type": "string",
      "description": "A company domain such as wix.com, or a name, which is looked up."
    },
    "country": {
      "type": "string",
      "description": "Two-letter country code, e.g. IL or US."
    },
    "seniority": {
      "enum": [
        "intern",
        "junior",
        "mid",
        "senior",
        "staff",
        "principal",
        "lead",
        "manager",
        "director",
        "exec"
      ],
      "type": "string"
    },
    "workplace": {
      "enum": [
        "remote",
        "hybrid",
        "onsite"
      ],
      "type": "string"
    },
    "salary_min": {
      "type": "integer",
      "minimum": 0,
      "description": "Lowest monthly gross salary in shekels."
    },
    "max_age_days": {
      "type": "integer",
      "minimum": 0,
      "description": "Only jobs posted within this many days."
    }
  },
  "additionalProperties": false
}
    arguments 67 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a4ce1b1b302d1f0a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a4ce1b1b302d1f0a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a4ce1b1b302d1f0a/badge.svg)](https://brick.blue/agent/a4ce1b1b302d1f0a?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.