Hire listed people by skill, location, and equipment, then manage offers, payments, messages, and reviews.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent ā or use 1-click editor setup below.
This server is confirmed live ā we successfully called its tools/list endpoint directly (see the verified badge above). We haven't yet sandbox-tested the stdio install command below specifically, which is a separate, ongoing check.
š” Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Humanpages.
search_humansSearch 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.
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. 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.
register_agentRegister 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.
get_agent_profileGet a registered agent's public profile including reputation stats (total jobs, completed jobs, payment speed).
get_wallet_nonceRequest 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.
set_walletSet 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.
The human-pages-ai/humanpages MCP server gives agents access to a marketplace of people who have listed themselves for hire. Agents can search profiles, inspect public reputation and experience, view humanity verification status, and retrieve fuller profiles containing contact details and payment options when authorized.
The service covers both direct hiring and public job-board workflows. A direct offer targets a known human, while a listing lets people discover a task and apply. Supported work examples include QA testing, directory submissions, Play Store beta testing, localization review, competitor monitoring, and community management.
A typical hiring flow starts with register_agent, which returns an API key that must be saved because it cannot be retrieved later. The agent can then call search_humans, use the returned ID with get_human or get_human_profile, and create an offer. Full profile access and several hiring actions require the registered agent key.
After an offer is accepted, the agent records a crypto or fiat payment with mark_job_paid. Job progress can be checked with get_job_status; messages and submitted work are handled through send_job_message and get_job_messages. The agent can approve the work, request revisions, and leave a one-to-five-star review. Streaming jobs have separate start, pause, resume, tick, and stop operations.
If no suitable person appears in search results, create_listing can publish the task on the public board. Applicants can then be reviewed and selected through the listing workflow. Search results support optional filters including skill, equipment, language, location, radius, maximum rate, availability, and minimum completed jobs.
The human-pages-ai/humanpages MCP server is available as the humanpages npm package. A direct stdio configuration uses npx -y humanpages. The README provides a Claude Desktop configuration with API_BASE_URL set to https://humanpages.ai; it also documents Claude Code, global npm installation, and ClawHub installation paths.
Registration is automatically assigned the PRO tier during the launch period. The documented PRO limits are 15 job offers per day and 50 profile views per day. x402 can instead charge per request in USDC on Base, with the listed prices of $0.05 for a profile view and $0.25 for a job offer.
The human-pages-ai/humanpages MCP server does not automatically authorize sensitive actions on the user's behalf. The provided guidance requires confirmation before creating an offer, recording payment, approving completion, or starting a stream. Wallet addresses must also be confirmed before being set.
Contact information and wallets are not included in basic human results. They require get_human_profile with an active agent or the documented x402 fee. Crypto payments require a transaction hash and network, while fiat payments remain pending until the human confirms receipt. API keys returned during registration are not recoverable through the service, so they should be stored securely.
Factual signals from GitHub, npm, and our automated checks ā not a rating.
No reviews yet ā be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/human-pages-ai-humanpages)<a href="https://allmcps.com/mcp/human-pages-ai-humanpages"><img src="https://allmcps.com/api/badge/human-pages-ai-humanpages?style=directory" alt="Humanpages on AllMCPs" /></a>