JobSweep
Search 239k open jobs from 3,519 company career sites. Free tier; an API key raises limits.
The current version, v1.1.0, was published to the official MCP registry on 2026-11-14. It is distributed as a hosted remote over streamable-http, filed under Search by this index. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using JobSweep in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireVerdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands. The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-11-15).
Contracts can change after screening, with no version bump. The gate pins JobSweep’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
Server-scoped, not a tool: this is text the server supplies for clients to inject into an agent’s context on connect (instructions or prompt metadata). It sits outside every tool contract hash, so this observation is its only drift signal.
Observed by mcpindex’s crawler between daily registry snapshots - a contract diff, not a safety verdict, and not an in-path prevention (that is the gate). A “safety-relevant diff” touches a safety-relevant field; it is not a confirmed vulnerability. Shown at the server level; individual tools are not named. Absence is not a clean bill of health: only public-registry servers are crawled.
Search the Ankra documentation: clusters, stacks, GitOps, CI/CD and the CLI. No account needed.
Search and triage all your mailboxes; draft replies and campaigns; send only as you allow.
UI encyclopedia for agents — search Elements and fetch component specs over MCP (OAuth).