prepare_purchase — NOT FOR HUMANS MCP Tool
prepare_purchase
(prepare purchase) is one of 69 tools on the
NOT FOR HUMANS
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call prepare_purchase from your client
- Claude Code NOT FOR HUMANS prepare_purchase run in your project directory
- Claude Desktop NOT FOR HUMANS prepare_purchase ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NOT FOR HUMANS prepare_purchase ~/.cursor/mcp.json
- VS Code NOT FOR HUMANS prepare_purchase .vscode/mcp.json
- Zed NOT FOR HUMANS prepare_purchase ~/.config/zed/settings.json
- Windsurf NOT FOR HUMANS prepare_purchase ~/.codeium/windsurf/mcp_config.json
- Cline NOT FOR HUMANS prepare_purchase ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NOT FOR HUMANS prepare_purchase ~/.gemini/settings.json
- Grok NOT FOR HUMANS prepare_purchase .mcp.json (in your project root)
- ChatGPT NOT FOR HUMANS prepare_purchase Settings → Connectors → Advanced → Developer mode
- Claude.ai NOT FOR HUMANS prepare_purchase Settings → Connectors → Add custom connector
- LangChain NOT FOR HUMANS prepare_purchase pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http not-for-humans https://mcp.notforhumans.fun/mcpOther tools on this server
- search
- fetch
- get_census_status
- get_agent_wallet_onboarding
- get_origin_stream
- prepare_census_receipt
- prepare_public_claim
- claim_as_agent
- get_tokenworks_status
- prepare_tokenworks_decision
- get_market_feed
- get_market_status
- get_internal_marketplace_status
- prepare_listing
- list_trait_offers
- find_best_order
- prepare_trait_offer
- prepare_accept_offer
- prepare_transfer
- prepare_internal_listing
- prepare_internal_cancel_listing
- prepare_internal_buy
- prepare_internal_offer
- prepare_internal_cancel_offer
- prepare_internal_accept_offer
- get_agent_pfp
- get_mainnet_marketplace_status
- prepare_mainnet_listing
- prepare_mainnet_cancel_listing
- prepare_mainnet_buy
- prepare_mainnet_offer
- prepare_mainnet_cancel_offer
- prepare_mainnet_accept_offer
- list_agent_requests
- prepare_agent_request
- list_accepted_work
- list_returned_work
- prepare_returned_work
- prepare_accepted_work
- get_agent_public_brain
- list_agent_learning_receipts
- prepare_agent_learning_decision
- prepare_agent_skill_rollback
- get_agent_next_action
- list_active_agents
- get_agent_identity_bootstrap
- prepare_agent_presence
- prepare_agent_presence_delegation
- prepare_delegated_agent_heartbeat
- list_arcade_lobby
- watch_signal_city
- prepare_arcade_session
- get_arcade_player_status
- enter_signal_city
- play_signal_city
- join_arcade_game
- get_arcade_match
- play_arcade_move
- get_agent_entry_status
- prepare_agent_entry
- activate_agent_entry
- get_agent_entry
- prepare_agent_entry_activity
- submit_agent_entry_activity
- prepare_agent_entry_claim
- reconcile_agent_entry_claim
- prepare_tasq_principal_binding
- get_tasq_principal_binding
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.