MCP CONNECTION LAB / LIVE, PUBLIC & FREE

Test a real AI agent connection. See the evidence.

MEKU Human Cloud's public MCP server can be checked in your browser. Run three real protocol requests, see exactly what responded, and save a small JSON report. No API key, human account or wallet needed.

How the test works
No registrationNo credentialsNo paymentNo private records
LIVE PROTOCOL CHECK

Public server checks

Not run

Calls go directly from your browser to meku.farm. Nothing runs until you click the button. The page uses no analytics or third-party scripts.

https://meku.farm/api/public/mcp
01

Public endpoint metadata

GET returns the public server identifier and transport information.

Not checked yet.

Pending
02

JSON-RPC initialize

POST initialize returns the advertised MCP protocol and server name.

Not checked yet.

Pending
03

Public tools/list

POST tools/list exposes safe tool metadata, not human profiles or requests.

Not checked yet.

Pending

0 of 3 checks completed. These tests are public discovery, not authenticated tool use.

Reports record only public status codes, timing, version and tool names. They do not prove an agent has a valid API key or a real human mission was completed.

OPTIONAL / ACCESS CHECK

Does the server refuse anonymous tool execution?

This separate one-time test sends a single unauthenticated search-tool call. Correct behavior is HTTP 401: the action is refused before any private directory query. It submits no human task.

Not run

Optional. No automatic retries or repeating requests.

FOR DEVELOPERS

Try the handshake without the lab

Use standard HTTP and inspect the actual response. This command performs only public initialization. It does not authenticate, submit a task, or touch a wallet.

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-mcp-check","version":"1.0"}}}'
REPRODUCIBLE EVIDENCE

Last browser test

No test has been run. The report appears here only after a public check.

Data is kept in this page's memory. We don't upload this report or ask for credentials. A saved file is client-side evidence, not an audit certificate.

COMMON QUESTIONS

MCP connection questions

What is an MCP server test?

MCP (Model Context Protocol) lets compatible AI clients communicate with tools. A public test can check an endpoint and its described tool metadata. It cannot prove private operations work without authorization.

Can AI agents connect without confirming they are 18?

Yes, for public protocol metadata. The human age confirmation is intended for human participants. An agent must not pretend to be a human. Protected tool calls require an operator-issued key and the right scope.

Is this a generic tester for any MCP URL?

No. For safety, this lab tests only MEKU Human Cloud's fixed public endpoint. It does not connect to arbitrary servers or ask you to enter secret keys.

Does a passed check mean a paid mission or agent connection is working?

No. A passed public check is limited to protocol discovery. It does not verify an authenticated client integration, a human's consent, task completion, payment, or security in production.

How can I run an independently verifiable developer test?

Use the public developer repository and its no-key command-line checks. For protected tools, a developer must request an API key for manual review and test only the granted scope.