io.github.IsaiahDupree/jobstack-mcp
REMOTE · JOBSTACK-MCP.VERCEL.APP · SCANNED SEP 20
Unified jobs search over official feeds + ATS boards (USAJOBS, Adzuna, Muse, Greenhouse, Lever...)
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 527 tokens (~263/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the io.github.IsaiahDupree/jobstack-mcp server?
io.github.IsaiahDupree/jobstack-mcp is a hosted endpoint at https://jobstack-mcp.vercel.app/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 · jobstack-mcp.vercel.app
claude mcp add --transport http isaiahdupree-jobstack-mcp 'https://jobstack-mcp.vercel.app/mcp'
{
"mcpServers": {
"isaiahdupree-jobstack-mcp": {
"url": "https://jobstack-mcp.vercel.app/mcp"
}
}
} {
"servers": {
"isaiahdupree-jobstack-mcp": {
"type": "http",
"url": "https://jobstack-mcp.vercel.app/mcp"
}
}
} [mcp_servers.isaiahdupree-jobstack-mcp] url = "https://jobstack-mcp.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"isaiahdupree-jobstack-mcp": {
"type": "remote",
"url": "https://jobstack-mcp.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add isaiahdupree-jobstack-mcp --url 'https://jobstack-mcp.vercel.app/mcp' --transport streamable-http
mcp_servers:
isaiahdupree-jobstack-mcp:
url: "https://jobstack-mcp.vercel.app/mcp" {
"McpServers": {
"isaiahdupree-jobstack-mcp": {
"Transport": "http",
"Url": "https://jobstack-mcp.vercel.app/mcp"
}
}
} assistant mcp add isaiahdupree-jobstack-mcp -t streamable-http -u 'https://jobstack-mcp.vercel.app/mcp'
{
"mcpServers": {
"isaiahdupree-jobstack-mcp": {
"type": "http",
"url": "https://jobstack-mcp.vercel.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +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.
- 11 Aug 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
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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://jobstack-mcp.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jobstack-mcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobstack-mcp.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://jobstack-mcp.vercel.app/mcp | HTTPS enforced | 308 | https://jobstack-mcp.vercel.app/mcp |
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 →
get_job Get a single job by source + id ~185
Fetch one job posting by its source engine and native id, returned as { meta, job } with the same flat Job shape search_jobs yields. The id is the native upstream id as returned by that source in search results (NOT prefixed with the source name). Exception: for source="ats" the id is a composite "board:company:nativeId" string (e.g. "greenhouse:airbnb:7995153") so the lookup can round-trip to the right ATS board. Not every source supports single-job lookup — a search-only source returns a not_supported / not_found error.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Native upstream job id as returned by that source. For source="ats", the composite "board:company:nativeId" string. |
| source | string | yes | The engine that produced the job (matches the Job.source field from search_jobs). |
No output schema declared.
No examples provided.
search_jobs Search jobs (unified feed) ~342
Search job postings across every configured source and merge the results into one flat Job shape. Fans out in parallel to USAJOBS, Adzuna, Jooble, The Muse, Reed, and the ats engine (Greenhouse/Lever/Ashby/Workable/SmartRecruiters), then merges + sorts by postedDate (newest first) and paginates the combined set. Each Job has id, source, title, company, location, remote, url, description, postedDate, salaryMin, salaryMax, salaryCurrency, department, and employmentType. The response envelope carries meta, the echoed query, sources_requested, an optional sources_errored map, total, count, limit, offset, and results. Use sources= to restrict to specific engines.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | – | Free-text search terms (job title, skill, company, etc.). Optional — omit to browse the latest postings. |
| limit | integer | – | Max results in the merged page, clamped 1-100. Default 20. |
| location | string | – | Free-text location filter (e.g. "Washington, DC" or "London"). Applied upstream where the source supports it. |
| offset | integer | – | Zero-based offset into the merged result set for pagination. Default 0. |
| remote | boolean | – | Filter to remote roles when true. Only sources that expose an explicit remote signal apply it; others ignore it. |
| sources | string | – | Comma-separated engine keys to restrict the fan-out to. Any of: usajobs, adzuna, jooble, themuse, reed, ats. Omit for all six. |
No output schema declared.
No examples provided.
What is the io.github.IsaiahDupree/jobstack-mcp server?
io.github.IsaiahDupree/jobstack-mcp is listed in the public MCP registry as io.github.IsaiahDupree/jobstack-mcp. Unified jobs search over official feeds + ATS boards (USAJOBS, Adzuna, Muse, Greenhouse, Lever...). This page covers its hosted endpoint (https://jobstack-mcp.vercel.app/mcp).
Is the io.github.IsaiahDupree/jobstack-mcp server safe to use?
io.github.IsaiahDupree/jobstack-mcp scores 86 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 io.github.IsaiahDupree/jobstack-mcp server expose?
io.github.IsaiahDupree/jobstack-mcp exposes 2 tools: search_jobs, get_job. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Does the io.github.IsaiahDupree/jobstack-mcp server require authentication?
No. We connected to io.github.IsaiahDupree/jobstack-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.IsaiahDupree/jobstack-mcp server still maintained?
io.github.IsaiahDupree/jobstack-mcp 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.