English Français العربية

Taste

Official registry AI and agents

Expert review for AI agents. On-chain proof of human review.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http taste 'https://api.humantaste.app/mcp/'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "taste": {
            "type": "http",
            "url": "https://api.humantaste.app/mcp/"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Taste
  2. what
  3. connect
  4. tools
  5. example
  6. compliance
  7. links

Taste

Expert review for AI agents. On-chain proof of human review.

This is the public manifest repository for the Taste MCP server. The server is hosted — there is nothing to install. server.json is the discovery manifest consumed by MCP registries; the server source is maintained privately.

what

Pay-per-call human work for AI agents over MCP + x402. Vetted humans review an AI agent's output across any media (text, images, video, audio, social posts), audit reasoning chains, run prepublish safety checks, gate high-stakes actions for human approval, and convene curated expert teams for working sessions on ideas, problems, or decisions. Approved outputs receive a Taste content certificate recorded on Base — any downstream agent can verify the review.

connect

MCP endpoint:  https://api.humantaste.app/mcp/
Transport:     Streamable HTTP (MCP 2025-06-18)
Payment:       x402, USDC on Base mainnet, $1.00–$15.00 per paid call
Free tools:    list_offerings, list_expert_profiles, get_result, verify_certificate
Typical wait:  5–30 min for evaluation calls; up to 24h for a think tank session

No authentication, no API key. Paid tools answer an unauthenticated call with HTTP 402; sign an EIP-3009 USDC transfer and retry.

tools

Free (no payment, no session):

ToolPurpose
list_offeringslist offerings, prices, certificate flag, operating-hours state
list_expert_profilesaggregate availability + estimated response time, no PII
get_resultpoll session status by sessionId or order reference code; returns the full deliverable when complete
verify_certificateread-only Taste content certificate lookup on Base, rate-limited 60/min/IP

Paid (x402 — USDC on Base):

ToolPricePurpose
verify_external_source$1.00verify whether an external source, project, or claim is trustworthy
review_content$1.00review AI-generated content for hallucinations, factual errors, domain mistakes — issues a certificate
verify_reasoning_chain$1.00audit a step-by-step reasoning chain for mid-chain errors — issues a certificate
prepublish_review$1.00review content for cultural sensitivity, brand safety, derivative risk before publishing — issues a certificate
predict_audience_reaction$1.00a human matching a target demographic rates and reacts to content
arbitrate_dispute$1.00an impartial human arbiter decides whether a deliverable meets a contract
request_human_approval$1.00pause a workflow for explicit human approval before an irreversible action
order_think_tank_session_30$5.00convene a curated team of human experts for a 30-min working session on an idea, problem, or decision; returns synthesized directions (1 free revision turn)
order_think_tank_session_60$15.00as above, 60-min session (2 free revision turns)

Each think tank order returns a TASTE-XXXX-XXXX-XXXX reference code. Two contextual helper tools — request_think_tank_revision and request_illustration_revision — spend a free revision turn against that code.

The live tool list is authoritative — server.json sets tools: "dynamic", so MCP clients call tools/list against the endpoint for the current surface.

example

curl -X POST https://api.humantaste.app/mcp/ \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"list_offerings","arguments":{}}}'

Paid calls return HTTP 402 with an X-Payment-Requirements header (base64 JSON). Sign EIP-3009 transferWithAuthorization for USDC on Base, then retry the same request with an X-Payment header.

compliance

EU AI Act Article 50(2) exempts AI-generated content from mandatory AI-disclosure labels when it has undergone human review or editorial control. Taste content certificates are the on-chain audit trail for that exemption.

Frequently asked questions

What is Taste?

Expert review for AI agents. On-chain proof of human review.

How do I install Taste?

It runs as a remote server. In Claude Code: claude mcp add --transport http taste 'https://api.humantaste.app/mcp/'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Taste need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Taste open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Taste?

It is published by with0utwhy. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.