Does the Tastewise MCP server require authentication?

Yes. When we connected to its endpoint without credentials on 2026-09-20, it returned HTTP undefined.

Can I grant read-only access to the Tastewise MCP server?

No. It publishes [], which does not separate reading from writing, so granting access grants both.

Can the Tastewise MCP server be self-hosted?

Not from the registry record. No installable package is declared, so the vendor-hosted endpoint is the only documented option.

Vendor-published

Tastewise MCP server

Food and beverage consumer intelligence, exposed to AI assistants over MCP. Access is arranged through a sales conversation rather than self-serve documentation.

Not listed in the public MCP Registry.

Not listed in the public MCP Registry. We enumerated the registry to cursor exhaustion on 2026-09-20 (337 pages, 33,644 records) and found no Tastewise entry.

Tastewise operates MCP Compare.

This entry is evaluated against the same published criteria as every other server, using only evidence any reader can reproduce. It is currently the least documented profile on the site. See about and ownership.

Tastewise exposes food and beverage consumer intelligence, exposed to AI assistants over MCP. Access is arranged through a sales conversation rather than self-serve documentation. Its apex domain publishes OAuth discovery metadata, so an MCP client can find and authorise against it without documentation. It advertises a single scope, ["mcp"], which does not separate reading from writing — so read-only access cannot be granted. Only 5 of 18 evaluation criteria are documented; the remaining 13 are not published anywhere public. Last checked 2026-09-20.

Add to comparison Vendor documentation

Identity and maintenance

Publisher and version information
Registry name	No registry entry
Publisher domain	tastewise.io
Maintainer type	Vendor-published Not listed in the public MCP Registry. We enumerated the registry to cursor exhaustion on 2026-09-20 (337 pages, 33,644 records) and found no Tastewise entry.
Latest version seen	Not published
Last checked	2026-09-20
Last changed	2026-09-20 Separate from “last checked”: we check far more often than anything changes.

Enterprise evaluation

Every row below exists whether or not we found an answer. Expand any row to see the exact source and the date. Unknown means undocumented, never unsupported.

Enterprise evaluation criteria for Tastewise
Access and authentication
Authentication required Whether the hosted endpoint accepted a connection with no credentials when we checked.	Yes We checked checked 2026-09-20 An unauthenticated request to https://tastewise.io/wp-json/mcp/mcp-oauth-server is rejected; the apex domain publishes RFC 9728 protected-resource metadata pointing at it. Unauthenticated connection attempt — https://tastewise.io/wp-json/mcp/mcp-oauth-server
OAuth 2.1 authorization Whether the server publishes OAuth discovery metadata a client can follow automatically.	Yes We checked checked 2026-09-20 https://tastewise.io/.well-known/oauth-protected-resource -> 200, naming authorization server https://tastewise.io OAuth Protected Resource Metadata — https://tastewise.io/.well-known/oauth-protected-resource
Dynamic client registration Without it, an IdP administrator must register a client by hand before anyone can connect.	Not documented We checked checked 2026-09-20 authorization-server metadata published, but no registration_endpoint Authorization Server Metadata — https://tastewise.io/.well-known/oauth-authorization-server
Documented scopes	Yes mcp We checked checked 2026-09-20 "scopes_supported": ["mcp"] OAuth Protected Resource Metadata — https://tastewise.io/.well-known/oauth-protected-resource
Read and write are separate scopes A single opaque scope means read-only access cannot be granted: approving access approves everything.	No We checked checked 2026-09-20 scopes_supported is ["mcp"] -- a single scope covering both reading and writing, so read-only access cannot be granted OAuth Protected Resource Metadata — https://tastewise.io/.well-known/oauth-protected-resource
Deployment and transport
Streamable HTTP transport	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
SSE transport	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Vendor-hosted endpoint Data leaves your network. Where it goes is a question for the vendor's documentation.	Yes We checked checked 2026-09-20 "resource": "https://tastewise.io/wp-json/mcp/mcp-oauth-server" -- a vendor-operated endpoint OAuth Protected Resource Metadata — https://tastewise.io/.well-known/oauth-protected-resource
Self-hostable package A published npm, PyPI, container or bundle artifact you can run inside your own perimeter.	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Supply chain
Public source repository	Not documented Vendor checked 2026-09-20 The public Tastewise GitHub organisation exposes no MCP server implementation. GitHub organisation — https://github.com/tastewise
Open-source license	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Repository actively maintained	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Package deprecated	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Secret inputs marked as secret Credential-shaped inputs the publisher did not flag as secret may be logged by a client.	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Documented controls
Audit logging documented	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Access controls documented	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Data residency documented	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations
Data retention documented	Not documented Vendor checked 2026-09-20 No public Tastewise page documents this. Access is gated behind a sales conversation. Tastewise public documentation — https://tastewise.io/integrations

What remains unknown

13 of 18 criteria are undocumented. These are the questions to put to the vendor — not conclusions about the product.

Dynamic client registration — authorization-server metadata published, but no registration_endpoint
Streamable HTTP transport — No public Tastewise page documents this. Access is gated behind a sales conversation.
SSE transport — No public Tastewise page documents this. Access is gated behind a sales conversation.
Self-hostable package — No public Tastewise page documents this. Access is gated behind a sales conversation.
Public source repository — The public Tastewise GitHub organisation exposes no MCP server implementation.
Open-source license — No public Tastewise page documents this. Access is gated behind a sales conversation.
Repository actively maintained — No public Tastewise page documents this. Access is gated behind a sales conversation.
Package deprecated — No public Tastewise page documents this. Access is gated behind a sales conversation.
Secret inputs marked as secret — No public Tastewise page documents this. Access is gated behind a sales conversation.
Audit logging documented — No public Tastewise page documents this. Access is gated behind a sales conversation.
Access controls documented — No public Tastewise page documents this. Access is gated behind a sales conversation.
Data residency documented — No public Tastewise page documents this. Access is gated behind a sales conversation.
Data retention documented — No public Tastewise page documents this. Access is gated behind a sales conversation.

Turn these into a vendor questionnaire

Questions people ask

Does the Tastewise MCP server require authentication?: Yes. When we connected to its endpoint without credentials on 2026-09-20, it returned HTTP undefined.
Can I grant read-only access to the Tastewise MCP server?: No. It publishes [], which does not separate reading from writing, so granting access grants both.
Can the Tastewise MCP server be self-hosted?: Not from the registry record. No installable package is declared, so the vendor-hosted endpoint is the only documented option.