Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Worklittle Jobs

REMOTE · MCP.WORKLITTLE.COM

Find jobs near you and apply instantly. Search over 7.5 million listings by role, pay and visa.

−4 this week 66 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5803 tokens (~232/item across 25 items; 16 tools + 9 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 Management49
  • Stability check failed: schema churn in the 30 days we've observed: 10 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −5
    • A breaking change shipped without a version bump: still 3.0 ▼ security
    • Tool “delete_my_resume” was removed ▼ security
    • Tool “get_apply_settings” was removed ▼ security
    • Tool “get_my_resume” was removed ▼ security
    • Tool “save_about_me” was removed ▼ security
    • Tool “steer_application” was removed ▼ security
    • Tool “submit_application” was removed ▼ security
    • Tool “update_apply_settings” was removed ▼ security
    • Tool “upload_my_resume” was removed ▼ security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-387b0336fa.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs-387b0336fa → ui://widget/.html security
    • New tool “update_application”, which the server declares destructive security
    • Tool “apply_for_job” rewrote its description, which is the text the model reads security
    • Tool “get_my_profile” rewrote its description, which is the text the model reads security
    • Tool “list_applications” rewrote its description, which is the text the model reads security
    • Tool “update_my_profile” rewrote its description, which is the text the model reads security
    • Schema quality: 159 → 232 ▼ functional
    • Resource “Apply status” was removed ▼ functional
    • Resource “Job List” was removed ▼ functional
    • Destructive annotations: 100 → pass functional
    • New tool “create_cover_letter” functional
    • “list_applications” added an optional parameter “my_jobs” cosmetic
    • “list_applications” added an optional parameter “offset” cosmetic
    • “list_applications” added an optional parameter “session_id” cosmetic
    • “list_applications” added an optional parameter “stage” cosmetic
    • “search_jobs” added an optional parameter “applied” cosmetic
    • “update_my_profile” added an optional parameter “about_you” cosmetic
    • “update_my_profile” added an optional parameter “address” cosmetic
    • “update_my_profile” added an optional parameter “auto_apply” cosmetic
    • “update_my_profile” added an optional parameter “auto_submit” cosmetic
    • “update_my_profile” added an optional parameter “city” cosmetic
    • “update_my_profile” added an optional parameter “clear_fields” cosmetic
    • “update_my_profile” added an optional parameter “country” cosmetic
    • “update_my_profile” added an optional parameter “current_company” cosmetic
    • “update_my_profile” added an optional parameter “current_title” cosmetic
    • “update_my_profile” added an optional parameter “degree” cosmetic
    • “update_my_profile” added an optional parameter “delete_resume” cosmetic
    • “update_my_profile” added an optional parameter “desired_role” cosmetic
    • “update_my_profile” added an optional parameter “facebook” cosmetic
    • “update_my_profile” added an optional parameter “github” cosmetic
    • “update_my_profile” added an optional parameter “huggingface” cosmetic
    • “update_my_profile” added an optional parameter “instagram” cosmetic
    • “update_my_profile” added an optional parameter “linkedin” cosmetic
    • “update_my_profile” added an optional parameter “name” cosmetic
    • “update_my_profile” added an optional parameter “resume_file” cosmetic
    • “update_my_profile” added an optional parameter “school” cosmetic
    • “update_my_profile” added an optional parameter “state” cosmetic
    • “update_my_profile” added an optional parameter “tailor_resume” cosmetic
    • “update_my_profile” added an optional parameter “tiktok” cosmetic
    • “update_my_profile” added an optional parameter “website” cosmetic
    • “update_my_profile” added an optional parameter “work_authorization” cosmetic
    • “update_my_profile” added an optional parameter “x” cosmetic
    • “update_my_profile” added an optional parameter “youtube” cosmetic
    • “list_applications” reworded the description of “limit” cosmetic
    • “search_jobs” reworded the description of “exclude_remote” cosmetic
    • “search_jobs” reworded the description of “limit” cosmetic
    • “update_my_profile” reworded the description of “drivers_license” cosmetic
    • “update_my_profile” dropped the optional parameter “company_name” cosmetic
    • “update_my_profile” dropped the optional parameter “facebook_url” cosmetic
    • “update_my_profile” dropped the optional parameter “github_url” cosmetic
    • “update_my_profile” dropped the optional parameter “home_address” cosmetic
    • “update_my_profile” dropped the optional parameter “huggingface_url” cosmetic
    • “update_my_profile” dropped the optional parameter “instagram_url” cosmetic
    • “update_my_profile” dropped the optional parameter “job_title” cosmetic
    • “update_my_profile” dropped the optional parameter “linkedin_url” cosmetic
    • “update_my_profile” dropped the optional parameter “location_city” cosmetic
    • “update_my_profile” dropped the optional parameter “location_country” cosmetic
    • “update_my_profile” dropped the optional parameter “location_state” cosmetic
    • “update_my_profile” dropped the optional parameter “personal_website_url” cosmetic
    • “update_my_profile” dropped the optional parameter “phone_country_iso” cosmetic
    • “update_my_profile” dropped the optional parameter “phone_national” cosmetic
    • “update_my_profile” dropped the optional parameter “profile_clear_fields” cosmetic
    • “update_my_profile” dropped the optional parameter “school_degree” cosmetic
    • “update_my_profile” dropped the optional parameter “tiktok_url” cosmetic
    • “update_my_profile” dropped the optional parameter “work_authorization_countries” cosmetic
    • “update_my_profile” dropped the optional parameter “x_url” cosmetic
    • “update_my_profile” dropped the optional parameter “you_interests” cosmetic
    • “update_my_profile” dropped the optional parameter “you_name” cosmetic
    • “update_my_profile” dropped the optional parameter “you_school” cosmetic
    • “update_my_profile” dropped the optional parameter “you_work” cosmetic
    • “update_my_profile” dropped the optional parameter “youtube_url” cosmetic
  • 20 Nov 26 +1
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-f17926753c.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs-f17926753c → ui://widget/.html security
    • “apply_for_job” added an optional parameter “url” cosmetic
    • “apply_for_job” added an optional parameter “urls” cosmetic
  • 19 Nov 26 0
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-6bfc2b57fe.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
    • Tool “apply_for_job” rewrote its description, which is the text the model reads security
    • Tool “search_jobs” rewrote its description, which is the text the model reads security
    • “apply_for_job” reworded the description of “auto_submit” cosmetic
  • 18 Nov 26 0
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-7659aca026.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
    • “search_jobs” reworded the description of “exclude_remote” cosmetic
  • 17 Nov 26 0
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-0287747f6c.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
  • 16 Nov 26 0
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-eb81344146.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
    • New tool “create_resume”, which the server declares destructive security
    • Tool “apply_for_job” rewrote its description, which is the text the model reads security
  • 15 Nov 26 0
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-bc6647b246.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
  • 14 Nov 26 0
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-map-e9d3f3654b.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-deck.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-ui.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs-native.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://widget/jobs.html → ui://widget/.html security
    • Resource “Jobs” now points somewhere else: ui://worklittle/jobs.html → ui://widget/.html security
Diagnostics

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 21 Nov 2026 · Probed https://mcp.worklittle.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=worklittle.com CN=WE1,O=Google Trust Services,C=US 21 Nov 2026 19 Feb 2027 ECDSA 256 ECDSA-SHA256 ac24af54133b319e0e31f8b49d002a78
SANs: worklittle.com, mcp.worklittle.com, *.mcp.worklittle.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.worklittle.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
worklittle.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.worklittle.com/ Verified 200
http (plaintext) http://mcp.worklittle.com/ Served over HTTP 200
MCP tools · 16 exposed · ~5,431 tokens

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 →

Tool Tokens
add_applied_job ~145

Jobs — Add a job to the user's applied jobs (Applied and Saved on worklittle.com) at a status such as saved or applied. To move a job already there, use update_applied_job.

NameTypeReqDescription
apply_urlstring–Optional employer apply URL.
company_namestringyes–
job_idstringyesWorklittle job id from search_jobs or get_job_details.
job_titlestringyes–
methodstring–How the user applied. Defaults to apply.
statusstring–Pipeline stage when known. Use saved for heart/save. Defaults to in_progress for apply / apply_with_ai, applied for api.

Structured output declared, but exposes no named fields.

No examples provided.

apply_for_job ~763

Jobs — Apply to jobs for the user: Worklittle fills out and submits each application. Pass job_id from search_jobs, or job_ids (up to 10) when they want to apply to several or all of them at once. Worklittle-hosted postings work the same way: their form is filled from the user's profile. It submits by default; pass auto_submit false when the user wants to review first, then show them the answers from list_applications with the session_id and send it with update_application (action submit) only after they say so. If it answers RESUME_REQUIRED or resume_warning, the user has no résumé saved: save the one they attach with update_my_profile (resume_file), or write one with create_resume and save_to_profile true, and apply again.

NameTypeReqDescription
applicantobject–With use_profile false: the person applying. name and email are required; phone, city, state, country, work_authorization, needs_sponsorship, desired_salary, about_you are recommended. Send their res…
applicant_idstring–With use_profile false: the person from an earlier apply. Store it permanently with the person and reuse it; it works with any Worklittle API key. It is also emailed to them; if lost, ask them for it.
auto_submitboolean–Default: the user's auto_submit setting (on unless they turned it off), which submits when the form is complete. false: stop at review (status awaiting_submit) so the user can check every answer; sen…
cover_letter_htmlstring–Optional cover letter HTML to seed.
job_idstring–Worklittle job id from search_jobs / get_job_details.
job_idsarray–Apply to up to 10 jobs in one call (instead of job_id), all for the same person and with the same options. Returns one result per job.
max_per_companyinteger–Applications to one company per 30 days for this person. Defaults to their apply setting (3). Raise it only after the person agrees, when a start returned COMPANY_LIMIT_REACHED.
resume_htmlstring–Optional resume HTML to seed.
resume_idstring–Use this one of the user's saved resumes. Leave out to let Worklittle pick the best one for the job.
resume_pdf_base64string–With use_profile false: the applicant's resume PDF, base64.
resume_textstring–With use_profile false: the applicant's resume as plain text.
tailor_resumeboolean–Default from apply settings (on): write a resume tailored to this job. false: send the resume as is.
testboolean–true: a free practice run. Nothing opens, nothing is stored or sent to an employer, no personal information needed. The session moves queued → running → completed over ~25 seconds.
urlstring–Instead of job_id: a link to the job posting (the employer's job page or application page), when the user pastes one. Worklittle finds the job, or adds it if it isn't listed, and applies; the result…
urlsarray–Like job_ids, for job posting links (can be combined with job_ids, up to 10 jobs in all). Each result includes its url and job_id.
use_profileboolean–Default true: apply as the signed-in user with their profile. false: apply as the applicant described below (another person, no Worklittle account needed).

Structured output declared, but exposes no named fields.

No examples provided.

check_application_status ~52

Jobs — Check an application Worklittle is filling out: its status, which form fields are filled, and a live view link. Only the status completed means it was submitted.

NameTypeReqDescription
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

create_cover_letter ~151

Jobs — Create a hiring-manager-ready one-page cover letter (no placeholders). Same formats/format options as create_resume (default html+pdf). $0.01 per cover letter, charged only when returned.

NameTypeReqDescription
companystring––
draftboolean–true: a draft that keeps [ ] gaps for missing facts instead of failing on thin input. Same price.
formatstring–html | pdf | docx
formatsarray––
instructionsstring––
job_contextobject––
job_idstring––
profileobject––
resume_textstring––
rolestring––

Structured output declared, but exposes no named fields.

No examples provided.

create_resume ~272

Jobs — Write a one-page resume for the user from what they tell you (work history, skills, education) or their saved profile, fitted to a job when job_id is given. Never invent facts. When details are thin, pass draft true and fill the [ ] gaps with them. When it is their new or updated main resume, pass save_to_profile true to save it to their profile in the same call (ask first; it replaces the current main resume). Costs $0.01.

NameTypeReqDescription
draftboolean–true: a draft that keeps [ ] gaps for missing facts instead of failing on thin input. Same price. Can't be saved.
formatstring–html | pdf | docx. pdf/docx also include html. Prefer formats[] when requesting multiple.
formatsarray–Subset of html, pdf, docx. Default when omitted: html and pdf.
instructionsstring––
job_contextobject––
job_idstring––
profileobject––
resume_textstring–What the user told you or their old resume, as plain text.
save_to_profileboolean–true: save the finished PDF as the user's main resume, so applications send it. Not with draft.

Structured output declared, but exposes no named fields.

No examples provided.

create_sign_in_link ~35

Jobs — Create a one-time link that opens worklittle.com signed in as the user (used by the app's buttons).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_job_details ~138

Jobs — Fetch detailed information about a specific job, including full responsibilities, qualifications, and company details. Pass job_id from search_jobs when you have one. If the user asks for full details of a role without an id (e.g. the first software engineer job in Austin), pass query and optional location instead — the tool loads the first matching live listing.

NameTypeReqDescription
job_idstring–The job ID from a previous search_jobs result when available.
locationstring–Optional location substring when resolving details by query.
querystring–Role/title search used when job_id is missing (picks the first live match).
NameTypeReqDescription
company_namestring––
descriptionstring––
idstring––
locationstring––
titlestring––
urlstring––

No examples provided.

get_market_overview ~141

Jobs — Returns aggregate job-market statistics from Worklittle. Call with no args for the whole market (workplace and job-type mix, top hiring companies). When the user names a role and/or city (e.g. product managers in San Francisco), pass query and location. The filtered slice includes match count, top companies in the sample, and salary signals from listings that publish pay.

NameTypeReqDescription
locationstring–Location substring for a market slice (e.g. San Francisco).
querystring–Role or title filter for a market slice (e.g. product manager).
workplace_typestring–Optional workplace filter for the slice.
NameTypeReqDescription
top_hiring_companiesarray––

No examples provided.

get_my_profile ~156

Jobs — Get everything Worklittle knows about the user, with the same field names update_my_profile takes: name, contact details, city/state/country, address, current_title and current_company, desired_role, desired_salary, work_authorization, needs_sponsorship, school, degree, languages, links, experience and education (work history), about_you (the More about you text used on every application), the main resume (status ready, processing or missing, and its text when ready) and apply_settings (auto_apply, auto_submit, tailor_resume, max_per_company: most applications to one company in any 30 days). A field never filled in is null. If they have not linked their account it returns connected false.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_applications ~346

Jobs — List the user's applications, newest first: ones Worklittle is filling out now (status active, with session_id), pending ones (matched by auto-apply or waiting for approval) and finished ones (completed = submitted; stopped = the person ended it; cancelled = ended before anything was filled in; failed = went wrong on our side). Check it before applying so the same job is never applied to twice. Filter with status, days (7 = the last week), job_id or applicant_id; when next_offset is set, call again with that offset. session_id: one application in detail instead (status, the answers filled in, a live view link; only completed means it was submitted). my_jobs true: the user's own Saved and Applied list on worklittle.com instead (jobs they saved or marked applied, including ones applied to elsewhere), filtered by stage.

NameTypeReqDescription
applicant_idstring–"me" for the user's own, or an applicant id (required on a shared API key)
daysnumber–Only applications started or updated in the last this many days (7 = last week, 30 = last month).
job_idstring––
limitnumber–Max rows to return (default 50, max 200).
my_jobsboolean–true: list the user's Saved and Applied list instead.
offsetnumber–Rows to skip: pass next_offset from the previous call to get the next page.
session_idstring–Show this one application in detail.
stagestring–With my_jobs: only jobs at this stage.
statusstring––

Structured output declared, but exposes no named fields.

No examples provided.

logout_connected_account ~22

Jobs — Sign the user out of Worklittle in this app.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

search_companies ~166

Jobs — Search the Worklittle market company index by name or slug (ranked typeahead). Returns id, name, slug, logo_url, and enrichment fields for employers with open jobs. Use when the user names an employer and you need a real slug/id for search_jobs company= filters, job alerts, or automations. If zero hits, try alternate spellings or related employer names from further search_companies calls — do not invent company ids or slugs. If still empty, tell the user that employer is not in the index yet and offer any close matches you found.

NameTypeReqDescription
limitnumber–Max results to return. Default 5, max 20.
qstringyesCompany name or slug query (min 2 characters, max 80).

Structured output declared, but exposes no named fields.

No examples provided.

search_jobs ~2,110

Jobs — Shows Worklittle job cards for a place and an optional role. The cards scroll endlessly: jobs near the place first, then farther away. Send the place and the role as SEPARATE fields. Never write 'product manager in San Francisco' as one query. PLACE: always pass near_lat + near_lng (the city's coordinates, which you know) and location as the display name (e.g. 'San Francisco, CA'). radius_km 25-50 for a city. If the user names no place, omit all place fields; the cards start at the user's approximate (IP-based) area. When a search runs short, results continue with close matches (search.scope related: same role and place with seniority, salary, job type and date filters dropped), then the rest of the country and worldwide (search.scope country or world), so say which cards are exact matches and where the roles are. ROLE: query holds only the job title text (e.g. 'product manager') and may be omitted for 'any job'. Search Worklittle job listings. People say Worklittle plus a role, city, company, or filters (or just 'jobs') — they will not name this tool. Call it whenever they want Worklittle jobs. Search by keyword, company, location, job type, seniority, or recency. Use for ANY industry (retail, finance, healthcare, tech, etc.). Search matches title and filter text (substring / FTS), not vector embeddings. Role / title text goes in query (+ optional keywords). The API matches job TITLE substrings only for that text — it does not mix company names into the same field. Preserve negative title terms with a leading dash, e.g. 'software engineer, -senior' excludes titles containing senior. Use company for employer slugs (include or exclude). Never concatenate many job titles into one query unless the user supplied comma-separated roles. Do not add seniority_level, stacks, or resume-derived terms unless they asked. Omit seniority_level unless they explicitly name a level as an inclusion filter (never infer from profile). Expand abbreviations only; umbrella phrases…

NameTypeReqDescription
appliedboolean–Filter by whether the user already applied. false: leave out jobs they applied to. true: only jobs they applied to. Omit to get every job; ones they applied to say applied: true.
companystring–Employer slug(s): bare slug or comma-separated OR include (e.g. meta,google,apple). Prefix with '-' to exclude (e.g. -lucid-motors,-tesla). Mix allowed (meta,google,-amazon). Lowercase hyphenated. Mi…
countrystring–ISO 3166-1 alpha-2 country filter (e.g. US, GB, DE). Returns jobs in that country or workplace_type remote.
cursorstring–Pagination cursor from a previous search_jobs response to fetch the next page.
description_languagestring–ISO 639-1 code for the language of the job posting body. Examples: en, es, de, fr, pt.
employment_typestring–Type of employment contract.
exclude_idsstring–Comma-separated job IDs to exclude (e.g. postings already shown in the conversation).
exclude_remoteboolean–Distance searches (near_lat/near_lng) return on-site and hybrid jobs in the radius. For remote jobs, search without near_lat/near_lng and set remote: true.
keywordsstring–Only if the user named skills or stacks in this turn. Omit by default — do not pull from resume or profile.
limitnumber–Number of results to return, at most 8 per call. Pass cursor from the response for more.
locationstring–Display name of the place (e.g. 'San Francisco, CA'). When near_lat/near_lng are set this is only a label and is NOT used as a text filter. Otherwise a text filter on job location strings (partial ma…
location_orstring–Comma-separated place substrings when the user names two or more metros at once (e.g. San Francisco,New York). The API returns jobs whose location text matches ANY term. Mutually exclusive with dista…
near_latnumber–Latitude for distance search. Use with near_lng. Typical source: browser geolocation or geocoded city.
near_lngnumber–Longitude for distance search. Required with near_lat.
posted_within_daysnumber–Days of posted-date lookback, at most 30. Omit → default 7. 0 → the full 30 days. 1 → today/last 24h. 7 → this week. Jobs older than 30 days are never returned. Never encode recency words in query.
querystring–Job title or role phrase (merged with keywords). Sent as API title= — matches job TITLE text only, separate from company. Preserve negative title terms with a leading dash, e.g. 'product manager, sof…
radius_kmnumber–Radius in kilometers around near_lat/near_lng. Default 50, max 500.
remoteboolean–true: remote jobs only (any country unless country is set). Leave out place fields. location 'remote' does the same.
seniority_levelstring–Omit unless the user explicitly asked for a band. Never infer from profile. Enum when set:
visa_sponsorshipstring–Filter by explicit visa sponsorship text in the posting (AI-extracted). Use 'yes' for jobs that sponsor visas (H-1B, etc.). Use 'no' only when the user wants roles that explicitly state no sponsorshi…
NameTypeReqDescription
cursorstring|null–Pagination cursor for the next page.
jobsarray–Matching job listings.
locationstring––
near_latnumber––
near_lngnumber––
querystring––
searchobject–Echo of search_jobs filters for the Job Cards widget.
totalnumber–Total matches when provided by the API.

No examples provided.

stop_application ~66

Jobs — Stop an application that Worklittle is filling out for the user. This cancels the application in progress and it cannot be resumed; the user would have to start it again. Needs the session_id from apply_for_job or list_applications.

NameTypeReqDescription
session_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

update_application ~239

Jobs — Change one of the user's applications. action submit: send an application waiting for review (status awaiting_submit), only after the user has seen its answers (list_applications with session_id) and said to send it. action steer: change what an application in progress fills in, without stopping it; pass their wish as instructions with their exact facts ("say my notice period is one month"), never adding facts. action stop: stop an application Worklittle is filling out; it cannot be resumed. These three need session_id from apply_for_job or list_applications. action move: put a job at a stage in the user's Saved and Applied list (saved, applied, interview, offer, rejected, withdrawn); action remove: take it off that list. These two need job_id.

NameTypeReqDescription
actionstringyes–
instructionsstring–For steer: what to change, in plain words.
job_idstring–For move and remove: the Worklittle job id.
session_idstring–For submit, steer and stop.
stagestring–For move: the stage to put the job at.

Structured output declared, but exposes no named fields.

No examples provided.

update_my_profile ~629

Jobs — Change anything on the user's Worklittle profile in one call; send only what changes, using the field names get_my_profile returns (name, phone, city, current_title, desired_role, desired_salary, work_authorization, needs_sponsorship, experience, education, links, …). experience and education replace the whole list. about_you: the More about you text Worklittle uses on every future application; it replaces the old text, so read get_my_profile first and merge, in the user's words, never inventing facts. clear_fields: names of fields to empty. resume_file: the resume the user attached in the chat, saved as their main resume (replaces it; other saved resumes stay). delete_resume true deletes the main resume. auto_apply, auto_submit and tailor_resume change how Worklittle applies for them.

NameTypeReqDescription
about_youstring–The More about you text Worklittle uses on every future application (standing answers like notice period, relocation, referrals). Replaces the old text: read get_my_profile first and merge, in the us…
addressstring–Home street address
auto_applyboolean–Worklittle applies to jobs that match the user on its own.
auto_submitboolean–Send applications without stopping for the user's review first.
citystring––
clear_fieldsarray–Field names to empty, e.g. ["address"]
countrystring––
current_companystring–Current employer(s), most recent first
current_titlestring–Current job title(s), most recent first
degreestring––
delete_resumeboolean–true: delete the user's main resume.
desired_rolestring–The roles they want, comma-separated
desired_salarystring–e.g. "$90,000+" or "$25+/hour"
drivers_licensestring–valid | none
educationarray–Replaces education. Months as YYYY-MM.
experiencearray–Replaces work history. Months as YYYY-MM; omit end for the current job.
facebookstring––
githubstring––
huggingfacestring––
instagramstring––
languagesarray––
linkedinstring––
namestring––
needs_sponsorshipboolean–true if they need visa sponsorship to work
phonestring––
resume_fileobject–The resume file the user attached in the chat.
schoolstring––
statestring––
tailor_resumeboolean–Tailor the user's resume to each job it applies to.
tiktokstring––
websitestring––
work_authorizationarray–ISO2 country codes they can work in
xstring––
years_experiencenumber––
youtubestring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Worklittle Jobs MCP server?

Worklittle Jobs is a hosted endpoint at https://mcp.worklittle.com/, 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 · mcp.worklittle.com

# add to Claude Code
claude mcp add --transport http worklittle-jobs 'https://mcp.worklittle.com/'
Common questions

What is the Worklittle Jobs MCP server?

Worklittle Jobs is an MCP server listed in the public MCP registry as io.github.worklittle/jobs. Find jobs near you and apply instantly. Search over 7.5 million listings by role, pay and visa. This page covers its hosted endpoint (https://mcp.worklittle.com/).

Is the Worklittle Jobs MCP server safe to use?

Worklittle Jobs scores 66 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 Worklittle Jobs MCP server expose?

Worklittle Jobs exposes 16 tools: search_jobs, search_companies, get_job_details, create_resume, create_cover_letter, and 11 more. Their descriptions and schemas cost roughly 5,431 tokens of context every time the server is loaded.

Does the Worklittle Jobs MCP server require authentication?

No. We connected to Worklittle Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Worklittle Jobs MCP server still maintained?

Worklittle Jobs is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Worklittle Jobs MCP server?

VerifyMCP ran 14 checks on Worklittle Jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.