# Human Pages (remote · humanpages.ai)

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

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `humanpages.ai`: 64/100 (this document), [markdown](https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages.md), [page](https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages)
- npm · `humanpages`: 67/100, [markdown](https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages-2.md), [page](https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages-2)

## Channel facts

- Endpoint: `https://humanpages.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.6`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 40 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 6606 tokens (~165/item across 40 items; 40 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http human-pages-ai-humanpages https://humanpages.ai/mcp
```

### Codex

```toml
[mcp_servers.human-pages-ai-humanpages]
url = "https://humanpages.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "human-pages-ai-humanpages": {
      "type": "remote",
      "url": "https://humanpages.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add human-pages-ai-humanpages --url https://humanpages.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  human-pages-ai-humanpages:
    url: "https://humanpages.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "human-pages-ai-humanpages": {
      "type": "http",
      "url": "https://humanpages.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (40)

### `search_humans` (~986 tokens)

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.

Input parameters:

- `accepts_crypto` (boolean): Filter to only show humans who have a crypto wallet set up and can accept USDC payments
- `available_only` (boolean): Only return humans who are currently available (default: true)
- `certificate` (string): Filter by certificate name or issuer (e.g., "AWS", "PMP", "Google"). Partial match, case-insensitive.
- `degree` (string): Filter by education degree (e.g., "Bachelor", "MBA", "PhD"). Partial match, case-insensitive.
- `equipment` (string): Filter by equipment (e.g., "car", "drone", "camera")
- `fiat_platform` (string): Filter by fiat payment platform the human accepts (e.g., "WISE", "PAYPAL", "VENMO", "REVOLUT", "CASHAPP", "ZELLE", "MONZO", "N26", "MERCADOPAGO")
- `field` (string): Filter by field of study (e.g., "Computer Science", "Marketing"). Partial match, case-insensitive.
- `has_photo` (boolean): Only return humans with an approved profile photo.
- `has_verified_login` (boolean): Only return humans who have verified their identity via an OAuth provider (Google, LinkedIn, or GitHub). Does not reveal which provider.
- `institution` (string): Filter by educational institution name (e.g., "MIT", "Oxford"). Partial match, case-insensitive.
- `language` (string): Filter by language ISO code (e.g., "en", "es", "zh")
- `lat` (number): Latitude for radius search (requires lng and radius)
- `lng` (number): Longitude for radius search (requires lat and radius)
- `location` (string): Filter by location. Use fully-qualified names for best results (e.g., "San Francisco, California, USA" not just "San Francisco"). When provided without lat/lng, the server geocodes the text and searc…
- `max_rate` (number): Maximum hourly rate in USD. Humans who set rates in other currencies are auto-converted to USD for comparison.
- `min_channels` (number): Only return humans with at least this many notification channels active (0-4). Channels: email, telegram, whatsapp, push. Use min_channels=2 to find humans who are likely to respond quickly to job of…
- `min_completed_jobs` (number): Only return humans who have completed at least this many jobs on the platform. Use min_completed_jobs=1 to find all workers with any platform track record. Works with or without other filters — no sk…
- `min_experience` (number): Minimum years of professional experience
- `min_vouches` (number): Only return humans vouched for by at least this many other users.
- `payment_type` (string): Filter by accepted payment type (UPFRONT, ESCROW, or UPON_COMPLETION)
- `radius` (number): Search radius in kilometers (default: 30km). Works with both text location and explicit lat/lng coordinates.
- `skill` (string): Filter by skill tag (e.g., "photography", "driving", "cleaning", "notary")
- `sort_by` (string): Sort results by: "completed_jobs" (humans with platform experience first), "rating" (highest rated first), "experience" (most years of professional experience first), "recent" (most recently active f…
- `verified` (string): Filter by verification status. Use "humanity" to only return humans who have verified their identity via Gitcoin Passport (score >= 20).
- `work_mode` (string): Filter by work mode preference (REMOTE, ONSITE, or HYBRID)

### `get_human` (~91 tokens)

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.

Input parameters:

- `id` (string, required): The unique ID of the human

### `register_agent` (~290 tokens)

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.

Input parameters:

- `accept_tos` (boolean, required): You must pass true to confirm you accept the Human Pages Terms of Use (https://humanpages.ai/terms). Required.
- `contact_email` (string): Contact email for the agent operator
- `description` (string): Brief description of what your agent does (max 500 chars)
- `name` (string, required): Display name for your agent (e.g., "Acme AI Assistant")
- `wallet_address` (string): Optional EVM wallet address (0x...) for USDC payments. Can also be set later with set_wallet. If you don't have a wallet, create one programmatically using the Coinbase Developer Platform (CDP) Agent…
- `webhook_url` (string): Webhook URL for receiving platform events (new job matches, status changes, announcements). Must be a public HTTPS endpoint.
- `website_url` (string): Your website URL (can be verified later for a trust badge)

### `get_agent_profile` (~41 tokens)

Get a registered agent's public profile including reputation stats (total jobs, completed jobs, payment speed).

Input parameters:

- `agent_id` (string, required): The registered agent ID

### `get_wallet_nonce` (~103 tokens)

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.

Input parameters:

- `agent_id` (string, required): Your registered agent ID
- `agent_key` (string, required): Your agent API key (starts with hp_)
- `wallet_address` (string, required): EVM wallet address to verify (0x...)

### `set_wallet` (~231 tokens)

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.

Input parameters:

- `agent_id` (string, required): Your registered agent ID
- `agent_key` (string, required): Your agent API key (starts with hp_)
- `nonce` (string): The nonce returned by get_wallet_nonce
- `signature` (string): EIP-191 signature of the challenge message from get_wallet_nonce
- `wallet_address` (string, required): EVM wallet address (0x...)
- `wallet_network` (string): Blockchain network (default: "base"). Options: base, ethereum, polygon, arbitrum

### `get_funding_info` (~202 tokens)

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).

Input parameters:

- `agent_id` (string, required): Your registered agent ID
- `agent_key` (string, required): Your agent API key (starts with hp_)
- `country` (string): ISO 3166-1 alpha-2 country code of the developer (e.g., "US", "IL", "SG", "NG"). Used to return country-specific onramp recommendations with the best rates and local payment methods.

### `verify_agent_domain` (~112 tokens)

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).

Input parameters:

- `agent_id` (string, required): The registered agent ID
- `agent_key` (string, required): The agent API key (starts with hp_)
- `method` (string, required): Verification method: "well-known" or "dns"

### `create_job_offer` (~745 tokens)

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.

Input parameters:

- `agent_id` (string, required): Your unique agent identifier (any string)
- `agent_key` (string, required): Your registered agent API key (starts with hp_). Required.
- `agent_lat` (number): Agent latitude for distance filtering. Required if human has maxOfferDistance set.
- `agent_lng` (number): Agent longitude for distance filtering. Required if human has maxOfferDistance set.
- `agent_name` (string): Display name override (defaults to registered agent name)
- `callback_secret` (string): Secret for HMAC-SHA256 signature verification (min 16 chars). The signature is sent in X-HumanPages-Signature header.
- `callback_url` (string): Webhook URL to receive job status updates (ACCEPTED, REJECTED, PAID, COMPLETED). Must be a public HTTP(S) endpoint.
- `category` (string): Category of the task (e.g., "photography", "research", "delivery", "cleaning")
- `description` (string, required): Detailed description of what needs to be done
- `escrow_arbitrator_address` (string): Wallet address of the arbitrator (from list_arbitrators). Required when payment_mode=ESCROW. The arbitrator resolves disputes and earns a fee (set by them, max 10%).
- `human_id` (string, required): The ID of the human to hire
- `payment_mode` (string): Payment mode. ONE_TIME (default) for single payments. STREAM for ongoing stream payments. ESCROW for on-chain escrow with arbitrator dispute resolution — funds locked in smart contract, auto-released…
- `payment_timing` (string): For ONE_TIME jobs only. "upfront" (default) = pay before work. "upon_completion" = pay after work is done.
- `preferred_payment_method` (string): Signal to the human what payment methods you support. "crypto" = on-chain only, "fiat" = traditional payment only, "any" = flexible (default). The human sees this when deciding whether to accept.
- `price_usd` (number, required): Agreed price in USD. Must meet the human's minOfferPrice if set. Payment method (crypto or fiat) is flexible — agreed after acceptance.
- `stream_interval` (string): How often payments are made/checkpointed. Required when payment_mode=STREAM.
- `stream_max_ticks` (number): Optional cap on number of payment intervals. Null = indefinite.
- `stream_method` (string): Stream method. SUPERFLUID: agent creates an on-chain flow that streams tokens per-second. MICRO_TRANSFER: agent sends periodic discrete transfers. Required when payment_mode=STREAM.
- `stream_rate_usd` (number): USD amount per interval (e.g., 10 = $10/day if interval=DAILY). Required when payment_mode=STREAM. Stream payments use crypto (USDC) on-chain.
- `title` (string, required): Title of the job/task

### `get_job_status` (~139 tokens)

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.

Input parameters:

- `job_id` (string, required): The job ID returned from create_job_offer

### `mark_job_paid` (~276 tokens)

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.

Input parameters:

- `job_id` (string, required): The job ID
- `payment_amount` (number, required): The amount paid in USD equivalent
- `payment_method` (string, required): How you paid the human. Crypto methods (usdc, eth, sol, other_crypto) are verified on-chain. Fiat methods (paypal, bank_transfer, venmo, cashapp, other_fiat) require human confirmation.
- `payment_network` (string): Blockchain network (e.g., "base", "ethereum", "solana"). Required for crypto payments, ignored for fiat.
- `payment_reference` (string, required): Proof of payment. For crypto: the on-chain transaction hash. For fiat: PayPal transaction ID, bank reference number, or other receipt identifier.

### `approve_completion` (~104 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (hp_...)
- `job_id` (string, required): The job ID

### `request_revision` (~99 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (hp_...)
- `job_id` (string, required): The job ID
- `reason` (string, required): Explain what needs to be revised or fixed

### `check_humanity_status` (~58 tokens)

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.

Input parameters:

- `human_id` (string, required): The ID of the human to check

### `leave_review` (~101 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `comment` (string): Optional review comment
- `job_id` (string, required): The job ID
- `rating` (number, required): Rating from 1-5 stars

### `get_human_profile` (~126 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)
- `human_id` (string, required): The ID of the human

### `request_activation_code` (~62 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)

### `verify_social_activation` (~75 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)
- `post_url` (string, required): URL of the social media post containing your activation code

### `get_activation_status` (~75 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)

### `get_payment_activation` (~42 tokens)

Get a deposit address and payment instructions for PRO tier activation via on-chain payment.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)

### `verify_payment_activation` (~87 tokens)

Verify an on-chain payment for PRO tier activation. On success, your agent is activated with PRO tier.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)
- `network` (string, required): The blockchain network (e.g., "ethereum", "base", "solana")
- `tx_hash` (string, required): The on-chain transaction hash of the activation payment

### `start_stream` (~280 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `job_id` (string, required): The job ID
- `network` (string, required): Blockchain network (e.g., "base", "polygon", "arbitrum")
- `sender_address` (string, required): Your wallet address that created the flow (Superfluid) or will send payments (micro-transfer)
- `token` (string): Token symbol (default: "USDC")

### `record_stream_tick` (~83 tokens)

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).

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `job_id` (string, required): The job ID
- `tx_hash` (string, required): The on-chain transaction hash for this tick payment

### `pause_stream` (~73 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `job_id` (string, required): The job ID

### `resume_stream` (~91 tokens)

Resume a paused stream. For Superfluid: create a new flow first, then call this — backend verifies. For micro-transfer: creates a new pending tick.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `job_id` (string, required): The job ID
- `sender_address` (string): Wallet address for the new flow (Superfluid only, optional if same as before)

### `stop_stream` (~61 tokens)

Stop a stream permanently and mark the job as completed. Can be called by agent or human on STREAMING or PAUSED jobs.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `job_id` (string, required): The job ID

### `send_job_message` (~111 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `content` (string, required): Message content (max 2000 characters)
- `job_id` (string, required): The job ID

### `get_job_messages` (~78 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `job_id` (string, required): The job ID

### `create_listing` (~561 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `budget_usd` (number, required): Budget in USD (minimum $5). Payment method is flexible — agreed between agent and human.
- `callback_secret` (string): Secret for HMAC-SHA256 webhook signature (min 16 chars)
- `callback_url` (string): Webhook URL for application notifications
- `category` (string): Category (e.g., "marketing", "photography", "research")
- `description` (string, required): Detailed description of the work, expectations, and deliverables
- `expires_at` (string, required): ISO 8601 expiration date (must be in future, max 90 days). Example: "2025-03-01T00:00:00Z"
- `location` (string): Location name for the work (e.g., "San Francisco")
- `location_country` (string): ISO 3166-1 alpha-2 country code (e.g., "US", "PH"). Improves Google Search visibility.
- `location_lat` (number): Latitude for location-based filtering
- `location_lng` (number): Longitude for location-based filtering
- `location_locality` (string): City name (e.g., "San Francisco", "Manila"). Improves Google Search visibility.
- `location_postal` (string): Postal/zip code (e.g., "94105"). Improves Google Search visibility.
- `location_region` (string): State or province (e.g., "California", "Metro Manila"). Improves Google Search visibility.
- `location_street` (string): Street address (e.g., "123 Main St"). Improves Google Search visibility.
- `max_applicants` (number): Maximum number of applicants before listing auto-closes
- `radius_km` (number): Radius in km for location-based filtering
- `required_equipment` (array): Equipment applicants should have (e.g., ["camera", "drone"])
- `required_skills` (array): Skills applicants should have (e.g., ["social-media", "copywriting"])
- `title` (string, required): Title of the listing (e.g., "Social media promotion for AI product")
- `work_mode` (string): Work mode for the listing

### `get_listings` (~223 tokens)

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.

Input parameters:

- `category` (string): Filter by category
- `lat` (number): Latitude for location-based filtering
- `limit` (number): Results per page (default: 20, max: 50)
- `lng` (number): Longitude for location-based filtering
- `max_budget` (number): Maximum budget in USD
- `min_budget` (number): Minimum budget in USD
- `page` (number): Page number (default: 1)
- `radius` (number): Radius in km for location-based filtering
- `skill` (string): Filter by required skill (comma-separated for multiple, e.g., "photography,editing")
- `work_mode` (string): Filter by work mode

### `get_listing` (~37 tokens)

Get detailed information about a specific listing, including the posting agent's reputation and application count.

Input parameters:

- `listing_id` (string, required): The listing ID

### `get_listing_applications` (~88 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `listing_id` (string, required): The listing ID

### `make_listing_offer` (~128 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `application_id` (string, required): The application ID of the chosen applicant
- `listing_id` (string, required): The listing ID

### `cancel_listing` (~58 tokens)

Cancel an open listing. All pending applications will be rejected. Only the agent who created the listing can cancel it.

Input parameters:

- `agent_key` (string, required): Your agent API key (starts with hp_)
- `listing_id` (string, required): The listing ID

### `list_arbitrators` (~70 tokens)

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.

### `register_as_arbitrator` (~230 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)
- `fee_bps` (number, required): Your fee in basis points (e.g., 500 = 5%). Max 1000 (10%).
- `sla` (string): Response time commitment (e.g., "24h response")
- `specialties` (array): Areas of expertise for dispute resolution (e.g., ["design", "code", "writing"])
- `wallet_signature` (string): Signed message linking your wallet to your agent: "I am arbitrator {wallet} for HP Agent {apiKeyHash}"
- `webhook_url` (string, required): Webhook endpoint for dispute notifications. Must have a /health endpoint that returns 200.

### `get_dispute_details` (~79 tokens)

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.

Input parameters:

- `agent_key` (string, required): Your agent API key (must be the assigned arbitrator)
- `job_id` (string, required): The job ID of the disputed escrow

### `submit_verdict` (~218 tokens)

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 }.

Input parameters:

- `agent_key` (string, required): Your agent API key
- `arbitrator_fee` (string, required): Your fee amount (raw USDC, 6 decimals). Must match your locked rate.
- `job_id` (string, required): The disputed job ID
- `nonce` (string, required): Unique nonce for replay protection
- `signature` (string, required): EIP-712 signature of the Verdict struct (hex string starting with 0x)
- `to_depositor` (string, required): Amount to refund to payer (raw USDC, 6 decimals)
- `to_payee` (string, required): Amount to send to worker (raw USDC, 6 decimals, e.g. "70000000" for $70)

### `get_promo_status` (~39 tokens)

Check the launch promo status — free PRO tier for the first 100 agents. Returns how many slots are claimed and remaining. No authentication required.

### `claim_free_pro_upgrade` (~53 tokens)

Deprecated: Agents are now auto-activated on PRO tier at registration. This endpoint is a no-op for agents already on PRO.

Input parameters:

- `agent_key` (string, required): Your registered agent API key (starts with hp_)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://humanpages.ai/mcp
- Repository: https://github.com/human-pages-ai/humanpages
- Website: https://humanpages.ai/
- Changelog RSS feed: https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages/changelog.json
- HTML version of this page: https://verifymcp.io/servers/human-pages-ai-humanpages/humanpages