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.

CyberJobs.cc

REMOTE · CYBERJOBS.CC

Search open cybersecurity jobs (SOC, AppSec, cloud, IAM, pentest, GRC) with posted pay, read hourly.

Available components

+3 this week 84 Trust /100

Last scanned (21 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 Security97
  • 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 656 tokens (~164/item across 4 items; 4 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 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.

  • 17 Nov 26 0
    • Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads security
  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Nov 26 0
    • Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads security
  • 14 Nov 26 +1
    • Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads security
  • 13 Nov 26 0
    • Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads security
  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
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://cyberjobs.cc/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cyberjobs.cc CN=YR1,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 RSA 2048 SHA256-RSA 6359a33c1dc97d361ce6262210ead1af41d
SANs: cyberjobs.cc
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cyberjobs.cc. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cc. DS published 12593 13 Verified
cyberjobs.cc. 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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://partner.googleadservices.com https://www.googletagservices.com https://adservice.google.com https://fundingchoicesmessages.google.com https://*.adtrafficquality.google https://www.youtube.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://*.doubleclick.net https://*.adtrafficquality.google https://fundingchoicesmessages.google.com https://csi.gstatic.com https://elevenlabs.io
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cyberjobs.cc/api/mcp Verified 200
http (plaintext) http://cyberjobs.cc/api/mcp HTTPS enforced 308 https://cyberjobs.cc/api/mcp
MCP tools · 4 exposed · ~498 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_cybersecurity_employer ~73

One employer on the board: what kind of company it is, its open security roles and the salaries they state, where it hires, and a link to its page.

NameTypeReqDescription
platformstringyesThe employer's name or slug, e.g. 'CrowdStrike' or 'avepoint'.

No output schema declared.

No examples provided.

get_cybersecurity_job_market ~104

How many security roles are open today, how many first appeared in the last 7 days, and the open roles per specialty and per employer (with each employer's slug for search_cybersecurity_jobs). Can be limited to the roles open to applicants in one country.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code (e.g. 'US', 'IN'): count only roles that accept applicants in that country.

No output schema declared.

No examples provided.

get_cybersecurity_salaries ~60

The yearly salaries open security postings state today, per specialty: the middle salary and the typical band, with how many stated ranges and employers each figure rests on. A specialty is included once at least three employers state ranges for it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_cybersecurity_jobs ~261

Search open cybersecurity roles (SOC and incident response, security engineering, cloud security, application security, identity and access, penetration testing and red team, threat intelligence, GRC and compliance, security architecture and consulting and security leadership) read from the hiring systems of 713 employers. Returns each role's title, employer, specialty, stated salary, where it hires and a link to the role. Every filter is optional.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code (e.g. 'US', 'GB', 'DE'): only roles that accept applicants in that country.
kindstring–Security specialty, one of the listed slugs, e.g. 'security-operations', 'cloud-security', 'governance-risk-compliance'.
limitinteger–Number of roles to return (1 to 25).
min_salary_usdinteger–Only roles whose stated yearly salary reaches at least this many US dollars.
platformstring–Employer slug; get_cybersecurity_job_market lists them.
querystring–Words matched against role titles, e.g. 'SOC analyst', 'Okta', 'penetration tester', 'FedRAMP'.

No output schema declared.

No examples provided.

Install

How do I install the CyberJobs.cc MCP server?

CyberJobs.cc is a hosted endpoint at https://cyberjobs.cc/api/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 · cyberjobs.cc

# add to Claude Code
claude mcp add --transport http cc-cyberjobs-mcp 'https://cyberjobs.cc/api/mcp'
Common questions

What is the CyberJobs.cc MCP server?

CyberJobs.cc is an MCP server listed in the public MCP registry as cc.cyberjobs/mcp. Search open cybersecurity jobs (SOC, AppSec, cloud, IAM, pentest, GRC) with posted pay, read hourly. This page covers its hosted endpoint (https://cyberjobs.cc/api/mcp).

Is the CyberJobs.cc MCP server safe to use?

CyberJobs.cc scores 84 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 CyberJobs.cc MCP server expose?

CyberJobs.cc exposes 4 tools: search_cybersecurity_jobs, get_cybersecurity_salaries, get_cybersecurity_job_market, get_cybersecurity_employer. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.

Does the CyberJobs.cc MCP server require authentication?

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

Is the CyberJobs.cc MCP server still maintained?

CyberJobs.cc 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 CyberJobs.cc MCP server?

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