Percolate
REMOTE · MCP.PERCOLATEAPP.COM · 2 COMPONENTS
Search the Percolate specialty coffee database: 1,100+ coffees with brew recipes and pairings.
Available components
Last scanned (3 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 822 tokens (~102/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Server version: 1.0.0 → 1.0.2 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 80. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 70. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://mcp.percolateapp.com/?src=registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.percolateapp.com | CN=YE1,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6867b1cee8163604d273188c2139d806294 |
| SANs: mcp.percolateapp.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 mcp.percolateapp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| percolateapp.com. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.percolateapp.com/?src=registry | Verified | 200 | |
| http (plaintext) | http://mcp.percolateapp.com/?src=registry | HTTPS enforced | 301 | https://mcp.percolateapp.com/?src=registry |
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 →
compare_coffees ~64
Side-by-side comparison: roast, body/acidity/sweetness, shared and distinct flavors, brew methods, and price difference.
| Name | Type | Req | Description |
|---|---|---|---|
| coffee_a | string | yes | First coffee — id or name |
| coffee_b | string | yes | Second coffee — id or name |
No output schema declared.
No examples provided.
dial_in_suggestion ~86
Brew guidance for a specific coffee: curated recipes from the Percolate catalog (ratio, temperature, grind) when available, or a roast-based starting point. Optionally scoped to your brew method.
| Name | Type | Req | Description |
|---|---|---|---|
| brew_method | string | – | Your brewer, e.g. 'V60', 'espresso', 'french press' |
| coffee | string | yes | Coffee id or name |
No output schema declared.
No examples provided.
find_similar ~72
Coffees with a similar profile to a given one, ranked by shared flavor notes and roast/body/acidity/sweetness proximity. Deterministic scoring over Percolate's structured tasting data.
| Name | Type | Req | Description |
|---|---|---|---|
| coffee | string | yes | Coffee id or name |
| limit | integer | – | Max results (default 5) |
No output schema declared.
No examples provided.
get_coffee ~85
Detailed record for one coffee: roast level, body/acidity/sweetness profile, flavor notes, suited brew methods, food and brew pairings, price, and retailer names with prices (no purchase links). Accepts a Percolate id or a name.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_name | string | yes | Coffee id or a name like 'Bean Box Taste of New York City' |
No output schema declared.
No examples provided.
get_recommendations ~141
Personalized coffee picks from flavor preferences (e.g. 'chocolate', 'berry', 'caramel'), a budget in USD, roast preference, and the brew gear you own.
| Name | Type | Req | Description |
|---|---|---|---|
| brew_method | string | – | What you brew with, e.g. 'espresso', 'pourover' |
| budget | number | – | Max price in USD per bag |
| limit | integer | – | Max results (default 5) |
| preferences | array | yes | Flavors the drinker enjoys, e.g. ['chocolate','caramel','nutty'] |
| roast_level | string | – | Roast level to filter by; omit to include all roasts |
No output schema declared.
No examples provided.
search_coffees ~191
Search 1,100+ curated specialty coffees in the Percolate database. Filter by category (espresso, single_origin, blend, decaf, dark), roast level, brew method, and price (USD). Returns tasting profiles, brew methods, and retailer names with prices (no purchase links).
| Name | Type | Req | Description |
|---|---|---|---|
| brew_method | string | – | e.g. 'espresso', 'pourover', 'french press', 'drip' |
| category | string | – | Coffee category to filter by; omit to search all |
| limit | integer | – | Max results (default 10, max 10) |
| price_max | number | – | Maximum price in USD |
| price_min | number | – | Minimum price in USD |
| query | string | – | Free-text search: coffee or roaster name |
| roast_level | string | – | Roast level to filter by; omit to include all roasts |
No output schema declared.
No examples provided.
trending_coffees ~67
Coffees Percolate users are adding to their collections most over the last 30 days (falls back to catalog popularity when live activity data is unavailable). The method used is labeled in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10, max 10) |
No output schema declared.
No examples provided.
what_to_brew ~116
A coffee suggestion for right now, based on time of day (evening picks lean decaf), mood, and the brew method you're using — scored over Percolate's tasting profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| brew_method | string | – | What you're brewing with |
| mood | string | – | e.g. 'need focus', 'lazy weekend', 'something comforting', 'adventurous' |
| time_of_day | string | – | When the coffee will be drunk — shifts the pick toward lighter or lower-caffeine options later in the day |
No output schema declared.
No examples provided.
How do I install the Percolate MCP server?
Percolate is a hosted endpoint at https://mcp.percolateapp.com/?src=registry, 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 · mcp.percolateapp.com
claude mcp add --transport http bguillow-rgb-percolate 'https://mcp.percolateapp.com/?src=registry'
What is the Percolate MCP server?
Percolate is an MCP server listed in the public MCP registry as io.github.bguillow-rgb/percolate. Search the Percolate specialty coffee database: 1,100+ coffees with brew recipes and pairings. This page covers its hosted endpoint (https://mcp.percolateapp.com/?src=registry).
Is the Percolate MCP server safe to use?
Percolate scores 86 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 Percolate MCP server expose?
Percolate exposes 8 tools: search_coffees, get_coffee, find_similar, get_recommendations, compare_coffees, and 3 more. Their descriptions and schemas cost roughly 822 tokens of context every time the server is loaded.
Does the Percolate MCP server require authentication?
No. We connected to Percolate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Percolate MCP server still maintained?
Percolate is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.