DEVELOPER
DOCUMENTATION
Public search-tool metadata. Every tool call needs a key; request submission and status need a normal key. Agents request. Humans decide.
REQUEST ACCESSAI agents are not human applicants. For public MCP connection tests, key review, and the correct agent onboarding path, read the AI agent MCP quickstart. An agent must not confirm a human age requirement.
Run our free MCP connection lab. Three real public checks, a downloadable JSON report, and no account or API key. You can also send a First Contact signal and copy a public handshake snapshot for another developer to check.
01 / CONNECTION & SAFE DISCOVERY
Endpoint: https://meku.farm/api/public/mcp. Official registry name: farm.meku/human-cloud.
Without an Authorization header, initialize, initialized notifications and tools/list expose public metadata only. The public catalog contains only meku_search_humans, with no directory records, requests or status. Every tools/call—including search—and every other method require an operator-issued, valid, unrevoked Agent API key in Authorization: Bearer meku_…. Supplied invalid credentials are rejected, not treated as anonymous. Website sign-in is not a substitute. Apply through AI ACCESS; issuance is manual. Keep your key private, outside browser code, repositories and public examples.
Read-only keys discover and dispatch only meku_search_humans through MCP; request submission and status are unavailable. Normal valid keys retain all three tools, with status scoped to their own requests. Existing REST request-read permissions are unchanged.
Key lifecycle: only newly issued search-only keys expire exactly 30 days from trusted server issuance. Developer-application approval issues a search-only key; explicit operator search-only issuance follows the same policy. Search-only tokens carry their expiry epoch in a versioned format (meku_exp1_…) whose one-way verifier binds that epoch, so the expiry cannot be extended by tampering; no database schema change is involved. The operator sees the exact expiry beside the plaintext key, shown only once. Existing keys keep their plain-hash verifiers and remain valid until revoked, subject to their existing scopes and rates; writable issuance remains without expiry. Expired, malformed or tampered search-only tokens return 401 before rate limiting for MCP and REST.
The example expects MEKU_API_KEY to be supplied privately in your local environment. It reads aggregate availability; it creates no review request, mission or payment. Authenticated calls still consume the key’s shared REST/MCP rate limit, including initialization, discovery, retries and failed calls.
export MEKU_MCP_URL="https://meku.farm/api/public/mcp"
# Supply MEKU_API_KEY privately; never paste it into shared code.
curl -X POST "$MEKU_MCP_URL" \
-H "Authorization: Bearer $MEKU_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"meku_search_humans","arguments":{"skills":["photography"]}}}'For public metadata discovery, send these JSON bodies to the same endpoint with Content-Type: application/json and no Authorization header. Include a valid key to discover that key’s permitted tools:
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"your-client","version":"1.0.0"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":2,"method":"tools/list"}The handler returns protocol 2025-06-18, server meku-human-cloud version 1.0.0, and tools.listChanged: false. It does not negotiate the requested protocol or track initialization sessions. Initialized notifications return 202 with no body; authenticated ping returns an empty result. GET returns unchanged public static connection metadata, not a tool catalog or SSE stream. Responses are JSON; no session ID or server event stream is implemented. Compatibility with every MCP client is not guaranteed.
Connect from an MCP client
MEKU Human Cloud uses Streamable HTTP at https://meku.farm/api/public/mcp. Discovery metadata is public, but every tool call needs your MEKU Agent API key in the Authorization header. It supports initialize-based clients (protocol 2025-06-18). Keep your key in an environment variable, never in a file you commit or share.
export MEKU_API_KEY="meku_your_key_here"Cursor: add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"meku-human-cloud": {
"url": "https://meku.farm/api/public/mcp",
"headers": {
"Authorization": "Bearer ${env:MEKU_API_KEY}"
}
}
}
}Cursor resolves ${env:MEKU_API_KEY} from the environment it was launched in. Cursor asks for approval before each tool call by default; keep that on.
Claude Code: run in your terminal:
claude mcp add --transport http meku-human-cloud https://meku.farm/api/public/mcp \
--header "Authorization: Bearer $MEKU_API_KEY"Key-storage warning: this terminal command expands the variable before Claude Code runs and stores the resulting key in its local configuration. Do not commit or share that configuration. Prefer the environment-backed .mcp.json example below to avoid storing the key itself.
Then check the connection with claude mcp get meku-human-cloud, or /mcp inside Claude Code. If you configure it in .mcp.json instead, include "type": "http":
{
"mcpServers": {
"meku-human-cloud": {
"type": "http",
"url": "https://meku.farm/api/public/mcp",
"headers": { "Authorization": "Bearer ${MEKU_API_KEY}" }
}
}
}Recommended first test (read-only): ask your agent to call meku_search_humans (for example with no arguments, or with skills set). It returns aggregate availability only, with no names or profiles. meku_request_human is a real write that goes to operator review, so don't use it as a connectivity test.
Troubleshooting: a 401 with "Missing API key" means the header didn't reach the server. Check that the variable is set in the shell that launched your client and that the value starts with meku_. "Invalid API key" or "revoked" means the key itself isn't valid. Apply at /ai-access.
Compatibility: the configuration syntax follows the official Cursor and Claude Code documentation. MEKU returns protocol 2025-06-18 without negotiation; these specific clients have not been verified end-to-end with an issued key. The server's transport limitations are described above.
02 / THE THREE CURRENT TOOLS
meku_search_humans
Advertised inputs: optional country: string, region: string and skills: string[]. Country and region must be strings of at most 80 characters; skills must be an array of at most 10 strings, each at most 40 characters. Invalid types, over-limit filters and unknown search properties are rejected before directory reads. Valid strings are trimmed and empty skills dropped. Every requested skill must match on the same public, listed, explicitly online human, case-insensitively with surrounding skill whitespace ignored. Empty skills means no skill filter. A supplied country is resolved to one canonical English country name through a fixed alias table (names, common variants and ISO 3166 codes: USA, US and United States are one country) and compared with saved profile countries resolved the same way; an unrecognised country matches nothing and is never guessed. A supplied region requires exact equality after trim/case normalization against saved profiles. Missing or blank saved regions are unknown and excluded when region is requested; omitting region leaves the country/skill behavior unchanged. Counts use self-reported profile country/region/skills, not verified live location or promised availability. An exact-filter zero does not prove nobody is available. Counts do not confirm availability or human consent.
Returns listed_humans, online_humans, matching_humans, matched_skills, countries,counts_complete, scanned_profile_limit, and a consent/privacy note. Only explicitly online public/listed profiles count as available; busy or unknown statuses are excluded. A stable scan covers at most 500 saved profiles. If counts_complete is false, all counts and country lists cover only that scanned group, not the whole network. Countries are narrowed to the people matching the requested skills and location; listed/online totals cover the scanned directory. Matched skills echo the requested filters, not proof that a match exists. No names, profile IDs or contacts are returned.
The public capability feed GET /api/public/seek-capabilities uses the same label normalisation (normalization: "meku-labels-v1"). Its countries are canonical English names only; saved values that are empty, currency codes or not recognisable as a country are counted in unrecognized_country_profiles instead of being listed. skill_categories are self-reported labels, lower-cased and de-duplicated exactly as entered, with no spelling correction; each human counts at most once per country and per skill. Stored profiles are not changed.
Error: Could not load availability. Please try again.
meku_request_human
Real write, not a dry run. Creates an execution request for operator review, not a mission or payment. Review does not replace human consent. Humans can accept, reject or stop missions.
Advertised required fields: title: string, action: stringand description: string. Skills are optional. Optional strings: country, region, deliverable, timeframe, budget_text and idempotencyKey. Optional booleans: travel_required and equipment_required.
Shared REST/MCP validation rejects wrong JSON text types rather than turning numbers or objects into task text. Text is trimmed and capped before minimum checks: title 4–120 characters; action 4–200; description 20–2000. Skills are optional and default to an empty array; at most 10 nonblank skills of 40 characters each are saved. Optional caps: country/region 80, deliverable 300, timeframe 120, budget 80. Blank optional text becomes null. Travel and equipment requirements must be real JSON booleans, not strings such as "true".
Field mapping now matches the published tool schema: budget_text, travel_required and equipment_required are passed to the shared request validator. They cannot quietly disappear from a submitted task. The advertised lengths now match the shared title, action and description limits, and skills are not required. Do not send camelCase aliases to schema-based MCP clients. An optional contact field exists in the shared REST validator but is not advertised by this MCP tool; do not rely on sending it to MCP.
Optional idempotencyKey supports 1–80 letters, digits, dots, underscores, colons or dashes. An omitted key means no retry protection; an explicitly empty or whitespace-only key is rejected. The key is scoped to the submitting agent key. An identical normalized task with the same key returns the saved request and deduplicated: true. Reusing that key for a different task returns a conflict instead of treating it as the same work. Database failures during saved retry checks fail closed rather than creating another request. This is not proof that every network failure was delivered exactly once.
Success fields: id, status, created_at, note, plus deduplicated: true on a recognized retry. New requests start as submitted.
Validation errors: Title must be at least 4 characters; Describe the physical-world action; Description must be at least 20 characters; Text fields must be strings; Travel and equipment requirements must be booleans. An optional REST contact must be a valid HTTPS or mailto URL. Invalid retry keys are rejected, and a changed payload using an existing retry key returns a conflict. Storage failures never report success.
meku_get_request_status
Required id: string, using the ID returned from submission. Reads only requests belonging to the exact submitting API key; another key on the same account does not grant access. The current format check accepts 36 hexadecimal/hyphen characters, not a full canonical UUID check.
Returns {request: {...}} with id, title, action, description, country, region, skills, deliverable, timeframe, budget_text, travel_required, equipment_required, requester_kind, status, created_at. No contact, owner/key identifiers or operator notes are included.
Status values: submitted, under_review, approved, rejected, cancelled. Errors: Request not found. for malformed, absent or cross-key requests; Could not load the request. for query failures.
03 / RESPONSE & ERROR CONTRACT
All three advertised input schemas disallow additional properties. Search enforces its bounded country/skills schema; request submission and status do not yet enforce their complete advertised schemas and still ignore unknown properties. Present tool arguments must be objects, never arrays or null. No output schema or structuredContent is supplied.
// Success: HTTP 200; parse content[0].text as JSON.
{"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"<JSON-serialized tool result>"}]}}
// Tool failure: also HTTP 200; inspect isError.
{"jsonrpc":"2.0","id":1,"result":{"content":[{"type":"text","text":"Request not found."}],"isError":true}}
// Authentication failure:
{"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Invalid API key."}}- 401 / -32001: missing or malformed key, unverifiable key, invalid key, revoked key. Expired search-only keys (“API key has expired.”) and malformed or tampered exp1 tokens are also rejected before rate limiting.
- 429 / -32001: “Could not check rate limit. Try again.”, “Could not record API key activity.” or “Rate limit reached. Limit: {per_minute} per minute, {per_day} per day.” Limits are operator-configured, fixed minute/day windows and shared across REST/MCP. No Retry-After header is supplied.
- 400 / -32700: “Parse error: body must be valid JSON.”
- 400 / -32600: “Invalid JSON-RPC 2.0 request.”
- 413 / -32600: request body exceeds the 64 KiB UTF-8 stream limit.
- 400 / -32602: invalid tool parameters or search filters.
- 200 / -32601: “Method not found: {method}”.
- 200 / -32602: “Unknown tool: {name}”.
When an Authorization header is supplied, authentication and the existing key-bound rate check precede JSON parsing. Without that header, only metadata discovery is public; other methods return 401. Authentication/rate failures use id:null and a Bearer challenge header. Send one JSON-RPC object per POST; batches and null return an invalid-request error. Unexpected internal failures are not reliably converted into JSON-RPC errors. Requests require a string or safe-integer, non-null ID; present params must be objects. Initialized notifications omit the ID and receive empty 202 responses; the harmless legacy initialized alias/null-ID form remains accepted, never for tools. The body limit counts actual streamed bytes regardless of Content-Length. Protocol rules follow the 2025-06-18 MCP basic specification; no transport session or SSE stream is implemented.
04 / OPERATIONAL STATUS & LONG-TERM VISION
Unsigned SIGNAL v0.1 website bridge: the authenticated website matcher builds a short-lived, unsigned intent from normalized skills, country and region only, then projects filters onto current directory counts. Every skill must match on the same human; a supplied country matches saved profile countries by canonical country name (fixed alias table, unrecognised values match nothing) and a supplied region matches exact saved profile values after trim/case normalization. Missing or blank regions do not match a requested region. Self-reported profile data is not verified live location or promised availability; an exact-filter zero does not prove nobody is available. Directory rows are not signed capabilities, and signed SIGNAL compatibility, publisher trust and ranking are not checked. No live feed or authority is created. MCP search also supports the bounded optional region filter; key permissions are unchanged. Trusted signed publisher/feed/checkpoint verification remains a separate gap.
Guided human-task intake: Propose a human task, review the draft and explicitly submit. Submitted/under-review/approved/declined request states do not imply human acceptance, execution or funding. Humans independently accept, refuse or stop missions.
Data boundaries: first-visit consent records necessary-only storage while no optional tracking provider is configured. Analytics, marketing and identifiable-content model training remain off. NEURA is an experimental, non-autonomous observatory of recorded network state and bounded benchmarks, not a reader of profiles, messages, task content, proof, locations or wallets. No new feed is enabled; approved feed fields, purpose, access and retention require an owner decision. SEEK’s radar is illustrative, not live data, ranking or signed-feed matching. Exact matching of saved regions is available, but is not verified live location or human acceptance.
Source-tested and partially hosted-checked: discovery metadata is public; aggregate search requires a key, and request submission and per-key status require a writable key. Read-only hosted checks confirm that anonymous private Agent Requests are denied and public MCP GET metadata is reachable. Authenticated, cross-account and complete mission flows still need independent hosted verification. No MCP tool automatically hires a human, creates a mission, funds work or retrieves proof.
Planned API, not callable through this MCP: mission creation, funding and proof retrieval are not tools exposed by this MCP server. Payment actions are unavailable in this preview and hosted payment settings are unverified. This MCP server exposes no financial operation.
In the reviewed payment design, MEKU SI on Solana Mainnet is the exclusive Human Cloud transactional currency; mission checkout, payouts and refunds are switched off in this release. SOL covers network fees and token-account rent only. MEKU SI is not an investment product. Official contract:
J5h8bqFW7tncH2LM3ZvFxd1kZV2AJ4rq44Puc1sGpump
Universal high income is MEKU’s long-term vision for expanding access to voluntary, useful work—not guaranteed earnings, available missions or automatic payments.
BACK TO AI ACCESS