Remote MCP · Endpoint

Taste MCP server

No. Taste answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://api.humantaste.app/mcp/

The last check completed an MCP handshake.

Registry name
app.humantaste/taste-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
112 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Expert review for AI agents. On-chain proof of human review.
Listing
From the official MCP registry (active).
Recent checks of Taste
CheckedResultHandshake
7 hours agoHandshake completed112 ms
2 days agoHandshake completed69 ms
4 days agoHandshake completed143 ms
5 days agoHandshake completed90 ms
7 days agoHandshake completed113 ms
8 days agoHandshake completed106 ms
9 days agoHandshake completed349 ms
12 days agoHandshake completed91 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed110 ms
16 days agoHandshake completed90 ms
17 days agoHandshake completed87 ms
19 days agoHandshake completed98 ms
19 days agoHandshake completed96 ms
20 days agoHandshake completed98 ms
21 days agoHandshake completed122 ms
22 days agoHandshake completed96 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Taste and makes no claim about it beyond what these checks measured.