# CyberJobs.cc (remote · cyberjobs.cc)

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

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `cyberjobs.cc`: 84/100 (this document), [markdown](https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp.md), [page](https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp)

## Channel facts

- Endpoint: `https://cyberjobs.cc/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http cc-cyberjobs-mcp 'https://cyberjobs.cc/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cc-cyberjobs-mcp": {
      "url": "https://cyberjobs.cc/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cc-cyberjobs-mcp": {
      "type": "http",
      "url": "https://cyberjobs.cc/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cc-cyberjobs-mcp]
url = "https://cyberjobs.cc/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cc-cyberjobs-mcp": {
      "type": "remote",
      "url": "https://cyberjobs.cc/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cc-cyberjobs-mcp --url 'https://cyberjobs.cc/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cc-cyberjobs-mcp:
    url: "https://cyberjobs.cc/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cc-cyberjobs-mcp": {
      "Transport": "http",
      "Url": "https://cyberjobs.cc/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cc-cyberjobs-mcp -t streamable-http -u 'https://cyberjobs.cc/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cc-cyberjobs-mcp": {
      "type": "http",
      "url": "https://cyberjobs.cc/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 84, +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.

### 2026-11-19 (score 83, +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.

### 2026-11-17 (score 82, 0)

- [security] Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads

### 2026-11-16 (score 82, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-15 (score 81, 0)

- [security] Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads

### 2026-11-14 (score 81, +1)

- [security] Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads

### 2026-11-13 (score 80, 0)

- [security] Tool “search_cybersecurity_jobs” rewrote its description, which is the text the model reads

### 2026-11-12 (score 80, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `search_cybersecurity_jobs` (~261 tokens)

Search cybersecurity jobs

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.

Input parameters:

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

### `get_cybersecurity_salaries` (~60 tokens)

Cybersecurity salaries by specialty

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.

### `get_cybersecurity_job_market` (~104 tokens)

Cybersecurity job market

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.

Input parameters:

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

### `get_cybersecurity_employer` (~73 tokens)

One employer's security roles and salaries

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.

Input parameters:

- `platform` (string, required): The employer's name or slug, e.g. 'CrowdStrike' or 'avepoint'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 82
- 2026-11-15: 81
- 2026-11-14: 81
- 2026-11-13: 80
- 2026-11-12: 80
- 2026-11-11: 79

## 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.

## Links

- Remote endpoint: https://cyberjobs.cc/api/mcp
- Website: https://cyberjobs.cc/
- Changelog RSS feed: https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cc-cyberjobs-mcp/api-mcp
