Nectar Jobs MCP server
com.nectarjobs/jobsnectarjobs.comstreamable-httpv1.2.1Scanned
Search 3M+ live job postings: salaries, filters, similar roles and CV matching. Free, no account.
7 tools: 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Nectar Jobs MCP server can do
The Nectar Jobs MCP server is published by nectarjobs.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: aggregate_jobs, job_trends and recommend_jobs), but cannot delete data. 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 3Claude Code: ask
aggregate_jobsAggregate 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
job_trendsHow a slice of the market has changed OVER TIME — use this for "is X growing/shrinking", "hiring trend", "more or fewer than last year".No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
recommend_jobsRank jobs by how well they match a résumé or free-text description of what the candidate wants.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
find_similar_jobsFind jobs semantically similar to a given job (excludes its duplicates).No findings
Why it is in this group
- The name "find_similar_jobs" says "find": a word for reading.
Description, as the server wrote it 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").
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_jobFetch a single job's full details, including its description and any duplicate postings of the same role on other sources.No findings
Why it is in this group
- The name "get_job" says "get": a word for reading.
Description, as the server wrote it Fetch a single job's full details, including its description and any duplicate postings of the same role on other sources.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_statsReturn corpus-wide coverage: total jobs, counts by source, and top companies.No findings
Why it is in this group
- The name "get_stats" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_jobsSearch live job postings: use when the user asks what jobs are open for a role, a place, a salary or a skill.1 finding
Why it is in this group
- The name "search_jobs" says "search": a word for reading.
Findings
- Info
The description is 2,685 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...when nothing matched, a ``hint`` names the filter most worth loosening."
Description, as the server wrote it 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 a posting which says nothing about its hours is recorded as ``full_time``, so that value is the least informative of the set. posted_since_days: only jobs posted within this many days. mode: "hybrid" (default, best), "semantic" (meaning-based), or "keyword" (exact). sort: "relevance" (default), "date" (newest first), or "salary" (highest first). page: 1-based page number, for paging past ``limit`` results. limit: max results per page (1-100). Returns a dict with ``total``, a ``jobs`` list (duplicates collapsed) and ``attribution``; when nothing matched, a ``hint`` names the filter most worth loosening.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nectarjobs.com/mcp: tools/list returned 7 tools to an anonymous client, including aggregate_jobs (write), job_trends (write), recommend_jobs (write)
Findings
Matches of fixed checks, with the text they matched.
- Infosearch_jobs
The description is 2,685 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...when nothing matched, a ``hint`` names the filter most worth loosening."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:aggregate_jobsChanges thingsdescription
- Changed:find_similar_jobsOnly readsdescription
- Changed:recommend_jobsChanges thingsdescription
- Changed:search_jobsOnly readsdescription
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http jobs https://nectarjobs.com/mcpclaude mcp add --transport http jobs https://nectarjobs.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__jobs__search_jobs",
"mcp__jobs__find_similar_jobs",
"mcp__jobs__get_job",
"mcp__jobs__get_stats"
],
"ask": [
"mcp__jobs__aggregate_jobs",
"mcp__jobs__job_trends",
"mcp__jobs__recommend_jobs"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jobs. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.nectarjobs/jobs/verify?hash=50919cc56629c19c627f8e1e5d28038cb0389b4cbac4d24dfc4fe0e7a2fea33e" | jq -e '.changed == false'Pinned hash 50919cc56629, from Nov 18, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.nectarjobs/jobs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.nectarjobs/jobs)Source: MCP Registry. Synced Nov 18, 2026, 18:17 UTC.
Nectar Jobs MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Nectar Jobs MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Nectar Jobs MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Nectar Jobs MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Nectar Jobs MCP server have?
- 7 tools: 3 write, 4 read. aggregate_jobs, job_trends, recommend_jobs, search_jobs, find_similar_jobs, get_job and get_stats.
Does the Nectar Jobs MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Nectar Jobs MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Nectar Jobs MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.