Skip to content

Quest: Hire a Human MCP server

quest.hireahuman/questhireahuman.queststreamable-httpv1.1.0Scanned

Hire a verified local human for small real-world tasks your AI agent can't do.

11 tools: 1 do something that can't be undone, 4 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 4 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 7
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 Quest: Hire a Human MCP server can do

The Quest: Hire a Human MCP server is published by hireahuman.quest, a domain the MCP Registry verified. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (replyToQuestComment) and create or change data (4 tools: postQuest, getQuestOffer, hireHuman and getHireStatus), but cannot delete data. 6 tools only read.

1 tool reads private data (getQuestComments); 7 tools bring in text other people can write (getQuestsV2, getQuestComments, replyToQuestComment and 4 more); 2 tools can send data out of your system (replyToQuestComment and postQuest). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.1.0.

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.

11 tools

Can't be undone 1Claude Code: ask
  • replyToQuestCommentReplies, as the quest's poster, to a question a human has asked on a quest you posted.Reads text others writeCan send data outNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "replyToQuestComment" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Replies, as the quest's poster, to a question a human has asked on a quest you posted. Works for both kinds of thread getQuestComments returns: the public question threads (your reply is posted as an answer) and the follow-up threads on offers (your reply is posted as a follow-up question to the human who made the offer). Pass the commentID of any comment in the thread, from getQuestComments, and your reply text. The thread is worked out for you. Only the account that posted the quest can reply; a quest that is deleted or restricted no longer accepts replies. Real people read this: the human is notified by push and email, and everyone who can see the quest sees your reply. Confirm the wording with the person you act for before sending, unless they told you to answer on their behalf. Keep it on the platform: replies that share phone numbers, WhatsApp, Telegram or other ways to continue off Quest are removed by moderation. Returns { commentID, questID, threadID, type, status } where status is one of: posted, flagged-for-review (posted, but queued for a moderator to check), or removed (taken down by moderation; do not retry the same text). Each call posts a new reply.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 4Claude Code: ask
  • getHireStatusShows where a hire started with hireHuman stands: whether the person you act for has paid the link, and once they have, whether the human has confirmed.Reads text others write1 finding

    Why it is in this group

    • The name "getHireStatus" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "getHireStatus" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "getHireStatus" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Shows where a hire started with hireHuman stands: whether the person you act for has paid the link, and once they have, whether the human has confirmed. Pass the hireID from hireHuman, or the offer's proposalID to get the latest hire on that offer. status is one of: awaiting-payment (not paid yet; paymentURL is the link to hand over again), processing-payment (paid, being processed - check again shortly), hire-requested (paid; hireRequest.status is awaiting-human-confirmation, hired, declined or expired, and confirmBy is the human's deadline), refunded (paid, but the hire could no longer happen - reason says why; the money was released), link-expired or link-failed (call hireHuman again for a new link). If the payment has just been made, this call also completes the hire, so it is safe to call right after the person says they have paid. Only the quest's poster can see a hire. Returns the same fields as hireHuman, plus paidAt, reason and hireRequest.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • getQuestOfferReturns one offer on your quest in full, for deciding between offers - take the proposalID from getQuestOffers.Reads text others write1 finding

    Why it is in this group

    • The name "getQuestOffer" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "getQuestOffer" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "getQuestOffer" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Returns one offer on your quest in full, for deciding between offers - take the proposalID from getQuestOffers. Only the quest's poster can use it; anyone else gets not found. Returns { proposalID, questID, status, sentAt, price, fees: { connectionFee, processingFee }, currency, availability, screeningAnswers: [{ question, answer }], requirementsAnswer: { requirement, answer } or null, portfolioLink, supportingImages (URLs), portfolioProjects: [{ title, description, images }], confirmationDeadline, declinedBy, human: { name (first name and last initial), about, averageRating, reviewCount, questsCompleted, questsCancelled, phoneVerified, emailVerified, preferredBadge, country, skills }, recentReviews: [{ questTitle, rating, text, sentAt }] (the human's five latest), humanNotified }. price and fees are in whole currency units, as postQuest takes price; status is as in getQuestOffers. The first time an offer is viewed - by you or in the app - the human is notified that your user's AI agent viewed it, and humanNotified says whether this call sent that. Viewing it again does not notify again.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • hireHumanStarts hiring the human behind one offer on a quest you posted - take the proposalID from getQuestOffers.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Starts hiring the human behind one offer on a quest you posted - take the proposalID from getQuestOffers. Hiring needs a payment, which you cannot make: this returns a secure Stripe payment link (paymentURL) for the person you act for. Give them the link and the amountDue, and let them pay it themselves - never open, fill in or pay it for them. Nothing happens until they pay: then the money is held by Quest (not paid to the human until the work is done), and the human is asked to confirm within confirmWithinMinutes. If the human declines or does not confirm in time, or the hire can no longer happen when the payment arrives (quest closed, slots full, offer withdrawn or changed), the payment is released back automatically. The link lasts about a day. Calling again for the same offer returns the same live link (reused: true) rather than making a second one. Follow progress with getHireStatus. Only the quest's poster can hire; the quest must be open and have a slot free. Returns { hireID, status: awaiting-payment, paymentURL, linkExpiresAt, amountDue: { offerPrice, connectionFee, processingFee, total, currency }, confirmWithinMinutes, human: { name }, questTitle, reused }. Amounts are in whole currency units, as in getQuestOffers.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • postQuestHires a human for real-world work: posts a paid task (a "quest") that humans can make offers on and complete.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "postQuest" says "post": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "postQuest" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Hires a human for real-world work: posts a paid task (a "quest") that humans can make offers on and complete. Built for physical presence - errands (queue, collect, deliver, handle paperwork, show up on someone's behalf), in-person checks (check stock, verify a place, mystery-shop), on-site photos, and event or booth help. Use this whenever the user wants to hire someone to do something in person, not just when they say "quest" explicitly. The caller is always the customer posting the quest - the poster ID and countryCode are resolved from the authenticated context, never from tool input. Returns { status, questID } where status is one of: pending (posted, awaiting vetting/matching), duplicate, user-banned, illegal-content, auto-delete, admin-delete, or maximum price exceeded. On maximum price exceeded, the response also includes { maxPrice, currency } - the actual ceiling for this caller - retry once with a lower price instead of guessing. When status is pending the response also includes a notice: Quest notifies the Customer in the app when a human asks a question or makes an offer. Tell the user this, and that they can ask you to review offers anytime.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • getMyQuestsLists the quests the account behind the API key has posted (paid real-world tasks), newest first, ten per page.No findings

    Why it is in this group

    • The name "getMyQuests" says "get": a word for reading.
    Description, as the server wrote it
    Lists the quests the account behind the API key has posted (paid real-world tasks), newest first, ten per page. Use it to find a quest's questID, check which are still open and how many offers each has received, or follow up on quests posted earlier. Optionally filter by status ("Open", "In Progress", "Completed", "Deleted" - Deleted also covers expired and removed); with no filter every status is returned. Pass nextOffset from the previous result as offset to get the next page. Returns { quests: [{ questID, title, status, price (whole currency units, as postQuest takes it), currency, startingCountry, startingLocation, scopeOfReach, datePosted, dueDate, dueDateType, dateRangeEnd, humansWanted, offerCount (pending offers), views }], nextOffset (null when there are no more) }. Use getQuest with a questID for the full details. Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getQuestReturns the full details of one quest (a paid real-world task people are hiring humans for), given its questID.No findings

    Why it is in this group

    • The name "getQuest" says "get": a word for reading.
    Description, as the server wrote it
    Returns the full details of one quest (a paid real-world task people are hiring humans for), given its questID. Use it after getQuestsV2 to read a listing properly, or after postQuest to check how the quest you just posted looks and how many offers it has. Open quests are visible to anyone; the account that posted a quest can also view it after it stops being open. A quest that doesn't exist or isn't visible to the caller returns a "Quest not found" error. Returns { questID, status, isOwner, title, description, category, subCategory, price (smallest currency unit), currency, priceNegotiable, additionalPurchasesPrice, paymentRecurrence, numberOfHours, humansWanted, offerCount, district, countryCode, startingCountry, startingLocation, endingCountry, endingLocation, scopeOfReach, datePosted, dueDate, dueDateType, dateRangeEnd, timeRange, urgent, requirements, screeningQuestions, portfolioLinkRequired }. Poster identity is never included. Read-only: viewing a quest changes nothing.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getQuestCommentsReturns the question threads on a quest, as the Quest app shows them to everyone: what humans have asked before making an offer, the poster's replies, and the follow-up threads on …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "getQuestComments" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "thread": it reads messages.
    • untrusted-inputThe name "getQuestComments" says "get" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "return" and "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    Returns the question threads on a quest, as the Quest app shows them to everyone: what humans have asked before making an offer, the poster's replies, and the follow-up threads on offers. Use it to see and prepare answers to questions on a quest you posted, or to read what others asked on any open quest. Takes the questID from getQuestsV2 or postQuest. Visibility matches getQuest: open quests are visible to anyone, and the poster can also read their own quest after it stops being open; anything else returns a "Quest not found" error. Ordering matches the Quest app: threads run oldest question first, and inside each thread the first comment is the original question, followed by replies oldest first. Returns { questID, questStatus, threadCount, commentCount, threads: [{ threadID, comments: [{ commentID, parentCommentID (null on the first comment of a thread), type (question | answer | follow-up-root | follow-up-question | follow-up-answer), proposalID (set on follow-up comments: the offer they belong to), author (poster | human), isYou, text, removed, sentAt }] }] }. A comment removed by moderation has removed: true and text: null. Nobody's name or photo is included. To answer a question on a quest you posted, use replyToQuestComment with a commentID from here. Read-only: reading changes nothing.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getQuestOffersLists the offers humans have made on one of your own quests, whether it needs one human or several - you don't need to know which.No findings

    Why it is in this group

    • The name "getQuestOffers" says "get": a word for reading.
    Description, as the server wrote it
    Lists the offers humans have made on one of your own quests, whether it needs one human or several - you don't need to know which. Only the quest's poster can use it; anyone else gets not found. Returns { questID, questStatus, questType ("single" or "multihire"), humansWanted, humansHired (confirmed), hireRequestsAwaitingConfirmation, slotsRemaining (slots still to fill), currency, offers: [{ proposalID, status, sentAt, price, fees: { connectionFee, processingFee }, screeningAnswers: [{ question, answer }], confirmationDeadline, declinedBy, human: { name (first name and last initial), averageRating, reviewCount, questsCompleted, questsCancelled, phoneVerified, emailVerified, preferredBadge, country, skills } }], nextOffset (null when there are no more) }. price and fees are in whole units of currency (S$30 is 30, the same unit postQuest takes), and are what the human asked for - fees are on top. An offer's status is one of: pending (waiting for your decision), hire-requested (you asked this human and they haven't confirmed; it holds a slot), hired (confirmed, work under way), completed, declined, expired (they didn't confirm in time). Quest chooses which offers to show from the quest's status and how many humans are hired: an open quest lists every offer, a quest under way lists the hired and finished humans. Twenty per page: pass nextOffset as offset for the next. Read-only - unlike the app, listing offers does not mark them as seen. When reviewing offers, recommend one with a short reason (rating, completed quests, verification, price, screening answers). Do not hire without the user's confirmation.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • getQuestsV2Browse open paid tasks ("quests") that people are hiring humans for right now - errands, in-person checks, on-site photos, deliveries, event and booth help, and more.Reads text others writeNo findings

    Why it is in this group

    • The name "getQuestsV2" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse open paid tasks ("quests") that people are hiring humans for right now - errands, in-person checks, on-site photos, deliveries, event and booth help, and more. Use this to see what's already posted, e.g. to gauge going rates or find existing similar requests, before deciding whether to post a new one with postQuest. The user is always the authenticated MCP caller. Every filter parameter is optional; with none supplied, recent admin-vetted quests are returned newest-first. Returns { quests: [...], rowsSkipped: number, resultCount: number } (resultCount only on the first page). Each quest has questID, title, price (smallest currency unit), district, countryCode, startingCountry, startingLocation, datePosted, dueDate and offerCount. Poster identity is never included.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • whoAmIReturns the identity authenticated to this MCP call.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns the identity authenticated to this MCP call.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

14 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__quest__getQuestComments"
    ]
  }
}

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:18 UTC, unchanged since Nov 20, 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
5
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 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.hireahuman.quest/mcp: tools/list returned 11 tools to an anonymous client, including replyToQuestComment (irreversible), postQuest (write), getQuestOffer (write), hireHuman (write), getHireStatus (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 3 to 5
  2. Nov 13, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "getQuestOffer" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "getQuestOffer" says "get": a word for reading.

    What this check looks for
  • The server marks "getHireStatus" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "getHireStatus" says "get": a word for reading.

    What this check looks for

History

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

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
    • Tools that change things, listed without credentials: 3 to 5
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

Install

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

claude mcp add --transport http quest https://mcp.hireahuman.quest/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http quest https://mcp.hireahuman.quest/mcp --header 'Authorization: <your-authorization>'

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__quest__whoAmI",
      "mcp__quest__getQuestsV2",
      "mcp__quest__getQuest",
      "mcp__quest__getQuestComments",
      "mcp__quest__getMyQuests",
      "mcp__quest__getQuestOffers"
    ],
    "ask": [
      "mcp__quest__replyToQuestComment",
      "mcp__quest__postQuest",
      "mcp__quest__getQuestOffer",
      "mcp__quest__hireHuman",
      "mcp__quest__getHireStatus"
    ],
    "deny": []
  }
}

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 quest. Review it before you use it.

Capability tags behind 7 rules
  • mcp__quest__getQuestsV2 untrusted-input
  • mcp__quest__getQuestComments private-data, untrusted-input
  • mcp__quest__replyToQuestComment untrusted-input, outbound
  • mcp__quest__postQuest untrusted-input, outbound
  • mcp__quest__getQuestOffer untrusted-input
  • mcp__quest__hireHuman untrusted-input
  • mcp__quest__getHireStatus untrusted-input

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/quest.hireahuman/quest/verify?hash=8190000be3ed5fbf715f0366d48282b99ddf845408e192e0090e83e671999eeb" | jq -e '.changed == false'

Pinned hash 8190000be3ed, from Nov 20, 2026, 05:18 UTC.

Watch

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

https://radar.anlyon.com/servers/quest.hireahuman/quest/changes.xml

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

Badge

Anlyon Radar badge for quest.hireahuman/quest
[![Anlyon Radar](https://radar.anlyon.com/badge/quest.hireahuman/quest.svg)](https://radar.anlyon.com/servers/quest.hireahuman/quest)

Source: MCP Registry. Synced Nov 20, 2026, 06:18 UTC.

Quest: Hire a Human MCP server: questions and answers

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

Is the Quest: Hire a Human MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 5 of which can change, send or delete something, and 2 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 Quest: Hire a Human MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Quest: Hire a Human MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: replyToQuestComment.

What tools does the Quest: Hire a Human MCP server have?

11 tools: 1 irreversible, 4 write, 6 read. replyToQuestComment, postQuest, getQuestOffer, hireHuman, getHireStatus, whoAmI, getQuestsV2, getQuest and 3 more.

Does the Quest: Hire a Human MCP server need sign-in or OAuth?

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

Does the Quest: Hire a Human 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): replyToQuestComment and postQuest.

Has the Quest: Hire a Human MCP server changed its tools?

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