Magnificent Jobs
REMOTE · MAGNIFICENTJOBS.COM
Semantic search over 3.5M+ live US job postings pulled straight from company ATSes. Read-only.
Available components
Last scanned (58 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 1 Sep 2026.
Category Search and Retrieval
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
Recent critical change
TLS certificate (2 Sept 2026). See the changelog before you install this server.
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 Security11
- TLS check failed: the certificate doesn't match the endpoint's hostname. See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 8 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Sept 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
- 31 Aug 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 8 Sept 2026 · Probed https://magnificentjobs.com/mcp
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: hostname_mismatch
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of magnificentjobs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| magnificentjobs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://magnificentjobs.com/mcp | TLS failed | ||
| http (plaintext) | http://magnificentjobs.com/mcp | HTTPS enforced | 301 | https://magnificentjobs.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 →
find_cities Find cities ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | – | City name prefix, e.g. 'san'. |
| state | string | – | Restrict to a state (name or 2-letter code). |
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | yes | – |
No examples provided.
get_job Get job details ~51
Full details for one job by slug: description, apply link, salary, skills, benefits, employer info.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The job slug from search_jobs results (last path segment of the url). |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | – | Direct apply link on the employer's ATS |
| ats | string|null | – | – |
| benefits | – | – | – |
| date_posted | string|null | – | – |
| description | string|null | – | – |
| description_source | string|null | – | – |
| education | – | – | – |
| employment_type | – | – | – |
| experience_level | string|null | – | – |
| key_skills | – | – | – |
| locations | – | – | – |
| org_industry | string|null | – | – |
| org_size | string|null | – | – |
| org_url | string|null | – | – |
| organization | string|null | – | – |
| requirements_summary | string|null | – | – |
| responsibilities_summary | string|null | – | – |
| salary | – | – | – |
| slug | string | yes | – |
| title | string|null | – | – |
| url | string | yes | – |
| visa_sponsorship | – | – | – |
| work_arrangement | string|null | – | – |
No examples provided.
list_states List states ~19
US states with the number of live jobs in each.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| states | array | yes | – |
No examples provided.
search_jobs Search jobs ~470
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | US city name, e.g. 'Denver' or 'Denver, CO'. Non-US cities are not covered and return no match. |
| employment_type | string | – | – |
| experience_level | string | – | Years-of-experience band. |
| limit | integer | – | Default 12. |
| offset | integer | – | For paging; use nextOffset from a previous call. |
| query | string | – | Expanded query, embedded verbatim: 'Full Job Title. One sentence of core responsibilities; 3-5 key skills/tools.' Keep user qualifiers (senior, night shift, fintech…). NO abbreviations or acronyms an… |
| radius_miles | integer | – | 10, 30 or 50 (default 50). Only used with city. |
| state | string | – | US state full name or 2-letter code. |
| work_arrangement | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| hasMore | boolean | yes | – |
| jobs | array | yes | – |
| mode | string | yes | Which search path ran (city_semantic, city_nearest, state_semantic, nationwide_semantic, newest, …) |
| nextOffset | number|null | yes | – |
| resolved | object | yes | How the request was interpreted: state, city + coordinates, radius, query, filters |
No examples provided.
How do I install the Magnificent Jobs MCP server?
Magnificent Jobs is a hosted endpoint at https://magnificentjobs.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 · magnificentjobs.com
claude mcp add --transport http com-magnificentjobs-jobs 'https://magnificentjobs.com/mcp'
What is the Magnificent Jobs MCP server?
Magnificent Jobs is an MCP server listed in the public MCP registry as com.magnificentjobs/jobs. Semantic search over 3.5M+ live US job postings pulled straight from company ATSes. Read-only. This page covers its hosted endpoint (https://magnificentjobs.com/mcp).
What tools does the Magnificent Jobs MCP server expose?
Magnificent Jobs exposes 4 tools: search_jobs, get_job, find_cities, list_states. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.
Does the Magnificent Jobs MCP server require authentication?
Its publisher declares no required credentials for Magnificent Jobs. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Magnificent Jobs MCP server still maintained?
Magnificent Jobs has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 1 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.