OpenJob

live.alpic.openjobs-3168f222Published by openjobs-3168f222.alpic.liveOfficial publisherv0.0.2Updated Nov 1, 2026

Find jobs in your own words and apply on the company website — no detours.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant search for job openings from a natural-language description and point the user to the company's own application page.

What you can do
This remote MCP server is described as letting a user find jobs in their own words and then apply on the company website, without detours. The registry description is the only available detail: no tool list, README, or documentation is provided, so the exact search parameters, result fields, and coverage are not shown. It appears to be a job-search and job-listing lookup service rather than a general web tool.
When to use it
Worth considering when someone wants an assistant to help find job openings from a plain-language description of what they are looking for, and to be sent to the employer's own page to apply. Less useful if you need application tracking, resume management, or verified listings, since none of that is documented here.
Requirements
Runs as a remote streamable HTTP endpoint at the provider's hosted address; no local package or runtime is needed. The manifest declares no authentication, no environment variables, and no headers, so nothing appears to be required to connect. Network access to the provider's endpoint is needed.
Before you install
No credentials, payments, or write actions are declared, and the description says applications happen on the company website rather than through the server. Because no tool list or documentation is available, what data the server receives and returns cannot be verified; treat job listings as unverified and confirm details on the employer's own site before applying.

Installation

In SourceWeft

  1. Open OpenJob in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/live.alpic.openjobs-3168f222%2Fopenjobs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "openjob": {
      "type": "http",
      "url": "https://openjobs-3168f222.alpic.live/"
    }
  }
}

Tools

6

get_app_intro

About OpenJob

Friendly introduction to OpenJob for job seekers. Use when the user is new or asks how this works. Return plain language only.

Takes no parameters.

explain_filters

Search tips

Plain-language search tips for job seekers. Use when the user asks how to search or what they can filter. No technical jargon in the reply.

Takes no parameters.

explain_data_source

About the job data

Where job listings come from, licensing, and links to the data provider. Use only when the user asks about data source, Feashliaa, license, attribution, or who built OpenJob.

Takes no parameters.

get_index_status

Job board status

How much of the job board is loaded and whether search is ready. Explain to the user in simple terms, not technical sync jargon.

Takes no parameters.

search_jobs

Search jobs

Search open company job listings. Map the user's natural language to filters. Always set search_mode on search_jobs and get_job_details: keyword_search when the user only describes a role, place, or filters; resume_match when they upload a resume/CV or ask to match jobs to their background or memory. Never show parameter names (role_cluster, skill_level, search_mode, etc.) to the user — speak like a career coach. Do not mention data sources or licenses unless the user asks — use explain_data_source for that. Every job has url and apply_url (company careers page). When you list jobs in a table, bullets, or prose, each row must include at least one clickable markdown link to that url — e.g. linked title [Title](url), linked company name, or a separate Apply / View posting link. Never list a job with no way to click through. After search_jobs, add a structured follow-up in the user's language — the widget shows cards; your text adds coaching. Include: (1) a markdown table Role | Company | Fit (use resume/memory when available; otherwise one-line highlight per row); (2) a numbered priority list for applying (top 3–5 with brief rationale); (3) if the user shared background, one CV positioning sentence they can reuse; (4) related title search variants as inline tags (e.g. Entrepreneur in Residence, Venture Development, GTM Associate, Chief of Staff). When the user has a resume or detailed background, call get_job_details on the best 5–8 urls before ranking. Do not invent match percentages. search_jobs live-checks up to 8 Greenhouse/Ashby/Lever listings per search and drops roles confirmed closed on the company site. For deeper advice on a shortlist, call get_job_details on the best urls (batch up to 10) to load full posting text. Use verifiable_only=true when the user wants only listings we can double-check live (~30% of the board). When the user uploads a resume (curriculum vitae) or asks to match jobs to their background (or ChatGPT memory): (1) extract target titles, s

Parametersatslimittitlecompanylocationmin_salaryremote_onlysearch_moderequiredskill_leveluser_intentverify_liverole_cluster+4 more

get_job_details

Job posting details

Fetch full posting text for job urls from search_jobs. Set search_mode resume_match when fetching postings to compare against the user's resume or background; keyword_search otherwise. Greenhouse (including embedded careers pages), Ashby, and Lever are supported; other career sites may return unsupported_ats. Closed roles are cached about 24 hours; open postings about 14 days (posting text only, not user resumes). Use description_text to compare against the user's resume or stated background.

Parametersurlurlssearch_modeuser_intent

Version history

1
  1. v0.0.2LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.