Home / MCP registry index / io.github.work0r-ai/workorai

Workorai

io.github.work0r-ai/workorai in the official MCP registry. Endpoint https://workorai.com/mcp. Source: github.com/work0r-ai/agent-kit.

The registry describes it as: WorkorAI talent marketplace MCP: candidate job search and employer hiring with explainable matching

We read its 29 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules.

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 workorai https://workorai.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "workorai": {
      "url": "https://workorai.com/mcp"
    }
  }
}

VS Code

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

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

request_access candidate.search_jobs candidate.get_job candidate.get_applications candidate.set_saved_job candidate.get_saved_jobs candidate.accept_invitation candidate.decline_invitation candidate.withdraw_application candidate.apply_to_job employer.list_jobs employer.get_job employer.create_job employer.update_job employer.publish_job employer.close_job employer.archive_job employer.delete_job employer.search_candidates_for_job employer.search_candidates_by_query employer.get_candidate employer.get_candidate_evidence employer.invite_candidate employer.list_applicants employer.set_review_status employer.get_applicant_detail employer.get_applicant_transcript employer.list_invitations employer.cancel_invitation

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-work0r-ai-workorai/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-work0r-ai-workorai)

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.