# Nectar Jobs (remote · nectarjobs.com)

Search 3M+ live job postings: salaries, filters, similar roles and CV matching. Free, no account.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `nectarjobs.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs.md), [page](https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs)

## Channel facts

- Endpoint: `https://nectarjobs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2251 tokens (~321/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Nectar Jobs MCP server?

Nectar Jobs is a hosted endpoint at https://nectarjobs.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.

### Claude

```bash
claude mcp add --transport http com-nectarjobs-jobs 'https://nectarjobs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nectarjobs-jobs": {
      "url": "https://nectarjobs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nectarjobs-jobs": {
      "type": "http",
      "url": "https://nectarjobs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nectarjobs-jobs]
url = "https://nectarjobs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nectarjobs-jobs": {
      "type": "remote",
      "url": "https://nectarjobs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-nectarjobs-jobs --url 'https://nectarjobs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nectarjobs-jobs:
    url: "https://nectarjobs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nectarjobs-jobs": {
      "Transport": "http",
      "Url": "https://nectarjobs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nectarjobs-jobs -t streamable-http -u 'https://nectarjobs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-nectarjobs-jobs": {
      "type": "http",
      "url": "https://nectarjobs.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +1)

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

### 2026-11-19 (score 73, +1)

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

### 2026-11-18 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_jobs” rewrote its description, which is the text the model reads

### 2026-11-17 (score 72, +1)

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

### 2026-11-16 (score 71, 0)

- [security] Tool “aggregate_jobs” rewrote its description, which is the text the model reads
- [security] Tool “find_similar_jobs” rewrote its description, which is the text the model reads
- [security] Tool “recommend_jobs” rewrote its description, which is the text the model reads

### 2026-11-15 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 71)

First indexed and scored.

## MCP tools (7)

### `search_jobs` (~679 tokens)

Search jobs

Search live job postings: use when the user asks what jobs are open for a role, a place,
    a salary or a skill. Each job carries ``url``, its page on Nectar Jobs, where the person applies.

    Args:
        query: keyword or natural-language query. Words that name an occupation ("manager",
            "software engineer") are matched against the TITLE; other words match the whole
            document (title, company, description), so a generic word's ``total`` overcounts —
            to compare role-type volumes, use aggregate_jobs instead.
        location: city or country substring over the posting's location text (matches broadly:
            "New York" includes the whole state). For a whole country, prefer ``country``.
        remote: filter to remote (true) or on-site (false) roles.
        salary_min: only roles whose salary range reaches this amount (raw number — currencies
            are not converted, so only meaningful combined with a single-currency market).
        company: company name substring.
        source: restrict to one source/board; get_stats lists the live sources and their sizes.
        seniority: one of intern, junior, senior, staff, principal, manager, director.
        category: job function from the site taxonomy (Engineering, "Data & ML", Product, Design,
            Sales, Marketing, "Customer Support", Operations, "Finance & Accounting",
            "People & HR", Legal, "IT & Security", …) — aggregate_jobs reports the live values.
        country: 2-letter ISO code ("US", "IN") — matches the derived country, more precise than
            a ``location`` substring.
        employment_type: contract or hours — permanent, fixed_term, contract, freelance, temporary,
            casual, seasonal, internship, apprenticeship, graduate, working_student, volunteer,
            self_employed, full_time, part_time, job_share, shift, term_time. Contract basis and
            schedule are one filter; a posting carries one of each. Note that…

Input parameters:

- `category`
- `company`
- `country`
- `employment_type`
- `limit` (integer)
- `location`
- `mode` (string)
- `page` (integer)
- `posted_since_days`
- `query` (string)
- `remote`
- `salary_min`
- `seniority`
- `sort` (string)
- `source`

### `aggregate_jobs` (~303 tokens)

Count jobs in a slice of the market

Aggregate counts for a filtered slice of the corpus — the tool for market/trend questions
    ("what kinds of roles are hiring in Pune?"), instead of issuing many limit-1 searches.

    Takes the same filters as search_jobs (keyword matching included, see its ``query`` note) and
    returns the slice's ``total`` plus breakdowns, each a {value: count} dict, biggest first:
    ``by_category`` (job function — the role-type axis), ``by_seniority``,
    ``by_employment_type`` (contract basis and hours in one axis; ``full_time`` is inflated because
    a posting silent about its hours is recorded as full-time), ``top_companies``,
    ``top_skills``, ``by_source``, ``benefits``, ``company_size``, ``lang``, and ``salary`` —
    per-currency posting counts with salary_max quartiles (currencies deliberately not blended).
    Every count collapses duplicate postings, so numbers are comparable to search totals. A
    breakdown on a field you filtered by lists only the values you filtered to.

Input parameters:

- `category`
- `company`
- `country`
- `employment_type`
- `location`
- `posted_since_days`
- `query` (string)
- `remote`
- `salary_min`
- `seniority`
- `source`

### `job_trends` (~478 tokens)

Job posting trends over time

How a slice of the market has changed OVER TIME — use this for "is X growing/shrinking",
    "hiring trend", "more or fewer than last year". aggregate_jobs describes a slice as it stands
    today; this one shows its history.

    Takes the same filters as aggregate_jobs, plus ``bucket`` ("day"/"week"/"month"),
    ``since_days`` (at most 730), and ``measure``. Returns a ``series``, oldest first, each period carrying
    ``postings`` (roles dated to it, duplicates collapsed) and ``still_open`` (how many are live
    now — the rest have since closed).

    ``measure="posted"`` (default) uses the employer's stated date: the market signal, but
    nullable, so check ``without_date`` — it counts roles the clock cannot place, and when it
    rivals the series totals the trend describes a minority of the slice.

    ``measure="first_seen"`` uses when we first crawled the row. Complete, but it measures OUR
    coverage: a backfill or a newly onboarded board appears as a spike of hundreds of thousands
    that is not a hiring event. Use it to audit ingestion, not to infer demand.

    Either way, periods before ``earliest`` are empty because we hold no data that far back, not
    because hiring stopped — never report that as a decline.

    CRITICAL for "posted": only compare periods at or after ``crawl_started``. Earlier ones are
    left-censored — the first crawl could only capture roles still live when it ran, so anything
    posted before that and already closed was never seen. Those buckets undercount severely (their
    ``still_open`` sits near 100%, the giveaway), and reading across the boundary turns the
    crawler's start date into a fake hiring boom.

Input parameters:

- `bucket` (string)
- `category`
- `company`
- `country`
- `employment_type`
- `location`
- `measure` (string)
- `query` (string)
- `remote`
- `salary_min`
- `seniority`
- `since_days` (integer)
- `source`

### `find_similar_jobs` (~133 tokens)

Find similar jobs

Find jobs semantically similar to a given job (excludes its duplicates).

    At most ``max_per_company`` results per company (0 = uncapped; spellings of one employer, such
    as "Thales" and "Thales Group", count together), so one employer's near-identical
    postings don't fill the list; ``exclude_same_company`` drops the anchor's own company entirely
    ("roles like this elsewhere").

Input parameters:

- `exclude_same_company` (boolean)
- `job_id` (integer, required)
- `limit` (integer)
- `max_per_company` (integer)

### `recommend_jobs` (~268 tokens)

Match jobs to a CV

Rank jobs by how well they match a résumé or free-text description of what
    the candidate wants. Returns the best-matching jobs first.

    ``country`` (ISO-2, e.g. GB) or ``location`` (a city or region) is REQUIRED — ask the seeker
    where they can work rather than guessing. Semantic ranking over every country returns the
    nearest postings on earth, most of which the person cannot take.

    ``resume_text``: only about the first 400 words shape the ranking; anything after them is not
    read. For a longer CV, send what defines the person's next role first: the role they want,
    their headline, their recent roles and their key skills, not the whole document in order.

    Ranking is purely semantic; the filters are hard. ``seniority`` (intern, junior, senior,
    staff, principal, manager, director) filters to exactly that tag — many postings carry none,
    so only pass it when the seeker insists.

Input parameters:

- `category`
- `country`
- `employment_type`
- `limit` (integer)
- `location`
- `remote`
- `resume_text` (string, required)
- `salary_min`
- `seniority`

### `get_job` (~41 tokens)

Get one job in full

Fetch a single job's full details, including its description and any
    duplicate postings of the same role on other sources.

Input parameters:

- `job_id` (integer, required)

### `get_stats` (~49 tokens)

Index coverage

Return corpus-wide coverage: total jobs, counts by source, and top companies.
    For the same numbers on a filtered slice (a location, a company, a query), use
    aggregate_jobs.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 71

## Common questions

### What is the Nectar Jobs MCP server?

Nectar Jobs is an MCP server listed in the public MCP registry as com.nectarjobs/jobs. Search 3M+ live job postings: salaries, filters, similar roles and CV matching. Free, no account. This page covers its hosted endpoint (https://nectarjobs.com/mcp).

### Is the Nectar Jobs MCP server safe to use?

Nectar Jobs scores 74 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 Nectar Jobs MCP server expose?

Nectar Jobs exposes 7 tools: search_jobs, aggregate_jobs, job_trends, find_similar_jobs, recommend_jobs, and 2 more. Their descriptions and schemas cost roughly 1,951 tokens of context every time the server is loaded.

### Does the Nectar Jobs MCP server require authentication?

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

### Is the Nectar Jobs MCP server still maintained?

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

### What did VerifyMCP test on the Nectar Jobs MCP server?

VerifyMCP ran 13 checks on Nectar Jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://nectarjobs.com/mcp
- Website: https://nectarjobs.com/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs.json
- HTML version of this page: https://verifymcp.io/servers/com-nectarjobs-jobs/nectarjobs
