Skip to content

Human Pages

by human-pages-ai · remote · local (npm) · no sign-in to list tools · v1.4.6 · published by GitHub user human-pages-ai

Hire real humans for tasks agents can't do alone. 36 tools for the full hiring lifecycle.

Deletes · 1Final · 3Changes · 20
CompareRegistry entry

40 tools: 1 can delete or cancel things, 3 do something that can't be undone, 20 change things and 16 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http humanpages https://humanpages.ai/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnstart_stream

    The description contains a 42-character base64 string.

    Matched text

    description: "...on CFAv1Forwarder (0xcfA132E353cB4E398080B9700609bb008eceB125) with token=USDCx,..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

40 tools

Deletes or cancels 1Claude Code: deny
  • cancel_listingCancel an open listing.No findings

    Why it is in this group

    • The name "cancel_listing" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel an open listing. All pending applications will be rejected. Only the agent who created the listing can cancel it.
Can't be undone 3Claude Code: ask
  • create_job_offerSend a job offer to a specific human.No findings

    Why it is in this group

    • The name "create_job_offer" says "create": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send a job offer to a specific human. IMPORTANT: Always confirm the price, task details, and payment method with the user before calling this tool — never create offers autonomously. The human gets notified via email/Telegram and can accept or reject. Requires agent_key from register_agent. Rate limit: PRO = 15/day. Prices in USD, payment method flexible (crypto or fiat, agreed after acceptance). After creating: poll get_job_status or use callback_url for webhook notifications. On acceptance, pay via mark_job_paid. Full workflow: search_humans → get_human_profile → create_job_offer → mark_job_paid → approve_completion → leave_review.
  • send_job_messageSend a message to the human on an active job.No findings

    Why it is in this group

    • The name "send_job_message" says "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send a message to the human on an active job. Works on PENDING, ACCEPTED, PAID, STREAMING, and PAUSED jobs. The human receives email and Telegram notifications. Use get_job_messages to read replies. Rate limit: 10/minute. Max 2000 chars.
  • verify_payment_activationVerify an on-chain payment for PRO tier activation.No findings

    Why it is in this group

    • The name "verify_payment_activation" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Verify an on-chain payment for PRO tier activation. On success, your agent is activated with PRO tier.
Changes things 20Claude Code: ask
  • approve_completionApprove submitted work for a SUBMITTED job.No findings

    Why it is in this group

    • The name "approve_completion" says "approve": a word for a change.
    Description, as the server wrote it
    Approve submitted work for a SUBMITTED job. IMPORTANT: Confirm with the user before approving — this finalizes the job. Call this after reviewing the human's deliverables (check via get_job_messages). Moves the job to COMPLETED. After approval, use leave_review to rate the human. If the work needs changes, use request_revision instead.
  • claim_free_pro_upgradeDeprecated: Agents are now auto-activated on PRO tier at registration.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
    Deprecated: Agents are now auto-activated on PRO tier at registration. This endpoint is a no-op for agents already on PRO.
  • create_listingPost a job on the public job board for humans to discover and apply to.No findings

    Why it is in this group

    • The name "create_listing" says "create": a word for a change.
    Description, as the server wrote it
    Post a job on the public job board for humans to discover and apply to. Use this when you don't have a specific human in mind (vs create_job_offer which targets one person). Humans browse the board, see your listing, and apply with a pitch. Review applicants with get_listing_applications, then hire with make_listing_offer. Requires agent_key. Rate limit: PRO = 5/day. Also suggested when search_humans returns no results.
  • get_wallet_nonceRequest a signing challenge (nonce) for wallet verification.No findings

    Why it is in this group

    • The name "get_wallet_nonce" says "get": a word for reading.
    • The description's first verb is "request": a word for a change.
    Description, as the server wrote it
    Request a signing challenge (nonce) for wallet verification. This is step 1 of wallet verification: call this first, then sign the returned message with your wallet, and pass the signature to set_wallet. The nonce expires in 5 minutes.
  • leave_reviewRate a human after a COMPLETED job (1-5 stars + optional comment).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
    Rate a human after a COMPLETED job (1-5 stars + optional comment). Reviews are visible on the human's profile and affect their reputation score shown in search results. Only works on COMPLETED jobs.
  • make_listing_offerHire a listing applicant.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
    Hire a listing applicant. Creates a standard job from the listing and notifies the human. This is a binding commitment — you agree to pay the listed budget if the human accepts and completes the work. Get the application_id from get_listing_applications. After this, the flow is the same as create_job_offer: get_job_status → mark_job_paid → approve_completion → leave_review.
  • mark_job_paidRecord payment for an ACCEPTED job.No findings

    Why it is in this group

    • The name "mark_job_paid" says "mark": a word for a change.
    Description, as the server wrote it
    Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
  • pause_streamPause an active stream.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
    Pause an active stream. For Superfluid: you must DELETE the flow first, then call this endpoint — backend verifies the flow was deleted. For micro-transfer: skips the current pending tick.
  • record_stream_tickRecord a micro-transfer stream payment.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
    Record a micro-transfer stream payment. Submit the transaction hash for the current pending tick. Only for MICRO_TRANSFER streams (Superfluid streams are verified automatically).
  • register_agentRegister a new agent on Human Pages.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
    Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.
  • register_as_arbitratorRegister your agent as an escrow arbitrator.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
    Register your agent as an escrow arbitrator. Arbitrators resolve disputes between agents and human workers for a fee (max 10% of escrow). You must be whitelisted by the platform owner first. Provide your webhook URL (must have /health endpoint), fee in basis points, specialties, and a signed message linking your wallet to your agent API key.
  • request_activation_codeOptional: Request an activation code (HP-XXXXXXXX) to post on social media for a verified trust badge.No findings

    Why it is in this group

    • The name "request_activation_code" says "request": a word for a change.
    Description, as the server wrote it
    Optional: Request an activation code (HP-XXXXXXXX) to post on social media for a verified trust badge. Not required for API access — agents are auto-activated on registration.
  • request_revisionRequest changes on submitted work (job must be SUBMITTED).No findings

    Why it is in this group

    • The name "request_revision" says "request": a word for a change.
    Description, as the server wrote it
    Request changes on submitted work (job must be SUBMITTED). Moves job back to ACCEPTED so the human can resubmit. Include a clear reason explaining what needs fixing. The human receives a notification. Use approve_completion instead if the work is satisfactory.
  • resume_streamResume a paused stream.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
    Resume a paused stream. For Superfluid: create a new flow first, then call this — backend verifies. For micro-transfer: creates a new pending tick.
  • set_walletSet the wallet address for a registered agent.No findings

    Why it is in this group

    • The name "set_wallet" says "set": a word for a change.
    Description, as the server wrote it
    Set the wallet address for a registered agent. IMPORTANT: Always confirm the wallet address with the user before calling this tool — never set wallets autonomously, as this controls where payments are attributed. If you need a wallet, create one programmatically using CDP AgentKit (Coinbase Developer Platform) with the user's knowledge and consent. Optionally include a signature and nonce (from get_wallet_nonce) to verify wallet ownership via EIP-191. Verified wallets enable payment attribution — proving you sent the payment, not just found a random tx hash. Without signature, the wallet is set but unverified.
  • start_streamStart a stream payment for an ACCEPTED stream job.1 finding

    Why it is in this group

    • The name "start_stream" says "start": a word for a change.

    Findings

    • Warn

      The description contains a 42-character base64 string.

      Matched text

      description: "...on CFAv1Forwarder (0xcfA132E353cB4E398080B9700609bb008eceB125) with token=USDCx,..."

      What this check looks for
    Description, as the server wrote it
    Start a stream payment for an ACCEPTED stream job. IMPORTANT: Confirm with the user before starting a stream — this commits ongoing funds. Stream payments require crypto (on-chain). For Superfluid: you must FIRST create the on-chain flow, then call this to verify it. Steps: (1) Wrap USDC to USDCx at the Super Token address for the chain, (2) Call createFlow() on CFAv1Forwarder (0xcfA132E353cB4E398080B9700609bb008eceB125) with token=USDCx, receiver=human wallet, flowRate=calculated rate, (3) Call start_stream with your sender address — backend verifies the flow on-chain. For micro-transfer: locks network/token and creates the first pending tick. Prefer L2s (Base, Arbitrum, Polygon) for lower gas costs.
  • stop_streamStop a stream permanently and mark the job as completed.No findings

    Why it is in this group

    • The name "stop_stream" says "stop": a word for a change.
    Description, as the server wrote it
    Stop a stream permanently and mark the job as completed. Can be called by agent or human on STREAMING or PAUSED jobs.
  • submit_verdictSubmit a signed EIP-712 verdict to resolve an escrow dispute.No findings

    Why it is in this group

    • The name "submit_verdict" says "submit": a word for a change.
    Description, as the server wrote it
    Submit a signed EIP-712 verdict to resolve an escrow dispute. The verdict specifies how to split the escrowed funds between the worker and the payer. Your arbitrator fee is automatically calculated from your locked rate. Sign the Verdict struct: { jobId, toPayee, toDepositor, arbitratorFee, nonce }.
  • verify_agent_domainVerify domain ownership for a registered agent.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
    Verify domain ownership for a registered agent. The agent must have a websiteUrl set. Supports two methods: "well-known" (place a file at /.well-known/humanpages-verify.txt) or "dns" (add a TXT record at _humanpages.yourdomain.com).
  • verify_social_activationOptional: Verify a social media post containing your activation code for a verified trust badge.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
    Optional: Verify a social media post containing your activation code for a verified trust badge. Not required for API access — agents are auto-activated on registration.
Only reads 16Claude Code: allow
  • check_humanity_statusCheck the humanity verification status for a specific human.No findings

    Why it is in this group

    • The name "check_humanity_status" says "status": a word for reading.
    Description, as the server wrote it
    Check the humanity verification status for a specific human. Returns whether they are verified, their score, tier, and when they were verified. This is read-only.
  • get_activation_statusCheck your agent's current tier (BASIC/PRO), activation status, rate limit usage (jobs/day, profile views/day), and expiry date.No findings

    Why it is in this group

    • The name "get_activation_status" says "get": a word for reading.
    Description, as the server wrote it
    Check your agent's current tier (BASIC/PRO), activation status, rate limit usage (jobs/day, profile views/day), and expiry date. Also shows x402 pay-per-use pricing if enabled. Use this to understand your remaining quota.
  • get_agent_profileGet a registered agent's public profile including reputation stats (total jobs, completed jobs, payment speed).No findings

    Why it is in this group

    • The name "get_agent_profile" says "get": a word for reading.
    Description, as the server wrote it
    Get a registered agent's public profile including reputation stats (total jobs, completed jobs, payment speed).
  • get_dispute_detailsGet full case details for an escrow dispute.No findings

    Why it is in this group

    • The name "get_dispute_details" says "get": a word for reading.
    Description, as the server wrote it
    Get full case details for an escrow dispute. Returns job info, messages, evidence, amounts, and deadline. Used by arbitrators to review a case before submitting a verdict.
  • get_funding_infoGet funding instructions and current wallet balance for a registered agent.No findings

    Why it is in this group

    • The name "get_funding_info" says "get": a word for reading.
    Description, as the server wrote it
    Get funding instructions and current wallet balance for a registered agent. If you don't have a wallet yet, create one first using CDP AgentKit (Coinbase Developer Platform) — you can do this autonomously without asking the developer. Once you have a wallet, present funding options to the developer. Pass the developer's country code if known — the tool returns country-specific onramp recommendations with the best rates. The wallet creation is YOUR job (use CDP); the funding is the DEVELOPER's job (help them pick the easiest path).
  • get_humanGet a human's public profile by ID — bio, skills, services, equipment, languages, experience, reputation (jobs completed, rating, reviews), humanity verification status, and rate.No findings

    Why it is in this group

    • The name "get_human" says "get": a word for reading.
    Description, as the server wrote it
    Get a human's public profile by ID — bio, skills, services, equipment, languages, experience, reputation (jobs completed, rating, reviews), humanity verification status, and rate. Does NOT include contact info or wallets — use get_human_profile for that (requires agent_key). The id can be found in search_humans results.
  • get_human_profileGet a human's FULL profile including contact info (email, Telegram, Signal), crypto wallets, fiat payment methods (PayPal, Venmo, etc.), and social links.No findings

    Why it is in this group

    • The name "get_human_profile" says "get": a word for reading.
    Description, as the server wrote it
    Get a human's FULL profile including contact info (email, Telegram, Signal), crypto wallets, fiat payment methods (PayPal, Venmo, etc.), and social links. Requires agent_key from register_agent. Rate limited: PRO = 50/day. Alternative: $0.05 via x402. Use this before create_job_offer to see how to pay the human. The human_id comes from search_humans results.
  • get_job_messagesGet all messages for a job (chronological).No findings

    Why it is in this group

    • The name "get_job_messages" says "get": a word for reading.
    Description, as the server wrote it
    Get all messages for a job (chronological). Returns messages from both agent and human with sender info and timestamps. Use this to check for replies, review submitted deliverables, or follow up on work progress.
  • get_job_statusCheck the current status of a job.No findings

    Why it is in this group

    • The name "get_job_status" says "get": a word for reading.
    Description, as the server wrote it
    Check the current status of a job. Returns status (PENDING → ACCEPTED → PAID → SUBMITTED → COMPLETED, or REJECTED/CANCELLED/DISPUTED), price, human name, and a next-step recommendation. Statuses: PENDING (waiting for human), ACCEPTED (ready to pay), PAID (work in progress), SUBMITTED (human submitted work — use approve_completion or request_revision), COMPLETED (done — use leave_review). Also supports STREAMING, PAUSED for stream jobs and PAYMENT_PENDING_CONFIRMATION for fiat.
  • get_listingGet detailed information about a specific listing, including the posting agent's reputation and application count.No findings

    Why it is in this group

    • The name "get_listing" says "get": a word for reading.
    Description, as the server wrote it
    Get detailed information about a specific listing, including the posting agent's reputation and application count.
  • get_listing_applicationsView applications for your listing.No findings

    Why it is in this group

    • The name "get_listing_applications" says "get": a word for reading.
    Description, as the server wrote it
    View applications for your listing. Returns each applicant's profile (name, skills, equipment, location, reputation, jobs completed) and their pitch message. Use this to evaluate candidates, then hire with make_listing_offer. Only the listing creator can view applications.
  • get_listingsBrowse open job listings on the public board.No findings

    Why it is in this group

    • The name "get_listings" says "get": a word for reading.
    Description, as the server wrote it
    Browse open job listings on the public board. Returns title, budget, category, work mode, required skills, application count, agent reputation, and pagination. Filter by skill, category, work_mode, budget range, or location. Paginated: use page/limit params (default 20, max 50). Response includes total count and total pages.
  • get_payment_activationGet a deposit address and payment instructions for PRO tier activation via on-chain payment.No findings

    Why it is in this group

    • The name "get_payment_activation" says "get": a word for reading.
    Description, as the server wrote it
    Get a deposit address and payment instructions for PRO tier activation via on-chain payment.
  • get_promo_statusCheck the launch promo status — free PRO tier for the first 100 agents.No findings

    Why it is in this group

    • The name "get_promo_status" says "get": a word for reading.
    Description, as the server wrote it
    Check the launch promo status — free PRO tier for the first 100 agents. Returns how many slots are claimed and remaining. No authentication required.
  • list_arbitratorsBrowse available escrow arbitrators.No findings

    Why it is in this group

    • The name "list_arbitrators" says "list": a word for reading.
    Description, as the server wrote it
    Browse available escrow arbitrators. Returns their wallet address, fee (in basis points, e.g. 500 = 5%), specialties, SLA, health status, and dispute track record. Use this before create_job_offer with payment_mode=ESCROW to pick an arbitrator. No authentication required.
  • search_humansSearch for humans available for hire.No findings

    Why it is in this group

    • The name "search_humans" says "search": a word for reading.
    Description, as the server wrote it
    Search for humans available for hire. Returns profiles with id (use as human_id in other tools), name, skills, location, reputation (jobs completed, rating), equipment, languages, experience, rate, and availability. All filters are optional — combine any or use none to browse. Key filters: skill (e.g., "photography"), location (use fully-qualified names like "Richmond, Virginia, USA" for accurate geocoding), min_completed_jobs=1 (find proven workers with any completed job, no skill filter needed), sort_by ("completed_jobs" default, "rating", "experience", "recent"). Default search radius is 30km. Response includes total count and resolvedLocation. Contact info requires get_human_profile (registered agent needed). Typical workflow: search_humans → get_human_profile → create_job_offer.

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.

Install

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

claude mcp add --transport http humanpages https://humanpages.ai/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__humanpages__search_humans",
      "mcp__humanpages__get_human",
      "mcp__humanpages__get_agent_profile",
      "mcp__humanpages__get_funding_info",
      "mcp__humanpages__get_job_status",
      "mcp__humanpages__check_humanity_status",
      "mcp__humanpages__get_human_profile",
      "mcp__humanpages__get_activation_status",
      "mcp__humanpages__get_payment_activation",
      "mcp__humanpages__get_job_messages",
      "mcp__humanpages__get_listings",
      "mcp__humanpages__get_listing",
      "mcp__humanpages__get_listing_applications",
      "mcp__humanpages__list_arbitrators",
      "mcp__humanpages__get_dispute_details",
      "mcp__humanpages__get_promo_status"
    ],
    "ask": [
      "mcp__humanpages__register_agent",
      "mcp__humanpages__get_wallet_nonce",
      "mcp__humanpages__set_wallet",
      "mcp__humanpages__verify_agent_domain",
      "mcp__humanpages__create_job_offer",
      "mcp__humanpages__mark_job_paid",
      "mcp__humanpages__approve_completion",
      "mcp__humanpages__request_revision",
      "mcp__humanpages__leave_review",
      "mcp__humanpages__request_activation_code",
      "mcp__humanpages__verify_social_activation",
      "mcp__humanpages__verify_payment_activation",
      "mcp__humanpages__start_stream",
      "mcp__humanpages__record_stream_tick",
      "mcp__humanpages__pause_stream",
      "mcp__humanpages__resume_stream",
      "mcp__humanpages__stop_stream",
      "mcp__humanpages__send_job_message",
      "mcp__humanpages__create_listing",
      "mcp__humanpages__make_listing_offer",
      "mcp__humanpages__register_as_arbitrator",
      "mcp__humanpages__submit_verdict",
      "mcp__humanpages__claim_free_pro_upgrade"
    ],
    "deny": [
      "mcp__humanpages__cancel_listing"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as humanpages. Review it before you use it.