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.

NextJobz Job Search

REMOTE · MCP.NEXTJOBZ.COM.BD

Search jobs on NextJobz by keyword, location, work type, salary, and experience level.

−5 this week 73 Trust /100

Last scanned (18 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 Security46
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 287 tokens (~287/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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 (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement.

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 −5
    • HTTPS: pass → unverified ▼ security
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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://mcp.nextjobz.com.bd/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.nextjobz.com.bd CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US 3 Oct 2026 19 Apr 2027 RSA 2048 SHA256-RSA 3149707c2a50c4381ca4e011d8001d51
SANs: *.nextjobz.com.bd, nextjobz.com.bd
CN=SSL.com TLS Issuing RSA CA R1,O=SSL Corporation,C=US (CA) CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US 21 Oct 2022 18 Oct 2032 RSA 3072 SHA256-RSA 26b9ffe4596fa61e1af21c63d672748a
CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US (CA) CN=SecureTrust CA,O=SecureTrust Corporation,C=US 17 Dec 2025 30 Dec 2029 RSA 4096 SHA256-RSA 7eb4274fc1d305be94c9883277f8467e2144f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nextjobz.com.bd. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
bd. DS published 7807 8 Verified
com.bd. DS published 15103 13 Verified
nextjobz.com.bd. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nextjobz.com.bd/mcp Verified 200
http (plaintext) http://mcp.nextjobz.com.bd/mcp Inconclusive 400
MCP tools · 1 exposed · ~287 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
search_jobs ~287

Search for jobs on NextJobz job portal. Returns paginated job listings with title, company, location, salary, skills, and deadline.

NameTypeReqDescription
companyNamestring|null–Filter by company name
contractboolean|null–Include contract jobs
fromSalarynumber|null–Minimum salary
fullTimeboolean|null–Include full-time jobs
hybridboolean|null–Include hybrid jobs
internshipboolean|null–Include internship jobs
jobLocationstring|null–Filter by job location (city or country)
maxExperienceinteger|null–Maximum years of experience required
minExperienceinteger|null–Minimum years of experience required
onSiteboolean|null–Include on-site jobs
pageNointeger–Page number (1-based)
pageSizeinteger–Results per page (max 20)
partTimeboolean|null–Include part-time jobs
postedFilterinteger|null–Filter by post date: 0=Last24Hours, 1=LastWeek, 2=LastMonth, 3=Last3Months
remoteboolean|null–Include remote jobs
searchstring|null–Job title or company keyword to search. Default searches all jobs.
toSalarynumber|null–Maximum salary

No output schema declared.

No examples provided.

Install

How do I install the NextJobz Job Search MCP server?

NextJobz Job Search is a hosted endpoint at https://mcp.nextjobz.com.bd/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 · mcp.nextjobz.com.bd

# add to Claude Code
claude mcp add --transport http ahmed-suman-nextjobz-job-search 'https://mcp.nextjobz.com.bd/mcp'
Common questions

What is the NextJobz Job Search MCP server?

NextJobz Job Search is an MCP server listed in the public MCP registry as io.github.ahmed-suman/nextjobz-job-search. Search jobs on NextJobz by keyword, location, work type, salary, and experience level. This page covers its hosted endpoint (https://mcp.nextjobz.com.bd/mcp).

Is the NextJobz Job Search MCP server safe to use?

NextJobz Job Search 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 NextJobz Job Search MCP server expose?

NextJobz Job Search exposes 1 tool: search_jobs. Their descriptions and schemas cost roughly 287 tokens of context every time the server is loaded.

Does the NextJobz Job Search MCP server require authentication?

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

Is the NextJobz Job Search MCP server still maintained?

NextJobz Job Search 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 NextJobz Job Search MCP server?

VerifyMCP ran 11 checks on NextJobz Job Search, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about NextJobz Job Search: Authorization and HTTPS. 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.