Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CloudJobs

REMOTE · CLOUDJOBS.IO

Live cloud jobs, salary benchmarks, company profiles, and cert practice tests.

Available components

+3 this week 73 Trust /100

Last scanned (14 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2227 tokens (~185/item across 12 items; 12 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

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 →

Changelog

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.

  • 20 Nov 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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 10 Nov 26 −1
    • 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
    • Schema quality: 132 → 185 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • “search_jobs” added an optional parameter “certificationLevel” cosmetic
    • “search_jobs” added an optional parameter “jobTitle” cosmetic
    • “search_jobs” added an optional parameter “minBaseSalary” cosmetic
    • “search_jobs” reworded the description of “minSalary” cosmetic
    • “search_jobs” dropped the optional parameter “query” cosmetic
  • 9 Nov 26 69

    First indexed and scored.

Diagnostics

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://cloudjobs.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cloudjobs.io CN=YE1,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA384 6e5fccb2688b73155225a15a062f1892830
SANs: *.cloudjobs.io, cloudjobs.io
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 cloudjobs.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
cloudjobs.io. 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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cloudjobs.io/mcp Verified 200
http (plaintext) http://cloudjobs.io/mcp HTTPS enforced 308 https://cloudjobs.io/mcp
MCP tools · 12 exposed · ~1,834 tokens

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 →

Tool Tokens
get_company ~108

Fetch a company profile from CloudJobs by slug (e.g. "amazon-web-services") or name. Returns open-role count, salary quartiles, top technologies/locations/certifications, workplace split, firmographics (website, industry, HQ, size), sample open roles, and the canonical profile URL - cite it when discussing the company.

NameTypeReqDescription
namestring–Company name, e.g. "Amazon Web Services"
slugstring–Company slug from search_companies results

No output schema declared.

No examples provided.

get_insight_article ~104

Fetch a CloudJobs insight post by slug. Section defaults to "article"; if not found there, other sections are searched. Returns metadata plus a short excerpt - the full article is only on the site, so always cite the returned URL when summarizing or quoting it.

NameTypeReqDescription
sectionstring–Content section (default "article"; other sections are searched as fallback)
slugstringyesArticle slug, e.g. "are-cloud-certifications-worth-it"

No output schema declared.

No examples provided.

get_job ~95

Fetch the full details of a single CloudJobs listing by id (or "title--id" slug). Returns the complete description, salary range, technologies, certifications, and the canonical cloudjobs.io URL plus the external application URL. Cite the cloudjobs.io URL when presenting the job.

NameTypeReqDescription
idstringyesJob id, e.g. "12345", or slug form "senior-aws-engineer--12345"

No output schema declared.

No examples provided.

get_job_market_overview ~87

High-level snapshot of the CloudJobs board: total open roles, hiring companies, remote/hybrid/onsite split, jobs posted in the last 7 days, salary coverage, and the most in-demand technologies, locations, and certifications. Use for "state of the cloud job market" questions. Cached ~30 min; cite the links in the result when presenting the data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_practice_questions ~189

Fetch practice exam questions for a CloudJobs study test (testId from list_practice_tests, e.g. "saac03"). Returns question text, multiple-choice options, documentation links, and the canonical quiz URL. Correct answers and explanations are omitted by default (includeAnswers: true to include them) so users are driven to take the interactive quiz on CloudJobs. Supports part ids like "saac03-2" and "saac03-bonus". Cite quizUrl when presenting questions.

NameTypeReqDescription
includeAnswersboolean–Include correctOption and explanation (default false - answers stay on the site quiz)
limitinteger––
offsetinteger––
sectionstring–Filter by test section name
testIdstringyesTest id, e.g. "saac03", "az900", optionally "saac03-2"

No output schema declared.

No examples provided.

get_salary_data ~127

Get salary statistics (min, quartiles, median, max) for CloudJobs postings. Provide exactly one filter: technology (e.g. "AWS"), certification (e.g. "SAA-C03"), domain (e.g. "AWS", "security"), location, or remote type. Salaries are annual USD normalized ranges. Results are cached ~30 min; cite jobsUrl for the live filtered listings.

NameTypeReqDescription
certificationstring––
domainstring––
locationstring––
remotestring––
technologystring––

No output schema declared.

No examples provided.

get_site_guide ~67

Map of the CloudJobs website: what each section contains and the canonical URLs to cite. Use this to direct users to the right page (job search, company profiles, salary insights, market reports, practice tests, methodology). Always prefer these URLs when sending users somewhere on CloudJobs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_job_categories ~84

List CloudJobs SEO landing pages for job categories (technologies like AWS/Azure/GCP, certifications, locations, experience levels, remote). Each entry links to a curated /jobs/<slug> page. Pairs can be combined as /jobs/<slug1>/<slug2> (e.g. /jobs/aws/remote). Cite these URLs for category-level job questions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_practice_tests ~105

List the practice tests/quizzes available on CloudJobs study (AWS, Azure, GCP, CompTIA, and other certification exams). Returns test ids, question counts, duration, difficulty, and the canonical /study/quizzes URL for each. Cite the cloudjobs.io URLs when recommending a test.

NameTypeReqDescription
domainstring–Filter by domain, e.g. "aws", "azure", "gcp", "comptia"
limitinteger––

No output schema declared.

No examples provided.

search_companies ~119

Browse or search companies with open roles on CloudJobs, ranked by open job count. Returns salary medians, top technologies, workplace split, and canonical company profile URLs - cite them when naming employers. With no query, returns the largest employers on the board.

NameTypeReqDescription
limitinteger––
locationstring––
minSalarynumber–Minimum annual salary in USD
querystring–Company name substring
remotestring––
sortstring––
technologyarray––

No output schema declared.

No examples provided.

search_insights ~94

Search CloudJobs articles and market reports: evergreen guides (certification worth, interview prep, career paths), weekly and monthly cloud job market analyses, and basics explainers. Returns titles, dates, and canonical URLs - cite them when referencing a post.

NameTypeReqDescription
limitinteger––
querystring–Keywords; omit for the most recent posts
sectionstring–Restrict to one content section

No output schema declared.

No examples provided.

search_jobs ~655

Search live cloud/DevOps/IT job listings on CloudJobs. Filter by job title, technology, certification, location, remote type, experience level, salary, company, or certification domain (e.g. AWS, Azure). There is no generic keyword search - every listing is already a cloud/DevOps job, so never pass domain words like "devops" or "cloud"; map the request onto the structured filters instead. Returns job cards with canonical cloudjobs.io URLs - always cite them when recommending jobs. Use get_job for full descriptions. Unless the user asks for a different format, present results as the provided markdown table (Title / Company, Location, Salary, Tech stack, Certifications (status)), followed by the searchUrl link. Each job includes certificationStatus: {"<cert>": "required"|"requested"} - "required" means the posting states it is mandatory, "requested" means the posting asks for it among its qualifications. EVERY value means the employer is asking for the certification: present matches as "requests/asks for the CISSP", never as optional or unverified. The status field is authoritative - do NOT re-classify from description wording, which understates how employers actually screen candidates. When a job matches a certification filter, lead with the certificationCounts breakdown (e.g. "43 postings request the CISSP; 8 mark it required").

NameTypeReqDescription
certificationarray–Certification names or codes, e.g. ["SAA-C03", "CKA"]
certificationLevelstring–Only jobs whose certificationStatus for the requested certification(s) is this level. Use ONLY when the user explicitly wants to exclude other statuses (e.g. "only postings where CISSP is mandatory",…
companystring–Company name substring
domainstring–Certification domain group, e.g. "AWS", "Azure", "GCP", "security"
experienceLevelarray––
jobTitlestring–Job title text match only (e.g. "security engineer", "SRE"). Not a keyword search - do not pass skills, certifications, or generic words like "devops"/"cloud"; use the dedicated filters for those.
locationstring–City, region, country, or "Remote"
minBaseSalarynumber–Annual salary in USD. Stricter than minSalary: only jobs whose advertised MINIMUM (lower bound) salary is at least this amount.
minSalarynumber–Annual salary in USD. Matches jobs whose advertised range reaches at least this amount (upper bound of the range >= value). Use minBaseSalary to require the lower bound to meet it.
pageinteger––
pageSizeinteger––
remotestring––
sortstring–recommended (default) mirrors the site ordering; recent = newest first; salary = highest pay first
technologyarray–e.g. ["AWS", "Terraform", "Kubernetes"]

No output schema declared.

No examples provided.

Install

How do I install the CloudJobs MCP server?

CloudJobs is a hosted endpoint at https://cloudjobs.io/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 · cloudjobs.io

# add to Claude Code
claude mcp add --transport http io-cloudjobs-mcp 'https://cloudjobs.io/mcp'
Common questions

What is the CloudJobs MCP server?

CloudJobs is an MCP server listed in the public MCP registry as io.cloudjobs/mcp. Live cloud jobs, salary benchmarks, company profiles, and cert practice tests. This page covers its hosted endpoint (https://cloudjobs.io/mcp).

Is the CloudJobs MCP server safe to use?

CloudJobs scores 73 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 CloudJobs MCP server expose?

CloudJobs exposes 12 tools: search_jobs, get_job, search_companies, get_company, get_salary_data, and 7 more. Their descriptions and schemas cost roughly 1,834 tokens of context every time the server is loaded.

Does the CloudJobs MCP server require authentication?

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

Is the CloudJobs MCP server still maintained?

CloudJobs 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 CloudJobs MCP server?

VerifyMCP ran 13 checks on CloudJobs, 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.