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.

JobsPipe

REMOTE · JOBSPIPE.DEV · 2 COMPONENTS · SCANNED SEP 20

Live job postings from 30+ ATS feeds and job boards, one schema. Live results need a Bearer key.

Available components

remote · jobspipe.dev 82 remote · mcp.jobspipe.dev 40
0 this week 82 Trust /100
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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation 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. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1388 tokens (~198/item across 7 items; 4 tools + 3 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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
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 6 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
Install

How do I install the JobsPipe MCP server?

JobsPipe is a hosted endpoint at https://jobspipe.dev/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 · jobspipe.dev

# add to Claude Code
claude mcp add --transport http dev-jobspipe-mcp 'https://jobspipe.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-jobspipe-mcp": {
      "url": "https://jobspipe.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-jobspipe-mcp": {
      "type": "http",
      "url": "https://jobspipe.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-jobspipe-mcp]
url = "https://jobspipe.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-jobspipe-mcp": {
      "type": "remote",
      "url": "https://jobspipe.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-jobspipe-mcp --url 'https://jobspipe.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-jobspipe-mcp:
    url: "https://jobspipe.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-jobspipe-mcp": {
      "Transport": "http",
      "Url": "https://jobspipe.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-jobspipe-mcp -t streamable-http -u 'https://jobspipe.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-jobspipe-mcp": {
      "type": "http",
      "url": "https://jobspipe.dev/mcp"
    }
  }
}

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

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.

  • 17 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: good → excellent functional
    • “search_jobs” added an optional parameter “language_not” cosmetic
    • “search_jobs” added an optional parameter “language_or” cosmetic
  • 16 Sept 26 0
    • “search_jobs” added an optional parameter “city_or” cosmetic
    • “search_jobs” reworded the description of “job_location_or” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 6 Sept 26 −1
    • “list_pricing_plans” reworded the description of “plan” cosmetic
    • “search_jobs” reworded the description of “job_location_or” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 5 Sept 26 0
    • “search_jobs” added an optional parameter “include_unlabeled_employment_type” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 4 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: excellent → good functional
  • 30 Aug 26 −1
    • Schema quality: 115 → 153 ▼ functional
    • “search_jobs” added an optional parameter “esco_skill_id_or” cosmetic
    • “search_jobs” added an optional parameter “has_recruiter_email” cosmetic
    • “search_jobs” added an optional parameter “max_applicant_count” cosmetic
    • “search_jobs” added an optional parameter “max_ghost_score” cosmetic
    • “search_jobs” added an optional parameter “metro_code_or” cosmetic
    • “search_jobs” added an optional parameter “min_salary_usd” cosmetic
    • “search_jobs” added an optional parameter “visa_sponsorship_or” cosmetic
    • “search_jobs” added an optional parameter “benefits_or” cosmetic
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Probed https://jobspipe.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jobspipe.dev CN=YR1,O=Let's Encrypt,C=US 4 Sept 2026 3 Dec 2026 RSA 2048 SHA256-RSA 5a2b4d72b5189a80a6b2019b9b9cb87e71d
SANs: api.jobspipe.dev, docs.jobspipe.dev, jobspipe.dev, mcp.jobspipe.dev, www.jobspipe.dev
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 secure

Validation of jobspipe.dev. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
jobspipe.dev. present 2371 13 Verified
jobspipe.dev. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jobspipe.dev/mcp Verified 200
http (plaintext) http://jobspipe.dev/mcp HTTPS enforced 308 https://jobspipe.dev/mcp
MCP tools · 4 exposed · ~1,165 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
list_job_sources ~57

List the ATS and job-board sources JobsPipe normalizes into a single JSON schema, with coverage and freshness notes.

NameTypeReqDescription
name_containsstring–Optional case-insensitive substring to filter sources by name (e.g. "workday").

No output schema declared.

No examples provided.

list_pricing_plans ~53

List JobsPipe pricing plans with monthly price in USD, monthly job quota and included features.

NameTypeReqDescription
planstring–Optional plan name to return just one plan (e.g. "free", "credits").

No output schema declared.

No examples provided.

search_jobs ~980

Search live, normalized job postings across 30+ sources by title, skill/tech, country, remote, seniority, employment type and recency. Returns guidance for calling the authenticated REST API that runs the query.

NameTypeReqDescription
benefits_orarray–Match jobs advertising any of these benefit slugs, e.g. 401k, health insurance. Coverage is partial.
city_orarray–Whole city names, e.g. London, Munich. Case-insensitive; a metro wrapper on the stored value is ignored. Spellings and diacritics are normalised for cities we know (München finds Munich, Cracow finds…
description_orarray–Match any of these skills or technologies in the posting.
employment_type_orarray–Match any of these employment types.
esco_skill_id_orarray–Match jobs tagged with any of these ESCO skill concept IDs (exact match).
has_recruiter_emailboolean–true for only jobs with a recruiter contact email parsed from the posting, false for only jobs without one.
include_unlabeled_employment_typeboolean–Also return jobs whose employment type is unknown. About 27% of postings do not state one, and employment_type_or excludes every one of them by default.
isic_division_orarray–ISIC Rev.4 employer industry divisions (2-digit, e.g. 62).
job_country_code_orarray–Match any of these ISO 3166-1 alpha-2 country codes.
job_location_orarray–Match any of these cities or regions, e.g. Seattle, WA. Metro wrappers are stripped (Greater London also matches London) and a state, province or UK nation by name matches every spelling of it (Penns…
job_seniority_orarray–Match any of these seniority levels.
job_title_orarrayyesMatch any of these job titles.
language_notarray–Exclude postings written in these languages, as lowercase ISO 639-1 codes, e.g. ["fr"]. Unlabelled postings are kept.
language_orarray–Languages the posting is written in, as lowercase ISO 639-1 codes, e.g. ["en"]. The language of the posting text, not the country: 18.3% of Swedish postings and 17.7% of German ones are in English. U…
limitnumber–Maximum rows to return.
max_applicant_countnumber–Only jobs with at most this many applicants. Counts exist only where the source exposes them (LinkedIn), so this also drops every job without a count.
max_ghost_scorenumber–Exclude jobs whose ghost-likelihood score (0-100) exceeds this. Unscored jobs always pass.
metro_code_orarray–Match any of these US CBSA metro codes, e.g. 35620 for New York. Non-US jobs never match.
min_salary_usdnumber–Only jobs whose posted salary reaches this annual USD amount. Jobs without a posted salary never match; estimated salaries are not consulted.
occupation_code_orarray–ISCO-08 occupation codes; 4-digit exact, 1-3 digit as hierarchy prefix.
posted_at_max_age_daysnumber–Only postings published within this many days.
region_orarray–US states and Canadian provinces as ISO 3166-2 codes, e.g. US-NY, CA-ON. Matches every spelling a job board publishes, so CA-ON finds both ON and Ontario. More precise than job_location_or for a stat…
remoteboolean–Only remote roles when true.
skills_orarray–Match jobs tagged with any of these skill slugs, e.g. python, kubernetes.
visa_sponsorship_orarray–Match any of these visa stances parsed from the posting text: offers, no, citizenship_required. Jobs that say nothing never match.
work_arrangement_orarray–Match any of remote, hybrid or onsite. Finer than remote, which answers false for hybrid and onsite alike. Jobs whose arrangement is unknown never match, and coverage is still backfilling, so this re…

No output schema declared.

No examples provided.

search_upwork_jobs ~75

Search live Upwork job postings ingested by JobsPipe. Returns normalized rows with budget, skills and client signals.

NameTypeReqDescription
limitnumber–Maximum rows to return (1-200, default 25).
offsetnumber–Pagination offset.
orderstring––
sortstring––

No output schema declared.

No examples provided.

Common questions

What is the JobsPipe MCP server?

JobsPipe is an MCP server listed in the public MCP registry as dev.jobspipe/mcp. Live job postings from 30+ ATS feeds and job boards, one schema. Live results need a Bearer key. This page covers its hosted endpoint (https://jobspipe.dev/mcp).

Is the JobsPipe MCP server safe to use?

JobsPipe scores 82 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 JobsPipe MCP server expose?

JobsPipe exposes 4 tools: search_jobs, list_job_sources, list_pricing_plans, search_upwork_jobs. Their descriptions and schemas cost roughly 1,165 tokens of context every time the server is loaded.

Does the JobsPipe MCP server require authentication?

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

Is the JobsPipe MCP server still maintained?

JobsPipe is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.