Nectar Jobs
REMOTE · NECTARJOBS.COM
Search 3M+ live job postings: salaries, filters, similar roles and CV matching. Free, no account.
Available components
Last scanned (21 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 18 Nov 26 0
- 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 security
- 17 Nov 26 +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.
- 16 Nov 26 0
- 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 security
- 15 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://nectarjobs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nectarjobs.com | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ec355eecc2eb416a0e1e870622c97cda |
| SANs: nectarjobs.com, *.nectarjobs.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nectarjobs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| nectarjobs.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://accounts.google.com https://apis.google.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://translate.googleapis.com https://accounts.google.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src https://accounts.google.com; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nectarjobs.com/mcp | Verified | 200 | |
| http (plaintext) | http://nectarjobs.com/mcp | HTTPS enforced | 301 | https://nectarjobs.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aggregate_jobs Count jobs in a slice of the market ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| company | – | – | – |
| country | – | – | – |
| employment_type | – | – | – |
| location | – | – | – |
| posted_since_days | – | – | – |
| query | string | – | – |
| remote | – | – | – |
| salary_min | – | – | – |
| seniority | – | – | – |
| source | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_similar_jobs Find similar jobs ~133
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").
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_same_company | boolean | – | – |
| job_id | integer | yes | – |
| limit | integer | – | – |
| max_per_company | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_job Get one job in full ~41
Fetch a single job's full details, including its description and any duplicate postings of the same role on other sources.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_stats Index coverage ~49
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
job_trends Job posting trends over time ~478
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | – |
| category | – | – | – |
| company | – | – | – |
| country | – | – | – |
| employment_type | – | – | – |
| location | – | – | – |
| measure | string | – | – |
| query | string | – | – |
| remote | – | – | – |
| salary_min | – | – | – |
| seniority | – | – | – |
| since_days | integer | – | – |
| source | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recommend_jobs Match jobs to a CV ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| country | – | – | – |
| employment_type | – | – | – |
| limit | integer | – | – |
| location | – | – | – |
| remote | – | – | – |
| resume_text | string | yes | – |
| salary_min | – | – | – |
| seniority | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_jobs Search jobs ~679
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…
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| company | – | – | – |
| country | – | – | – |
| employment_type | – | – | – |
| limit | integer | – | – |
| location | – | – | – |
| mode | string | – | – |
| page | integer | – | – |
| posted_since_days | – | – | – |
| query | string | – | – |
| remote | – | – | – |
| salary_min | – | – | – |
| seniority | – | – | – |
| sort | string | – | – |
| source | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · nectarjobs.com
claude mcp add --transport http com-nectarjobs-jobs 'https://nectarjobs.com/mcp'
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.