JobScout MCP

JobScout MCP

A privacy-first, bring-your-own-connections MCP server for multi-source job discovery. JobScout gives AI agents one normalized pool with provenance, deterministic deduplication, and specialist AI/Web3 signals.

JobScout deliberately stops at trustworthy discovery. It does not store CVs, rank candidates, contact employers, or apply to jobs.

Why JobScout

• Search enabled providers without making one source the whole market.
• Keep discovery provenance separate from canonical employer application routes.
• Continue with partial results when an individual provider fails.
• Enforce remote and freshness filters after provider retrieval.
• Classify AI, agentic and Web3 signals locally and deterministically.
• Keep candidate identity and career policy in a private client such as Career OS.

MCP tools

Tool	Purpose	Network
jobscout_list_sources	Show configured providers, transports and coverage	No
jobscout_search_jobs	Search, normalize, filter and deduplicate enabled sources	Provider-dependent
jobscout_classify_jobs	Detect AI, agentic and Web3 signals in supplied jobs	No
jobscout_deduplicate	Normalize and merge supplied JobScout records	No
jobscout_briefing	Project records into briefing-ready entries with a compact one_line and best link	No

Two MCP prompts guide first-run use without the server storing anything: jobscout_setup walks through enabling providers and what each one contacts; jobscout_find_jobs gathers role, location and remote preference per search. A search run with zero enabled providers returns setup_required: true with guidance instead of a misleading empty result, and results report providers_disabled, records_rejected and undated_records so thin results are always explained.

Quick start

Node.js 22.13 or newer is required.

npm exec --yes --package=@sarutobi-sasuke/jobscout-mcp -- jobscout-mcp

Codex example with the public Himalayas adapter enabled:

codex mcp add jobscout --env JOBSCOUT_ENABLE_HIMALAYAS=true -- npm exec --yes --package=@sarutobi-sasuke/jobscout-mcp -- jobscout-mcp

MCP hosts can also run the package straight from GitHub, which is useful for pinning to a commit or testing an unreleased branch:

npm exec --yes --package=github:SarutobiSasuke8/jobscout-mcp -- jobscout-mcp

See installation for Claude Desktop, Cursor, local development, JobSpy, and troubleshooting.

Providers

Providers are disabled by default and failures are isolated.

Provider	Transport	Authentication	Notes
Himalayas	Remote MCP	Optional	Public job search; employer route should still be verified
JobSpy	Local Python subprocess	None	Optional python-jobspy; availability and site terms vary

The provider contract supports future official ATS and specialist job-board adapters without coupling the core to any one vendor. See provider documentation.

AI and Web3 intelligence

Every normalized job can include deterministic signals covering AI agents, inference, evals, safety, Web3 protocols, DeFi, DePIN, wallets, exchanges, developer infrastructure, gaming, and agentic commerce. Technology detection currently includes MCP, A2A, x402, LLMs, RAG, Ethereum, Base, and Solana.

These are inspectable discovery signals, not opaque candidate scores. See job intelligence.

Optional agent operating guide

agents/jobscout-operator.md gives an MCP-capable agent a safe, reusable discovery workflow and output contract. It is intentionally one functional operator—not a bundled fictional team—and contains no private candidate profile or Career OS policy.

Trust and safety

• Provider responses are untrusted and schema-validated.
• Only HTTP(S) job URLs are accepted.
• Remote and subprocess outputs have explicit size and time limits.
• JobSpy is spawned without a shell and receives typed JSON over stdin.
• No auto-apply, login automation, CAPTCHA bypass, credential capture, or proxy evasion.
• Users remain responsible for provider terms, job freshness, location eligibility, and employer-route verification.

Read SECURITY.md before enabling third-party providers.

Development

npm install
cp .env.example .env
npm run check
npm run smoke:mcp

The protocol smoke test uses the official MCP Inspector. Provider contributions must include fixtures, failure behavior, provenance handling, and tests; see CONTRIBUTING.md.

Release status

Live on npm as @sarutobi-sasuke/jobscout-mcp and on the official MCP Registry as io.github.SarutobiSasuke8/jobscout-mcp. Releases are tagged vX.Y.Z on GitHub; CI publishes to npm with provenance.

Prior art and licence

JobSpy is used as an optional MIT-licensed dependency rather than copied. borgius/jobspy-mcp-server demonstrated demand for a JobSpy MCP wrapper; no source from it is copied here.

JobScout MCP is Apache-2.0 licensed. Third-party dependencies retain their own licences.