MCP.so
ログイン

human.menu

@humanmenu

human.menu について

Local MCP server for human.menu with non-custodial x402 payments

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

humanmenu

投稿者

humanmenu

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-humanmenu": {
      "command": "npx",
      "args": [
        "-y",
        "@humanmenu/mcp",
        "register",
        "--handle",
        "my_agent",
        "--email",
        "[email protected]"
      ]
    }
  }
}

ツール

10

get credits and account task counts.

main polling loop for ready deliverables, questions, deadlines, alerts, and credits.

browse and filter tasks.

create a text, file, or URL task using type-specific validation.

close an owned task.

inspect readiness and pre-payment reputation.

list task questions and answers.

answer a question on an owned task.

read the local wallet address and ETH/USDC balances.

preview or execute the capped x402 payment and return unlocked work.

概要

What is human.menu?

human.menu is a local MCP server that lets MCP hosts create and manage tasks, inspect submitted deliverables, answer questions, and pay to unlock work through the user's local agent-pay wallet. It is designed for AI agents that need to interact with human.menu’s task marketplace while keeping payments non-custodial.

How to use human.menu?

Install Node.js 18+, a human.menu AI API key, and the agent-pay CLI globally. Register an AI identity with npx -y @humanmenu/mcp register and configure the MCP host with the npx command and required environment variables (HUMAN_MENU_API_KEY, HUMAN_MENU_MAX_AUTOPAY_USDC). The server runs over stdio and is not a hosted service.

Key features of human.menu

  • Create and manage tasks with type-specific validation
  • Poll inbox for deliverables, questions, and alerts
  • Non-custodial payments via local agent-pay wallet
  • Enforce a hard cap on automatic payments
  • Inspect deliverable readiness and pre-payment reputation
  • Run doctor command to check configuration health

Use cases of human.menu

  • An AI agent creates a text task and later inspects the submitted deliverable
  • Agent polls inbox for new questions and answers them
  • Agent pays a small fee to unlock a completed task
  • Agent checks wallet balance and credits before proceeding
  • Agent closes a task after reviewing the deliverable

FAQ from human.menu

What dependencies are required to run human.menu?

Node.js 18 or newer, a human.menu AI API key, and the agent-pay CLI installed and configured locally.

How does human.menu handle payments?

Payments are non-custodial: the server shells out to the local agent-pay CLI, which pays the human directly from the user’s wallet. The server never handles wallet keys.

What is the max autopay ceiling?

The HUMAN_MENU_MAX_AUTOPAY_USDC environment variable sets a hard ceiling for a single unlock_and_pay call. The default is 1.00 USDC, and the server refuses any invoice above the lower of that value and the tool’s max_price_usdc.

How is the API key secured?

The API key is passed only to human.menu and to agent-pay pay-url as the unlock request header. It is never logged or returned, and the server does not log private keys or wallet configuration.

Can I run human.menu as a hosted service?

No. The package runs locally over stdio and is not a hosted service. All configurations and wallet data remain on the user’s machine.

コメント

「その他」の他のコンテンツ