Home / MCP registry index / io.github.human-pages-ai/humanpages

Human Pages

io.github.human-pages-ai/humanpages in the official MCP registry. Endpoint https://humanpages.ai/mcp. Source: github.com/human-pages-ai/humanpages.

The registry describes it as: Hire real humans for tasks agents can't do alone. 36 tools for the full hiring lifecycle.

We read its 40 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "humanpages": {
      "url": "https://humanpages.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"humanpages","type":"http","url":"https://humanpages.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search_humans get_human register_agent get_agent_profile get_wallet_nonce set_wallet get_funding_info verify_agent_domain create_job_offer get_job_status mark_job_paid approve_completion request_revision check_humanity_status leave_review get_human_profile request_activation_code verify_social_activation get_activation_status get_payment_activation verify_payment_activation start_stream record_stream_tick pause_stream resume_stream stop_stream send_job_message get_job_messages create_listing get_listings get_listing get_listing_applications make_listing_offer cancel_listing list_arbitrators register_as_arbitrator get_dispute_details submit_verdict get_promo_status claim_free_pro_upgrade

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-human-pages-ai-humanpages/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-human-pages-ai-humanpages)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.