Home / MCP registry index / io.github.worklittle/jobs

Worklittle Jobs

io.github.worklittle/jobs in the official MCP registry. Endpoint https://mcp.worklittle.com/.

The registry describes it as: Find jobs near you. Search over 4 million openings by role, place, pay, visa and more.

We read its 23 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http jobs https://mcp.worklittle.com/

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "jobs": {
      "url": "https://mcp.worklittle.com/"
    }
  }
}

VS Code

code --add-mcp '{"name":"jobs","type":"http","url":"https://mcp.worklittle.com/"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_jobs search_companies get_job_details get_market_overview track_applied_job get_my_profile list_recent_chats mint_mcp_ui_embed_session logout_connected_account upload_my_resume get_my_resume delete_my_resume update_my_profile apply_for_job check_application_status submit_application stop_application steer_application save_about_me list_active_applications list_applications get_apply_settings update_apply_settings

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-worklittle-jobs/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-worklittle-jobs)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.