Taste

What Taste MCP server does

Taste MCP server connects AI agents with paid human review through MCP and x402. Humans can assess text, images, video, audio, and social posts, although the specific input accepted depends on the selected offering. The service also supports expert working sessions, contract-related arbitration, audience feedback, and explicit approval before an irreversible workflow action.

Several review tools issue a Taste content certificate. Certificates are recorded on Base and can later be checked with the read-only verify_certificate tool. The service also includes verify_external_source for evaluating whether a source, project, or claim is trustworthy.

The Taste MCP server is a fit for workflows where an automated result needs an independent human check, a decision requires approval, or downstream agents need to verify that review occurred.

How it works

The hosted endpoint is available at https://api.humantaste.app/mcp/ using Streamable HTTP and MCP 2025-06-18. There is no local server package to install, and the README specifies no authentication or API key requirement.

Free calls include list_offerings, list_expert_profiles, get_result, and verify_certificate. list_offerings reports prices, certificate availability, and the current operating-hours state. list_expert_profiles returns aggregate availability and estimated response times without personal information. Long-running work can be checked by session ID or order reference code through get_result.

Paid calls initially return HTTP 402 with payment requirements. The caller signs an EIP-3009 USDC transfer on Base mainnet and retries the same request with an X-Payment header. Listed paid calls cost between $1 and $15. Evaluation calls commonly take 5–30 minutes, while a think tank session may take up to 24 hours.

Think tank orders return a TASTE-XXXX-XXXX-XXXX reference code. The service documents contextual revision helpers for think tank and illustration work; available tools are dynamic, so clients should query tools/list for the current surface.

Setup and configuration

Configure an MCP client to use the Streamable HTTP endpoint rather than installing a local command. A minimal request can call list_offerings with JSON-RPC over HTTP and accepts either JSON or the text/event-stream response format.

Before using paid operations, the calling workflow needs a way to hold and authorize USDC on Base mainnet. Payment is made per call through x402; the material does not specify an environment variable, API key, or persistent account configuration.

The free tools can be used to inspect current offerings and availability before placing an order. Use the returned session ID or reference code to poll asynchronous work, then use certificate verification when a completed review provides one.