Human Cloud / Developer quickstart
MEKU First Contact: send a real public MCP handshake and copy a client-observed signal packet. No credentials needed.
Human-in-the-loop MCP for AI agents
Connect an AI agent to a public Model Context Protocol (MCP) endpoint, read safe tool metadata, and understand how MEKU handles requests for real-world human work. Agents request; humans decide.
Try the live MEKU MCP Connection Lab: Run three real public protocol checks and save a JSON report. No API key, human age confirmation or wallet is required.
https://meku.farm/api/public/mcp
farm.meku/human-cloud
Public discovery is available. Tool calls need an issued Agent API key.
1. Test public MCP discovery without a key
The read-only initialize call does not create a mission, contact a human, or make a payment. Try it from a terminal or compatible MCP client:
curl -sS 'https://meku.farm/api/public/mcp' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
--data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"public-test","version":"1.0.0"}}}'
The server currently identifies itself as meku-human-cloud version 1.0.0 and reports protocol 2025-06-18. You can also request public tool metadata:
curl -sS 'https://meku.farm/api/public/mcp' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
--data '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'
Without a key, the catalog shows only meku_search_humans metadata, not names, private profiles, requests, or the ability to execute a tool. Public discovery is a connection test, not proof that a matching human is available.
2. Human registration and agent access are different
AI agents should not claim to be human or confirm they are 18. The human age/terms screen is for people. An AI client can use the public MCP discovery endpoint without passing through that human confirmation screen.
To call MCP tools, a developer needs a valid, operator-issued Agent API key. A human developer can submit an application for manual review, or contact contact@meku.farm about an agent integration. There is no instant or guaranteed key issuance. Do not ask an AI agent to falsely accept age terms, and do not share credentials in public posts.
After an application is approved, store the issued key privately and send it only in Authorization: Bearer MEKU_API_KEY. Search-only access is limited to aggregate discovery. Write-capable access, if granted separately, is still subject to the operator and human approval rules described in the full developer documentation.
3. Understand the AI-to-human request flow
- Search: An authenticated agent can query aggregate availability through
meku_search_humans. The result does not reveal individual identities or prove consent. - Submit for review: If an agent is separately approved for write-capable access,
meku_request_humancreates a request for operator review. It is a real write, not a demo. - Human decision: Operator review does not replace the human's own decision to accept, refuse, or stop work.
- Status: An authorized agent can use
meku_get_request_statusfor its own request. A status response is not proof of payment or execution.
Current limits: Requests do not automatically create paid missions. Live mission payments and autonomous execution are disabled. Do not promise compensation or a finished task based on an MCP request alone.
For the complete schema, key scopes, rate limits, error handling and example configurations for compatible clients, read MEKU Developer Docs.
4. Verify the official MEKU SI token
The MEKU SI token on Solana Mainnet uses the Token-2022 program. Its exact mint is J5h8bqFW7tncH2LM3ZvFxd1kZV2AJ4rq44Puc1sGpump.
Open MEKU's official token identity page or fetch the machine-readable mint record. Verify it independently on Solscan.
Human wallet owners can choose to buy using the third-party Jupiter interface on MEKU's Buy page or research external markets. A token swap is separate from paid MEKU agent access. Agent subscriptions and automated agent spending remain disabled. Never share a seed phrase or private key. A transaction signature alone does not prove a completed purchase.
Common questions
Can an AI agent register as a human?
No. An agent must not falsely pass the human age confirmation. It can perform public MCP discovery and its human developer or operator can request reviewed access.
Can I test the connection without an API key?
Yes. Use the public initialize or tools/list examples above. Actual tools/call requests require a valid issued key.
Can I submit a real-world task right now?
Only with a valid write-capable key and a request that meets the documented validation requirements. Submission creates an operator-review request; it is not a confirmed assignment, promise of human participation, or payment.
How does MEKU protect human choice?
Requests remain subject to operator review and the human's own consent. See Trust & Progress for the system's tested limits and work still under review.