Skip to content
Job Opportunities API logo

Job Opportunities API MCP server

Which servers in the official MCP registry are Job Opportunities API's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Job Opportunities API

Whose server it is
  • Registry nameorg.jobopportunitiesapi/mcpverified in the MCP registry

The registry name sits under jobopportunitiesapi.org. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools6
  • Server calls itselfjobopportunitiesapi
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 564 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Check per-field provenance before building on a filter", the likely first call is get_job.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-21
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer576 ms
  • Space in an agent's context≈ 3,344 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • not sure · Launch a niche job board with live employer postings
  • not sure · Feed AI agents with verified employer job postings
  • can do · Check per-field provenance before building on a filter

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-21
  • search_jobs

    Search JOA's live ledger of employer-direct job postings (current count: the coverage tool). Filter by country, city, US state, job category/family, seniority, remote type, employment type, engagement (employee/vendor), contract category…

  • get_job

    Fetch a single job posting's full detail: the complete advert description, per-field provenance (published/inferred/absent), and closure info if the role has since closed. NEEDS a JOA API key -- free Explore key at…

  • company_hiring

    Look up one employer by slug: its profile (website, industry, live open-role count) and its 30/90/365-day open-roles trend (daily snapshots from 2026-10-06, earlier gaps; each point is labelled snapshot or reconstructed). The open-roles…

  • market_signals

    Aggregate, keyless market statistics: salary percentiles (p25/p50/p75, annualised EUR) and time-to-fill (days) by job family x country x seniority, plus listing/company/open/closed counts for that segment. Every percentile is suppressed…

  • coverage

    Aggregate, keyless facts about the dataset itself: total live listings, employers with a live listing, per-source breakdown, and freshness (how recently every row was last re-confirmed live at its source). Optionally also the full…

  • changes_since

    The incremental change feed: every job created, updated, withdrawn or delisted since a given cursor, in change order, with a next_since cursor to resume from -- how an integrator keeps a local copy of the ledger current without…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "jobopportunitiesapi": {
      "type": "http",
      "url": "https://api.jobopportunitiesapi.org/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http jobopportunitiesapi https://api.jobopportunitiesapi.org/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.jobopportunitiesapi.org/mcp as a custom connector in the settings.

OpenAPI spec

19 paths, read 2026-10-21. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.