Magnificent Jobs MCP Server

by magnificentjobs Your server? Claim it

not responding

Magnificent Jobs is listed as active in the registry but did not answer our last check. It exposes 4 tools. Last commit 21 Aug 2026.

Semantic search over 3.5M+ live US job postings pulled straight from company ATSes. Read-only.

Uptime history 34 days of history · worst day 0%

34 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

104 ms

Response time

average over 24h

Stars

last commit 21 Aug 2026

What the code does

We read the source, 16 h ago · tools taken from the live server · rules 3dff92dd89df

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims read-only, but the code runs commands cli/bin/magnificentjobs.mjs:207

function has(bin) { return spawnSync(platform() === "win32" ? "where" : "which", [bin], { stdio: "ignore" }).status === 0; }

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command cli/bin/magnificentjobs.mjs:207

function has(bin) { return spawnSync(platform() === "win32" ? "where" : "which", [bin], { stdio: "ignore" }).status === 0; }

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Magnificent Jobs and you get told the day something new turns up.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add jobs --transport http https://magnificentjobs.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "jobs": {
      "url": "https://magnificentjobs.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.jobs]
url = "https://magnificentjobs.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "jobs": {
      "url": "https://magnificentjobs.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "jobs": {
      "url": "https://magnificentjobs.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

cities

find_cities

Look up US cities that currently have jobs (prefix match), with job counts. Use when a city name is ambiguous or you need the exact spelling before search_jobs.

job

get_job

Full details for one job by slug: description, apply link, salary, skills, benefits, employer info.

jobs

search_jobs

Search live job postings in the United States (US only — no other countries) by meaning (embedding similarity against the postings). YOU write the expanded query — it is embedded as-is, with no server-side rewriting — so always send `query` in this shape: "<Full job title>. <One sentence of what the role does; 3-5 key skills/tools>." NO ABBREVIATIONS anywhere in the query — spell everything out (ML → machine learning, AI → artificial intelligence, RN → registered nurse, SWE → software engineer, QA → quality assurance, PM → product manager, CDL → commercial driver's license, EMT → emergency medical technician, etc.) and keep the user's qualifiers (seniority, shift, domain). Example: user says 'ML eng jobs' → query 'Machine Learning Engineer. Builds, trains and deploys machine learning models; Python, PyTorch, MLOps, data pipelines.' Optionally add `city` (results within radius_miles of that city, ranked by relevance) and/or `state`. Without a city, ranks across the state or nationwide. Returns job cards with a `url` to show the user; call get_job for details.

states

list_states

US states with the number of live jobs in each.

Endpoints

URL	Transport	State	Latency	Checked
https://magnificentjobs.com/mcp	streamable-http	answering	104 ms	6 min ago

Alternatives to Magnificent Jobs

same job, measured the same way

HuntBoard

by huntboard

Search real, recent job postings from company career pages and ATS boards, scored for fit.

1 tools answering

ENTRA Jobs

by dubaikseniia-wq

Verified AI/tech jobs from company ATSs: search, fit matching, salary stats; employer job posting

8 tools answering

FrankSpace Public MCP

by co-frankspace

Read-only search over live UK office & workspace listings on FrankSpace.

5 tools answering

Jobs Search Multi

by dataleadspro

Search job postings across Indeed, LinkedIn, and more from one request - titles, companies

4 tools answering

MCP Lever

by smeet666

Search public Lever job boards: resolve a company, read its openings, read one in full.

63 installs/wk local only

Jobily Jobs

by jobily

Search Greek job listings on Jobily.gr by role, location, sector or company. Anonymous, read-only.

5 tools answering

Workway

by enigma-52

Search 490k+ live jobs from company ATS boards, save roles, follow companies, manage talent profile.

answering

Intermediair Jobs

by intermediair-www

Search and retrieve job postings on Intermediair (read-only).

2 tools answering

Magnificent Jobs — questions

Answers built from our own checks of this server.

What can Magnificent Jobs do?

It exposes 4 tools, read directly from the server on our last check. Among them: find_cities, get_job, list_states, search_jobs. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Magnificent Jobs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 104 ms. The bar chart above shows every period we have measured.

The registry lists Magnificent Jobs as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Magnificent Jobs?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Magnificent Jobs need an API key?

No. Magnificent Jobs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

Is Magnificent Jobs open source?

Yes — it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.