_ registry / mcp http-sse · checked 57m ago

nextgenenergyjobs

https://www.nextgenenergyjobs.com

Registry code: bfa89821858ecd4f

api record

nextgenenergyjobs.com lists open jobs in the modern power sector: grid, nuclear, renewables and data-center power. Coverage is mostly US and updated daily. Battery storage has no sector of its own: search it with query.

Tools: list_sectors (valid filter values and live counts), search_jobs (find openings, 10 per page), get_job (details for one job by slug or URL).

endpoint
https://www.nextgenenergyjobs.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is nextgenenergyjobs live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is nextgenenergyjobs free to use?
Yes — the hub reached it with no key and no payment.
What tools does nextgenenergyjobs have?
3 tools: get_job, list_sectors, search_jobs.
Is nextgenenergyjobs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
489ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_sectors open 57m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • search_jobs open 57m ago

    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, most recently updated first, 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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "default": 1,
          "maximum": 50,
          "minimum": 1,
          "description": "Page number, 10 jobs per page."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Keywords, e.g. \"electrical engineer\" or \"battery storage\". Skip for browse-only searches."
        },
        "remote": {
          "type": "boolean",
          "description": "true = jobs flagged remote in the listing."
        },
        "sector": {
          "enum": [
            "data-centers",
            "grid",
            "nuclear",
            "renewables"
          ],
          "type": "string",
          "description": "Sector slug. Call list_sectors for what each one covers."
        },
        "company": {
          "type": "string",
          "maxLength": 100,
          "description": "Employer name, e.g. \"Fervo Energy\". An unknown name returns 0 jobs and similar names. Wins over sector when both are set."
        },
        "location": {
          "type": "string",
          "maxLength": 100,
          "description": "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)."
        },
        "with_salary": {
          "type": "boolean",
          "description": "true = only jobs with pay data. Estimated pay is included and labeled \"estimate\"."
        },
        "posted_within": {
          "enum": [
            "24h",
            "7d",
            "30d",
            "90d"
          ],
          "type": "string",
          "description": "Only jobs posted within the last 24 hours, 7, 30 or 90 days."
        },
        "employment_type": {
          "enum": [
            "full_time",
            "part_time",
            "contract",
            "internship"
          ],
          "type": "string"
        },
        "experience_level": {
          "enum": [
            "entry",
            "mid",
            "senior",
            "executive"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 75 lines
  • get_job unknown 57m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "job"
      ],
      "properties": {
        "job": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "Job slug from search_jobs, or the full nextgenenergyjobs.com job URL."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bfa89821858ecd4f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bfa89821858ecd4f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bfa89821858ecd4f/badge.svg)](https://brick.blue/agent/bfa89821858ecd4f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.