# NextGen Energy Jobs (remote · www.nextgenenergyjobs.com)

Search open jobs in grid, nuclear, renewables, storage and data centers. Read-only, no login.

- 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 · `www.nextgenenergyjobs.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-nextgenenergyjobs-jobs/api-mcp.md), [page](https://verifymcp.io/servers/com-nextgenenergyjobs-jobs/api-mcp)

## Channel facts

- Endpoint: `https://www.nextgenenergyjobs.com/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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 702 tokens (~234/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 NextGen Energy Jobs MCP server?

NextGen Energy Jobs is a hosted endpoint at https://www.nextgenenergyjobs.com/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 com-nextgenenergyjobs-jobs 'https://www.nextgenenergyjobs.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nextgenenergyjobs-jobs": {
      "url": "https://www.nextgenenergyjobs.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nextgenenergyjobs-jobs": {
      "type": "http",
      "url": "https://www.nextgenenergyjobs.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nextgenenergyjobs-jobs]
url = "https://www.nextgenenergyjobs.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nextgenenergyjobs-jobs": {
      "type": "remote",
      "url": "https://www.nextgenenergyjobs.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-nextgenenergyjobs-jobs --url 'https://www.nextgenenergyjobs.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nextgenenergyjobs-jobs:
    url: "https://www.nextgenenergyjobs.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nextgenenergyjobs-jobs": {
      "Transport": "http",
      "Url": "https://www.nextgenenergyjobs.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nextgenenergyjobs-jobs -t streamable-http -u 'https://www.nextgenenergyjobs.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-nextgenenergyjobs-jobs": {
      "type": "http",
      "url": "https://www.nextgenenergyjobs.com/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-20 (score 84, +1)

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

### 2026-11-18 (score 83, +1)

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

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

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

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

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

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

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

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

### 2026-11-07 (score 78, +1)

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

### 2026-11-06 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `search_jobs` (~371 tokens)

Search energy jobs

Use this when the user wants to find open jobs in the modern power sector: grid, nuclear, renewables, data-center power. Searches active postings on nextgenenergyjobs.com by keyword, employer, location, sector, seniority, job type, remote and posted date. Battery storage has no sector of its own: search it with query. Returns 10 jobs per page, newest first (by the date the job was first seen), with a link and a slug for get_job. Pay shows when the listing has pay data; estimates are labeled. Not for jobs outside energy, resume writing or applying.

Input parameters:

- `company` (string): Employer name, e.g. "Fervo Energy". An unknown name returns 0 jobs and similar names. Wins over sector when both are set.
- `employment_type` (string)
- `experience_level` (string)
- `location` (string): One city, US state, or country, e.g. "Texas" or "Denver, CO". For a metro area use its main city (Bay Area -> San Francisco) or the state. No zip codes. Spell out non-US regions (Ontario, Canada).
- `page` (integer): Page number, 10 jobs per page.
- `posted_within` (string): Only jobs posted within the last 24 hours, 7, 30 or 90 days.
- `query` (string): Keywords, e.g. "electrical engineer" or "battery storage". Skip for browse-only searches.
- `remote` (boolean): true = jobs flagged remote in the listing.
- `sector` (string): Sector slug. Call list_sectors for what each one covers.
- `with_salary` (boolean): true = only jobs with pay data. Estimated pay is included and labeled "estimate".

Output parameters:

- `jobs` (array)
- `page` (number)
- `total` (number)
- `totalPages` (number)

### `get_job` (~102 tokens)

Get job details

Use this when the user wants the details of one job found with search_jobs: pay, location, job type, and the employer description. Takes the job slug or the full job URL. Returns facts, the employer-written text, and the link to read the full listing and apply. Not for searching. A job that closed returns a message saying so.

Input parameters:

- `job` (string, required): Job slug from search_jobs, or the full nextgenenergyjobs.com job URL.

### `list_sectors` (~60 tokens)

List sectors and filters

Use this when you need the valid sector, seniority, job type and posted-date values for search_jobs, or the user asks what kinds of energy jobs exist. Returns the four sectors with a short scope and live open-job counts. Cheap to call.

## Diagnostics

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

## Score history

- 2026-11-21: 84
- 2026-11-20: 84
- 2026-11-19: 83
- 2026-11-18: 83
- 2026-11-17: 82
- 2026-11-16: 82
- 2026-11-15: 82
- 2026-11-14: 81
- 2026-11-13: 81
- 2026-11-12: 80
- 2026-11-11: 80
- 2026-11-10: 79
- 2026-11-09: 79
- 2026-11-08: 78
- 2026-11-07: 78
- 2026-11-06: 77
- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 74
- 2026-10-29: 74

## Common questions

### What is the NextGen Energy Jobs MCP server?

NextGen Energy Jobs is an MCP server listed in the public MCP registry as com.nextgenenergyjobs/jobs. Search open jobs in grid, nuclear, renewables, storage and data centers. Read-only, no login. This page covers its hosted endpoint (https://www.nextgenenergyjobs.com/api/mcp).

### Is the NextGen Energy Jobs MCP server safe to use?

NextGen Energy Jobs 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 NextGen Energy Jobs MCP server expose?

NextGen Energy Jobs exposes 3 tools: search_jobs, get_job, list_sectors. Their descriptions and schemas cost roughly 533 tokens of context every time the server is loaded.

### Does the NextGen Energy Jobs MCP server require authentication?

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

### Is the NextGen Energy Jobs MCP server still maintained?

NextGen Energy Jobs 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 NextGen Energy Jobs MCP server?

VerifyMCP ran 13 checks on NextGen Energy Jobs, 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://www.nextgenenergyjobs.com/api/mcp
- Website: https://www.nextgenenergyjobs.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-nextgenenergyjobs-jobs/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nextgenenergyjobs-jobs/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-nextgenenergyjobs-jobs/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-nextgenenergyjobs-jobs/api-mcp
