Search / live.alpic.openjobs-3168f222/openjobs
Find jobs in your own words and apply on the company website — no detours.
v0.0.2 · active · website · descriptor JSON · versions
protogrid{
"mcpServers": {
"openjobs": {
"type": "http",
"url": "https://openjobs-3168f222.alpic.live"
}
}
}claude mcp add --transport http openjobs https://openjobs-3168f222.alpic.live[mcp_servers.openjobs]
url = "https://openjobs-3168f222.alpic.live"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"openjobs": {
"type": "remote",
"url": "https://openjobs-3168f222.alpic.live",
"enabled": true
}
}
}{
"mcpServers": {
"openjobs": {
"type": "http",
"url": "https://openjobs-3168f222.alpic.live"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=openjobs&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vb3BlbmpvYnMtMzE2OGYyMjIuYWxwaWMubGl2ZSJ9"
}{
"servers": {
"openjobs": {
"type": "http",
"url": "https://openjobs-3168f222.alpic.live"
}
}
}{
"mcpServers": {
"openjobs": {
"httpUrl": "https://openjobs-3168f222.alpic.live"
}
}
}extensions:
"openjobs":
enabled: true
name: "openjobs"
type: streamable_http
uri: "https://openjobs-3168f222.alpic.live"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations6 of 6 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_app_intro (idempotentHint); explain_filters (idempotentHint); explain_data_source (idempotentHint); …tools.token_costabout 2,676 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website -unreachable(5 failures) ~updated-133d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://openjobs-3168f222.alpic.live streamable-http | none | no (5 failures) | 77% | 273 ms | 2025-11-25 | 2026-10-12 |
explain_data_sourceread-only | 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. |
explain_filtersread-only | 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. |
get_app_introread-only | Friendly introduction to OpenJob for job seekers. Use when the user is new or asks how this works. Return plain language only. |
get_index_statusread-only | How much of the job board is loaded and whether search is ready. Explain to the user in simple terms, not technical sync jargon. |
get_job_detailsread-only | 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. |
search_jobsread-only | 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, seniority, locations, remote preference, title keywords, exclusions; (2) if missing both a role and a place, ask one short question; (3) run 2–4 search_jobs calls with varied strategies and search_mode resume_match; (4) for the best 5–10 results call get_job_details with their urls (batch up to 10) and search_mode resume_match; (5) dedupe, rank using description_text when status is ok, explain top picks in plain language with apply links; do not invent percentage match scores. For role families (founder/founder's/founders associate, chief of staff, product manager) pass the user's words in title — OpenJob normalizes spelling variants automatically; role_cluster is optional. hide_recruiters defaults true (skip recruiting agencies). |
Schemas: list_tools.
{
"name": "live.alpic.openjobs-3168f222/openjobs",
"icons": [
{
"src": "https://openjobs-3168f222.alpic.live/assets/icon.png",
"sizes": [
"200x200"
],
"mimeType": "image/png"
}
],
"title": "OpenJob",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://openjobs-3168f222.alpic.live",
"type": "streamable-http"
},
{
"url": "https://openjobs-3168f222.alpic.live",
"type": "sse"
}
],
"version": "0.0.2",
"websiteUrl": "https://openjobs-3168f222.alpic.live/try",
"description": "Find jobs in your own words and apply on the company website — no detours."
}