Skip to content

workorai MCP server

io.github.work0r-ai/workoraiwork0r-aistreamable-httpv0.4.3Scanned

WorkorAI talent marketplace MCP: candidate job search and employer hiring with explainable matching

29 tools: 3 can delete or cancel things, 3 do something that can't be undone, 9 change things and 14 only read.

Tools: 3 delete, 3 irreversible, 9 write, 14 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things and 3 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the workorai MCP server can do

The workorai MCP server is published by the GitHub account work0r-ai. It has 29 tools. It can delete or cancel things (3 tools: employer.archive_job, employer.delete_job and employer.cancel_invitation), do things that cannot be undone, such as sending, paying or publishing (candidate.withdraw_application, employer.publish_job and employer.invite_candidate) and create or change data (9 tools: request_access, candidate.set_saved_job, candidate.accept_invitation, candidate.decline_invitation and 5 more). 14 tools only read.

2 tools can send data out of your system (employer.publish_job and employer.invite_candidate).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.4.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

29 tools

Deletes or cancels 3Claude Code: deny
  • employer.archive_jobTransition a CLOSED job to ARCHIVED.No findings

    Why it is in this group

    • The name "employer.archive_job" says "archive": a word for removing or ending something.
    Description, as the server wrote it
    Transition a CLOSED job to ARCHIVED. Returns NOT_FOUND for missing or non-owner jobs and CONFLICT when the job is not in CLOSED.
  • employer.cancel_invitationCancel a pending invitation sent to a candidate.No findings

    Why it is in this group

    • The name "employer.cancel_invitation" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel a pending invitation sent to a candidate. The invitation record is deleted; the employer can re-invite the same candidate later.
  • employer.delete_jobPermanently delete a DRAFT job that was never published.No findings

    Why it is in this group

    • The name "employer.delete_job" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    Description, as the server wrote it
    Permanently delete a DRAFT job that was never published. Returns NOT_FOUND for missing or non-owner jobs and CONFLICT when the job is not in DRAFT.
Can't be undone 3Claude Code: ask
  • candidate.withdraw_applicationWithdraw the candidate's active application to a job (APPLIED -> WITHDRAWN).No findings

    Why it is in this group

    • The name "candidate.withdraw_application" says "withdraw": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Withdraw the candidate's active application to a job (APPLIED -> WITHDRAWN). Idempotent (withdrawing again succeeds). Returns NOT_APPLIED when there is no active application (e.g. only an open invitation, or already declined), and NOT_FOUND when no application exists for the job.
  • employer.invite_candidateInvite a discoverable candidate to one of the employer's PUBLISHED jobs.Can send data outNo findings

    Why it is in this group

    • The name "employer.invite_candidate" says "invite": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "employer.invite_candidate" says "invite": it sends or publishes something to other people.
    Description, as the server wrote it
    Invite a discoverable candidate to one of the employer's PUBLISHED jobs. Creates a JobApplication with status=INVITED. If a prior WITHDRAWN row exists for this (candidate, job) pair, the row is UPDATEd back to INVITED (re-invite is allowed after the candidate withdrew on their own). INVITED, APPLIED, and DECLINED rows still block with INVITE_BLOCKED: INVITE_NOT_ALLOWED. Inspect `existingApplications` on employer.get_candidate before calling to know which case applies. Returns INVITE_BLOCKED with one of several sub-reasons (JOB_NOT_FOUND, JOB_NOT_PUBLISHED, CANDIDATE_NOT_FOUND, NOT_DISCOVERABLE, INVITE_NOT_ALLOWED) when the invite cannot be created. A missing vacancy and a vacancy owned by another employer both return JOB_NOT_FOUND (you cannot tell them apart — anti-enumeration).
  • employer.publish_jobTransition a DRAFT job to PUBLISHED.Can send data outNo findings

    Why it is in this group

    • The name "employer.publish_job" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "employer.publish_job" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Transition a DRAFT job to PUBLISHED. Returns NOT_FOUND for missing or non-owner jobs and CONFLICT when the job is not in DRAFT.
Changes things 9Claude Code: ask
  • candidate.accept_invitationAccept an employer's invitation to a job (INVITED -> APPLIED).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Accept an employer's invitation to a job (INVITED -> APPLIED). Idempotent — accepting an already-accepted invite succeeds. Returns NOT_INVITED when there is no open invitation (e.g. already withdrawn/declined), and NOT_FOUND when the job/invite is not found or the job is no longer public.
  • candidate.apply_to_jobApply the candidate to a PUBLISHED job, reusing their evaluated profile interview as evidence.No findings

    Why it is in this group

    • The name "candidate.apply_to_job" says "apply": a word for a change.
    Description, as the server wrote it
    Apply the candidate to a PUBLISHED job, reusing their evaluated profile interview as evidence. Idempotent (re-applying succeeds; `reused` is true when an application row already existed). Requires a completed + evaluated interview — otherwise returns GATE_LOCKED / GATE_EVALUATING / GATE_FAILED. A missing or non-public job returns NOT_FOUND.
  • candidate.decline_invitationDecline an employer's invitation to a job (INVITED -> DECLINED).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Decline an employer's invitation to a job (INVITED -> DECLINED). TERMINAL — a declined invite blocks any re-invite from the employer, so only decline when the candidate is sure. Idempotent (declining again succeeds). Returns NOT_INVITED when there is no open invitation, NOT_FOUND when the job/invite is not found.
  • candidate.set_saved_jobSet whether a PUBLISHED job is in the candidate's saved list (idempotent desired-state, NOT a toggle — pass saved:true to bookmark, saved:false to remove).No findings

    Why it is in this group

    • The name "candidate.set_saved_job" says "set": a word for a change.
    Description, as the server wrote it
    Set whether a PUBLISHED job is in the candidate's saved list (idempotent desired-state, NOT a toggle — pass saved:true to bookmark, saved:false to remove). Returns NOT_FOUND for a missing or non-public job.
  • employer.close_jobTransition a PUBLISHED job to CLOSED.No findings

    Why it is in this group

    • The name "employer.close_job" says "close": a word for a change.
    Description, as the server wrote it
    Transition a PUBLISHED job to CLOSED. Returns NOT_FOUND for missing or non-owner jobs and CONFLICT when the job is not in PUBLISHED.
  • employer.create_jobParse raw text via Gemini AI and create a DRAFT job under the current employer.No findings

    Why it is in this group

    • The name "employer.create_job" says "create": a word for a change.
    Description, as the server wrote it
    Parse raw text via Gemini AI and create a DRAFT job under the current employer. Synchronous: latency 5-30s. The agent can then call employer.update_job to refine fields and employer.publish_job to make it live.
  • employer.set_review_statusUpdate the employer review state on an application (NEW / REVIEWING / SHORTLISTED / REJECTED / HIRED).No findings

    Why it is in this group

    • The name "employer.set_review_status" says "set": a word for a change.
    Description, as the server wrote it
    Update the employer review state on an application (NEW / REVIEWING / SHORTLISTED / REJECTED / HIRED). SHORTLISTED and HIRED unlock the candidate's direct contact in subsequent list_applicants / get_applicant_detail calls. WITHDRAWN applications surface as CONFLICT.
  • employer.update_jobUpdate the fields of an existing employer job.No findings

    Why it is in this group

    • The name "employer.update_job" says "update": a word for a change.
    Description, as the server wrote it
    Update the fields of an existing employer job. Accepts a partial whitelist; rawInput and dataSource are not editable (the wrapper auto-flips dataSource to USER_EDITED on every agent update). Non-owner reads return NOT_FOUND.
  • request_accessUse when someone wants to find work/jobs (candidate) or hire/find candidates (employer) but the authenticated role tools are not usable yet.No findings

    Why it is in this group

    • The name "request_access" says "request": a word for a change.
    Description, as the server wrote it
    Use when someone wants to find work/jobs (candidate) or hire/find candidates (employer) but the authenticated role tools are not usable yet. Explains role-specific onboarding (candidate profile interview, employer key generation), MCP key location, and next steps for both surfaces.
Only reads 14Show 14 read-only tools
  • candidate.get_applicationsList the candidate's own job applications (newest first) with status, dates, the originating interview score, and a job summary.No findings

    Why it is in this group

    • The name "candidate.get_applications" says "get": a word for reading.
    Description, as the server wrote it
    List the candidate's own job applications (newest first) with status, dates, the originating interview score, and a job summary. Returns only the caller's applications — no jobId input, so it is not an enumeration surface.
  • candidate.get_jobFetch a single published job by id.No findings

    Why it is in this group

    • The name "candidate.get_job" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single published job by id.
  • candidate.get_saved_jobsList the candidate's saved (bookmarked) jobs, newest first.No findings

    Why it is in this group

    • The name "candidate.get_saved_jobs" says "get": a word for reading.
    Description, as the server wrote it
    List the candidate's saved (bookmarked) jobs, newest first. Only currently PUBLISHED jobs are returned — a job saved earlier then closed/archived is omitted.
  • candidate.search_jobsSemantically rank published jobs against the authenticated candidate profile (embedding-based fit).No findings

    Why it is in this group

    • The name "candidate.search_jobs" says "search": a word for reading.
    Description, as the server wrote it
    Semantically rank published jobs against the authenticated candidate profile (embedding-based fit). Optional tier (best|good|weak) narrows to a match-quality band — start with tier:'best' for the strongest fits and cascade only if needed; omit for the full ranked list (read tierCounts for the band sizes). Each scored row carries matchExplanation (the white-box 'why': fit score, the candidate's skills that match the job's required set, and a rationale). A free-text `q`, or a candidate who has not completed an interview yet, instead browses published jobs by recency — those rows carry NO fit score (`matchScore` is `null`, no bands); treat them as a browse list, not a ranking.
  • employer.get_applicant_detailFull applicant bundle: resume, interview light slice (overallScore + summary + facts), GitHub analysis, LinkedIn analysis.No findings

    Why it is in this group

    • The name "employer.get_applicant_detail" says "get": a word for reading.
    Description, as the server wrote it
    Full applicant bundle: resume, interview light slice (overallScore + summary + facts), GitHub analysis, LinkedIn analysis. The verbatim transcript is delivered by employer.get_applicant_transcript; the resume's contact fields are blanked unless the application is SHORTLISTED or HIRED.
  • employer.get_applicant_transcriptVerbatim interview transcript for one applicant.No findings

    Why it is in this group

    • The name "employer.get_applicant_transcript" says "get": a word for reading.
    Description, as the server wrote it
    Verbatim interview transcript for one applicant. Ownership-only gate (same as the UI Download button — no SHORTLISTED/HIRED requirement). Returns an empty array when the source interview never produced turns.
  • employer.get_candidateFetch a discoverable candidate by user id.No findings

    Why it is in this group

    • The name "employer.get_candidate" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a discoverable candidate by user id. Returns search-entry shape plus a light interview slice (overallScore + summary + completedAt + evaluatedAt) and `existingApplications`: every JobApplication this candidate has on any of the employer's jobs (all 4 statuses, all 4 job statuses) so the agent can decide whether re-inviting will succeed. Heavy artefacts (transcript, facts, resume, github, linkedin) live behind employer.get_applicant_detail and require an application.
  • employer.get_candidate_evidenceFetch the interview EVIDENCE (facts proven in the interview + their Q&A, the interview summary, the résumé summary, and GitHub/LinkedIn signals) for ONE candidate AGAINST one of yo…No findings

    Why it is in this group

    • The name "employer.get_candidate_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the interview EVIDENCE (facts proven in the interview + their Q&A, the interview summary, the résumé summary, and GitHub/LinkedIn signals) for ONE candidate AGAINST one of your published jobs — the white-box basis to explain WHY a candidate ranks where they do. Use it AFTER search_candidates_for_job: shortlist with the scorecard, then read the evidence here for the few you care about and write your own comparative review. Returns NOT_FOUND if the job is missing / not yours / not published, or the candidate is not in that job's searchable pool.
  • employer.get_jobFetch a single employer job record by id.No findings

    Why it is in this group

    • The name "employer.get_job" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single employer job record by id. Returns NOT_FOUND for missing jobs and for jobs owned by another employer (no existence leak).
  • employer.list_applicantsList the live (APPLIED) applicants on one of the employer's jobs.No findings

    Why it is in this group

    • The name "employer.list_applicants" says "list": a word for reading.
    Description, as the server wrote it
    List the live (APPLIED) applicants on one of the employer's jobs. The candidate showcase + interview overallScore/summary are always returned; contact fields are only included when the application is SHORTLISTED or HIRED.
  • employer.list_invitationsList the pending (INVITED) candidates on one of the employer's jobs — candidates who have been invited but have not yet accepted or declined.No findings

    Why it is in this group

    • The name "employer.list_invitations" says "list": a word for reading.
    Description, as the server wrote it
    List the pending (INVITED) candidates on one of the employer's jobs — candidates who have been invited but have not yet accepted or declined.
  • employer.list_jobsList jobs owned by the current employer account.No findings

    Why it is in this group

    • The name "employer.list_jobs" says "list": a word for reading.
    Description, as the server wrote it
    List jobs owned by the current employer account.
  • employer.search_candidates_by_queryFree-form semantic search across discoverable (interviewed) candidates with no job context.No findings

    Why it is in this group

    • The name "employer.search_candidates_by_query" says "search": a word for reading.
    Description, as the server wrote it
    Free-form semantic search across discoverable (interviewed) candidates with no job context. The query is embedded and candidates are ranked by semantic similarity — a preliminary search with no per-vacancy fit score (there is no vacancy to fit). For a scored ranking, use employer.search_candidates_for_job with a job id.
  • employer.search_candidates_for_jobSemantically rank discoverable (interviewed) candidates against one of the employer's own jobs, with a per-candidate fit score AND a white-box explanation.No findings

    Why it is in this group

    • The name "employer.search_candidates_for_job" says "search": a word for reading.
    Description, as the server wrote it
    Semantically rank discoverable (interviewed) candidates against one of the employer's own jobs, with a per-candidate fit score AND a white-box explanation. WORKFLOW for finding the best hire: 1) call with tier:'best' to get the strongest candidates (cover the required skills + proven in interview), cascade to tier:'good' then tier:'weak' only if you need more (read tierCounts to decide; paginate within a band via page.hasMore, not page.total); 2) each row carries matchExplanation — the white-box 'why' (the fit score, the skills the candidate PROVED in their interview, what they're missing, and a plain-English rationale) — use it to explain your shortlist on OUR data, not a black box; 3) for the few you shortlist, call employer.get_candidate_evidence(jobId, userId) for the interview facts + Q&A to write a deeper comparative review. Omit tier for the full ranked pool (back-compat). Returns NOT_FOUND when the job is missing / owned by another employer (no existence leak), or NOT_INDEXED / NO_CATEGORIES when the job is not indexed for semantic search yet (re-save / republish, then retry).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
15
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 15 tools that change things (3 destructive, 3 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://workorai.com/mcp: tools/list returned 29 tools to an anonymous client, including employer.archive_job (destructive), employer.delete_job (destructive), employer.cancel_invitation (destructive), candidate.withdraw_application (irreversible), employer.publish_job (irreversible) and 10 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.4.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http workorai https://workorai.com/mcp
claude mcp add --transport http workorai https://workorai.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__workorai__candidate_search_jobs",
      "mcp__workorai__candidate_get_job",
      "mcp__workorai__candidate_get_applications",
      "mcp__workorai__candidate_get_saved_jobs",
      "mcp__workorai__employer_list_jobs",
      "mcp__workorai__employer_get_job",
      "mcp__workorai__employer_search_candidates_for_job",
      "mcp__workorai__employer_search_candidates_by_query",
      "mcp__workorai__employer_get_candidate",
      "mcp__workorai__employer_get_candidate_evidence",
      "mcp__workorai__employer_list_applicants",
      "mcp__workorai__employer_get_applicant_detail",
      "mcp__workorai__employer_get_applicant_transcript",
      "mcp__workorai__employer_list_invitations"
    ],
    "ask": [
      "mcp__workorai__request_access",
      "mcp__workorai__candidate_set_saved_job",
      "mcp__workorai__candidate_accept_invitation",
      "mcp__workorai__candidate_decline_invitation",
      "mcp__workorai__candidate_withdraw_application",
      "mcp__workorai__candidate_apply_to_job",
      "mcp__workorai__employer_create_job",
      "mcp__workorai__employer_update_job",
      "mcp__workorai__employer_publish_job",
      "mcp__workorai__employer_close_job",
      "mcp__workorai__employer_invite_candidate",
      "mcp__workorai__employer_set_review_status"
    ],
    "deny": [
      "mcp__workorai__employer_archive_job",
      "mcp__workorai__employer_delete_job",
      "mcp__workorai__employer_cancel_invitation"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as workorai. Review it before you use it.

Capability tags behind 2 rules
  • mcp__workorai__employer_publish_job outbound
  • mcp__workorai__employer_invite_candidate outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.work0r-ai/workorai/verify?hash=167d796a66e98f48b3fbc6a9411f54b573349575baf7a0714a806e7c89a5e359" | jq -e '.changed == false'

Pinned hash 167d796a66e9, from Nov 20, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.work0r-ai/workorai/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.work0r-ai/workorai
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.work0r-ai/workorai.svg)](https://radar.anlyon.com/servers/io.github.work0r-ai/workorai)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.

workorai MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the workorai MCP server safe?

No scan can promise that. What its definitions show: 29 tools, 15 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the workorai MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: employer.archive_job, employer.delete_job and employer.cancel_invitation.

Can the workorai MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: candidate.withdraw_application, employer.publish_job and employer.invite_candidate.

What tools does the workorai MCP server have?

29 tools: 3 destructive, 3 irreversible, 9 write, 14 read. employer.archive_job, employer.delete_job, employer.cancel_invitation, candidate.withdraw_application, employer.publish_job, employer.invite_candidate, request_access, candidate.set_saved_job and 21 more.

Does the workorai MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the workorai MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): employer.publish_job and employer.invite_candidate.

Has the workorai MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.