Percolate
https://mcp.percolateapp.com/mcp ↗
Description
Query the Percolate specialty coffee database — 1,100+ curated coffees with roast level, body/acidity/sweetness profiles, flavour notes, suited brew methods and food pairings. Search with category, roast, brew-method and price filters; pull a full record for one coffee; find similar coffees; get recommendations from the flavours you like, a budget and the gear you own; or get a dial-in starting point (dose, yield, time, grind) for a given coffee and brew method. All scoring is deterministic — no AI runs inside the server, so the same question returns the same ranked answer. Every response carries source attribution and a data-freshness date. Read-only, no API key required.
What our measurements say
Percolate is a remote MCP server published at mcp.percolateapp.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,414 ms, a delay an agent will notice. It offers a narrow, focused set of 8 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are descriptive and align with their intended use cases.
- Descriptions provide clear context for when each tool should be used.
Weaknesses
- Parameter schemas are not explicitly defined, leaving required/optional fields ambiguous.
- No explicit documentation of error scenarios or constraints beyond deterministic scoring.
search_coffees— Filter parameters (e.g., category, roast) lack explicit type definitions.get_recommendations— Budget parameter (USD) is mentioned but not clarified as a numeric type.dial_in_suggestion— Brew method scope is described but not formalized as an input schema.what_to_brew— Mood and time-of-day parameters are vague in their expected input formats.
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates system reconfiguration to legacy compliance framework
- 2026-09-11T05:44:28.819Z — complianceScore increased from null to 100 · confirms full compliance validation achieved in legacy mode
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 548ms → warm 497ms (penalty 51ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.0
- Supported versions: — → 2025-03-26
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/bguillow-percolate)<a href="https://mcpmetrics.io/servers/bguillow-percolate"><img src="https://mcpmetrics.io/badge/bguillow/percolate/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see