Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Taste

REMOTE · API.HUMANTASTE.APP · SCANNED SEP 24

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

0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3462 tokens (~173/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Taste MCP server?

Taste is a hosted endpoint at https://api.humantaste.app/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.humantaste.app

# add to Claude Code
claude mcp add --transport http app-humantaste-taste-mcp 'https://api.humantaste.app/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-humantaste-taste-mcp": {
      "url": "https://api.humantaste.app/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-humantaste-taste-mcp": {
      "type": "http",
      "url": "https://api.humantaste.app/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-humantaste-taste-mcp]
url = "https://api.humantaste.app/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-humantaste-taste-mcp": {
      "type": "remote",
      "url": "https://api.humantaste.app/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-humantaste-taste-mcp --url 'https://api.humantaste.app/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-humantaste-taste-mcp:
    url: "https://api.humantaste.app/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-humantaste-taste-mcp": {
      "Transport": "http",
      "Url": "https://api.humantaste.app/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add app-humantaste-taste-mcp -t streamable-http -u 'https://api.humantaste.app/mcp/'
// mcp.json
{
  "mcpServers": {
    "app-humantaste-taste-mcp": {
      "type": "http",
      "url": "https://api.humantaste.app/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 78
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://api.humantaste.app/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=humantaste.app CN=YE2,O=Let's Encrypt,C=US 23 Aug 2026 21 Nov 2026 ECDSA 256 ECDSA-SHA384 5979a729bfd31d417b5352fbcd47f38ec48
SANs: *.humantaste.app, humantaste.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.humantaste.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
humantaste.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-frame-options SAMEORIGIN
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.humantaste.app/mcp/ Verified 200
http (plaintext) http://api.humantaste.app/mcp/ HTTPS enforced 301 https://api.humantaste.app/mcp/
MCP tools · 20 exposed · ~3,462 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
arbitrate_dispute ~307

Get an impartial human arbiter to decide whether a deliverable meets an agreed contract, or to settle disagreements between agents. Call when automated evaluation cannot determine quality, when two parties dispute fulfillment, or when subjective judgment is needed for contract assessment. Returns approve/reject verdict, reasoning, deliverable quality rating, contract alignment.

NameTypeReqDescription
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
contractDescriptionstringyesThe agreed contract or deliverable specification.
deliverablestringyesThe deliverable to assess. Text or a publicly accessible URL.
partyAPositionstringyesOne side of the dispute. The expert evaluates both impartially — order is arbitrary.
partyBPositionstringyesThe other side of the dispute.
termsHashstring–Terms anchor this dispute is bound to: keccak256 of the att/v1 terms manifest (as echoed from the x402 payment), or an opaque 32-byte document hash such as an LCP atrHash ("sha256:0x…" accepted). Per…
termsJsonobject–The full att/v1 terms manifest object. If provided it must be a valid manifest whose keccak256 equals termsHash.
termsUristring–Where the att/v1 manifest is hosted (https/ipfs). Convenience only — the hash is the identity.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

ask_a_human ~111

Ask a vetted human a plain-text question and get a plain-text answer back, usually within 30 minutes. Call when you need a quick human take, gut check, or local/lived-experience answer a model cannot reliably give. No scoring, no verdict, no certificate — just a direct human response. Returns the human's answer, plus an optional note on who answered.

NameTypeReqDescription
questionstringyesThe plain-text question for a human to answer. Anything you want a quick human take on.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

consult_domain_expert ~411

A vetted human in a named domain answers your question with first-hand knowledge. Pass `domain` to match an expert. Pass `parentSessionId` for follow-ups (cap 3). Returns answer, anonymised role, confidence, first-hand flag. Approved answers get an on-chain Taste cert. Listed domains: musician, cantor, writer, farmer, UX designer, Swedish archipelago resident, Stockholm local, Protestant priest, art curator, museum staff, culture journalist, food critic. Other domains: best-effort 24-48h.

NameTypeReqDescription
buyerWalletAddressstring–Optional. An EVM wallet address. If provided, you can later retrieve the deliverable on humantaste.app by connecting this wallet.
contextstring–Optional. Why you are asking and what you are working on (essay, research, product decision, etc.). Helps the expert frame their answer.
domainstringyesArea of expertise needed. Examples of currently listed domains: "Professional musician", "Cantor", "Writer", "Farmer", "UX designer", "Person living in the Swedish Archipelago", "Stockholm local", "P…
parentSessionIdstring–Optional. If present, this is a follow-up question to the same expert on an existing consultation. Up to 3 follow-ups per parent. Server validates the parent is completed and within the follow-up cap.
questionstringyesThe specific question to ask the expert. Be precise — the more specific the question, the better the answer.
referenceUrlsarray–Optional. Publicly accessible URLs the expert should review before answering.
requireListedDomainboolean–Optional. If true, the job is declined immediately when the domain is not on the supported listed-domain list, instead of being queued for best-effort sourcing.
NameTypeReqDescription
followupsRemainingnumber––
messagestringyes–
offeringstringyes–
parentSessionIdstring––
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

get_result ~110

Check the status of a previously submitted request. Returns the full structured deliverable once the expert (or order team) completes the work. Accepts a sessionId or an order reference code (think tank or illustration).

NameTypeReqDescription
referenceCodestring–An order reference code (TASTE-...) from a think tank or illustration order. Use this instead of sessionId to retrieve the result — it always returns the latest revision.
sessionIdstring–The session ID returned by a paid tool call.
NameTypeReqDescription
deliverableobject––
estimatedWaitMinsnumber––
messagestring––
reasonstring––
statusstringyes–
tipstring––

No examples provided.

list_expert_profiles ~77

Returns currently-available expert taglines (pseudonymous descriptions of the kinds of expertise on hand) plus the real-time count of online expert seats and estimated wait. Use this as a cheap pre-flight check before calling a paid tool. Taglines describe expertise kinds, not individuals: no per-expert PII is exposed. Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
estimatedResponseMinsnumberyes–
expertTaglinesarrayyes–
onlineExpertsnumberyes–
qualityPolicystringyes–
servicestringyes–
statusstringyes–

No examples provided.

list_offerings ~35

List all available human expert evaluation offerings with pricing, tool names, and whether each issues an on-chain Taste content certificate. Free.

Input schema present but exposes no named parameters.

NameTypeReqDescription
nextOpenAtstring|nullyes–
offeringsarrayyes–
onlineExpertsnumberyes–
operatingHoursstringyes–
servicestringyes–
statusstringyes–
usagestringyes–

No examples provided.

order_think_tank_session_30 ~231

Convene a think tank — a curated team of vetted human experts runs a 30-minute working session on your idea, problem, or decision and returns synthesized directions, ideas with rationale, and recommended next steps. Returns a sessionId + referenceCode immediately — poll get_result with either when the team is done. Includes 1 free revision turn: call request_think_tank_revision with the code to ask for adjustments.

NameTypeReqDescription
buyerWalletAddressstring–Optional. An EVM wallet address. If provided, you can later retrieve the deliverable on humantaste.app by connecting this wallet.
descriptionstringyesThe idea, concept, or problem you want the think tank to work on. Be specific about the goal and any constraints.
mediaUrlsarray–Optional. Publicly accessible URLs to reference material (images, decks, docs, links) the team should review.
requestedDeliverablesarray–Optional. What you want out of the session — e.g. "5 campaign concepts", "a positioning statement", "product name ideas".
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
referenceCodestringyes–
revisionTurnsnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

order_think_tank_session_60 ~231

Convene a think tank — a curated team of vetted human experts runs a 60-minute working session on your idea, problem, or decision and returns synthesized directions, ideas with rationale, and recommended next steps. Returns a sessionId + referenceCode immediately — poll get_result with either when the team is done. Includes 2 free revision turns: call request_think_tank_revision with the code to ask for adjustments.

NameTypeReqDescription
buyerWalletAddressstring–Optional. An EVM wallet address. If provided, you can later retrieve the deliverable on humantaste.app by connecting this wallet.
descriptionstringyesThe idea, concept, or problem you want the think tank to work on. Be specific about the goal and any constraints.
mediaUrlsarray–Optional. Publicly accessible URLs to reference material (images, decks, docs, links) the team should review.
requestedDeliverablesarray–Optional. What you want out of the session — e.g. "5 campaign concepts", "a positioning statement", "product name ideas".
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
referenceCodestringyes–
revisionTurnsnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

predict_audience_reaction ~159

Get a real human matching your target demographic to rate and react to your content as a representative audience member. Call before A/B test commits, before ad spend, or before distribution decisions. Returns overall rating, criteria scores, qualitative feedback, comparison notes.

NameTypeReqDescription
contentstringyesThe content to evaluate. Text or a publicly accessible URL for non-text media.
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
targetDemographicstringyesThe audience whose reaction matters. Required — load-bearing for expert matching. E.g. "crypto-native traders, 18-35", "non-technical SMB owners in the US", "casual gamers".
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

prepare_consult_domain_expert ~228

Get a humantaste.app URL where a human can place a consult_domain_expert order from a browser (Connect MetaMask, pay $15 USDC on Base, session created). Use this when your MCP client has no wallet integration (Claude Desktop, generic chat UIs). The URL is pre-filled with the brief you pass in; the user just opens it, reviews, connects a wallet, and pays. Returns the payment URL and the price. Free.

NameTypeReqDescription
contextstring–Optional. Why you are asking and what you are working on.
domainstringyesArea of expertise needed (e.g. Farmer, Protestant priest, UX designer, Stockholm local, art curator, museum staff, culture journalist, food critic).
parentSessionIdstring–Optional. If present, the URL submits a follow-up to an existing consultation (capped at 3 per parent, same expert).
questionstringyesThe specific question to ask the expert.
referenceUrlsarray–Optional. Publicly accessible URLs the expert should review.
NameTypeReqDescription
messagestringyes–
paymentUrlstringyes–
priceUsdcnumberyes–
tipstringyes–

No examples provided.

prepublish_review ~151

Get a vetted human expert to review your AI-generated content — text, images, videos, social posts, audio, or any media — for cultural sensitivity, brand safety, derivative risks, and audience appeal before you publish. Call before social posts, marketing campaigns, content distribution, or anywhere public-facing. Returns verdict (safe / needs_changes / do_not_publish), flagged issues, fix suggestions. Approved content receives a Taste content certificate on-chain, verifiable downstream.

NameTypeReqDescription
contentstringyesThe content to review. Text directly, or a publicly accessible URL for non-text media.
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

request_human_approval ~198

Pause your workflow for explicit human approval before executing a high-stakes action. Call before any irreversible action — large spend, on-chain transaction, public content publish, customer-facing decision. Returns approved/denied + reasoning. Approvals can be enforced on-chain via the Taste Gatekeeper hook for ACP and ERC-8183 jobs.

NameTypeReqDescription
actionDescriptionstringyesDescribe the action awaiting approval. Include numbers (amounts, recipients, URLs) the human needs to see.
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
stakesstringyesWhat kind of risk the action carries. Reversible: undoable. Irreversible: cannot be undone. Financial: moves value. Public: visible externally.
timeoutMinutesinteger–Maximum minutes to wait for a human response before returning denied_timeout. Default 30, max 120.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

request_illustration_revision ~117

Spend a free revision turn on a completed illustration order. Provide the reference code from your original order and describe the adjustments you want — the same illustrator revisits the brief and returns an updated deliverable. Poll get_result with the reference code to retrieve it. Free: no payment required, the turn is included with your order.

NameTypeReqDescription
adjustmentsstringyesWhat you want the illustrator to adjust, expand, or rethink.
referenceCodestringyesThe TASTE-... reference code returned when you placed the illustration order.
NameTypeReqDescription
messagestringyes–
referenceCodestringyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–
turnsRemainingnumberyes–

No examples provided.

request_think_tank_revision ~120

Spend a free revision turn on a completed think tank order. Provide the reference code from your original order and describe the adjustments you want — the same team revisits the brief and returns an updated deliverable. Poll get_result with the reference code to retrieve it. Free: no payment required, the turn is included with your order.

NameTypeReqDescription
adjustmentsstringyesWhat you want the team to adjust, expand, or rethink.
referenceCodestringyesThe TASTE-... reference code returned when you placed the think tank order.
NameTypeReqDescription
messagestringyes–
referenceCodestringyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–
turnsRemainingnumberyes–

No examples provided.

review_code ~206

Get a vetted human engineer to review your code, architecture, and design decisions — not just style, but correctness, security, and whether the structure will hold up. Call before you treat code as done: payment flows, auth, data handling, or any logic where a subtle bug is costly. Pass the code (inline or a publicly accessible URL) and what it is meant to do. Returns verdict (approved / needs_changes / reject), a correctness score, security findings, architecture notes, and suggested changes. Approved code receives a Taste content certificate on-chain.

NameTypeReqDescription
codestringyesThe code to review. Paste it inline, or pass a publicly accessible URL (e.g. a gist or raw file).
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
intentstringyesWhat the code is meant to do — the behaviour and constraints, plus any correctness or security concerns to focus on.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

review_content ~151

Get a vetted human expert to review your AI-generated content — text, images, videos, social posts, audio, or any media — for hallucinations, factual errors, weak parts, and domain mistakes. Call before publishing, before forwarding to another agent, or before acting on the content. Returns verdict, issues found, suggested improvements. Approved outputs receive a Taste content certificate on-chain you can attach as proof of human review.

NameTypeReqDescription
contentstringyesThe content to review. Text directly, or a publicly accessible URL for non-text media (images, video, audio, posts).
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

review_plan ~183

Get a vetted human to review your implementation or project plan before you build. Call right after you draft a plan for a non-trivial task — a human catches wrong assumptions, missing steps, architectural dead-ends, and risky sequencing while changes are still cheap, before any code is written. Pass the plan, the goal it serves, and any constraints. Returns verdict (proceed / revise / rethink), risks flagged, missing considerations, and sequencing notes. Approved plans receive a Taste content certificate on-chain.

NameTypeReqDescription
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
goalstringyesWhat the plan is meant to achieve — the objective or task it addresses.
planstringyesThe implementation or project plan to review. Paste the full plan — steps, approach, architecture, sequencing.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

verify_certificate ~157

Verify a Taste content certificate on-chain. Call when consuming content from another source that claims to be human-reviewed — returns reviewer domain, date, offering, verdict, validity, and an evidence tier: "evidence-verified" certs carry the reviewer's EIP-712 verdict signature + their Human Passport score attestation (EAS on Base), independently checkable without trusting Taste. Free. Use to build trust chains: agent A's output is reviewed → certificate issued → agent B consumes content and verifies cert before acting.

NameTypeReqDescription
certificateId––Numeric certificate id. Provide this OR contentHash.
contentHashstring–keccak256 hash of the content, as 0x-prefixed hex. Provide this OR certificateId.
NameTypeReqDescription
agentstring––
certificateIdstring––
contentHashstring––
domainstring––
evidenceobject––
foundbooleanyes–
issuedAtstring––
offeringTypestring––
reasonstring––
validboolean––
verdictstring––

No examples provided.

verify_external_source ~136

Have a vetted human expert verify whether an external source, project, or claim is trustworthy. Call when your output or planned action depends on an external claim you cannot independently verify (crypto project legitimacy, social media authenticity, source credibility, vendor due diligence). Returns verdict, red flags, positive signals, confidence score.

NameTypeReqDescription
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
subjectstringyesThe URL, project name, or claim to verify. Be specific (e.g. a URL, a project name + token address, or a verbatim claim).
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

verify_reasoning_chain ~143

Audit your step-by-step reasoning for mid-chain errors before producing the final answer. Call when stakes are high and your chain has 3+ steps — humans catch wrong intermediate steps that final-output checks miss (right-looking answers built on broken intermediate logic). Returns per-step verdict, flagged errors, suggested corrections. Approved chains receive a Taste content certificate on-chain.

NameTypeReqDescription
chainarrayyesOrdered array of reasoning steps. Each step: { step (number), reasoning (string), output (string), toolUsed? (string) }.
contextstring–Optional context. Use to clarify intent, constraints, audience, or anything that helps the expert evaluate.
NameTypeReqDescription
messagestringyes–
offeringstringyes–
priceUsdcnumberyes–
sessionIdstringyes–
statusstringyes–
tipstringyes–

No examples provided.

Common questions

What is the Taste MCP server?

Taste is an MCP server listed in the public MCP registry as app.humantaste/taste-mcp. Expert review for AI agents. On-chain proof of human review. This page covers its hosted endpoint (https://api.humantaste.app/mcp/).

Is the Taste MCP server safe to use?

Taste scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Taste MCP server expose?

Taste exposes 20 tools: list_offerings, list_expert_profiles, get_result, prepare_consult_domain_expert, request_think_tank_revision, and 15 more. Their descriptions and schemas cost roughly 3,462 tokens of context every time the server is loaded.

Does the Taste MCP server require authentication?

No. We connected to Taste without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Taste MCP server still maintained?

Taste is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.