Pandough
REMOTE · PANDOUGH.APP · SCANNED SEP 25
Flour-first dough plans: yeast, hydration, schedule from flour you own. No API key for plan tools.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1464 tokens (~209/item across 7 items; 7 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 Management73
- Stability observed for 22 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the Pandough MCP server?
Pandough is a hosted endpoint at https://pandough.app/api/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 · pandough.app
claude mcp add --transport http app-pandough-mcp 'https://pandough.app/api/mcp'
{
"mcpServers": {
"app-pandough-mcp": {
"url": "https://pandough.app/api/mcp"
}
}
} {
"servers": {
"app-pandough-mcp": {
"type": "http",
"url": "https://pandough.app/api/mcp"
}
}
} [mcp_servers.app-pandough-mcp] url = "https://pandough.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-pandough-mcp": {
"type": "remote",
"url": "https://pandough.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-pandough-mcp --url 'https://pandough.app/api/mcp' --transport streamable-http
mcp_servers:
app-pandough-mcp:
url: "https://pandough.app/api/mcp" {
"McpServers": {
"app-pandough-mcp": {
"Transport": "http",
"Url": "https://pandough.app/api/mcp"
}
}
} assistant mcp add app-pandough-mcp -t streamable-http -u 'https://pandough.app/api/mcp'
{
"mcpServers": {
"app-pandough-mcp": {
"type": "http",
"url": "https://pandough.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 25 Sept 2026 · Probed https://pandough.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pandough.app | CN=YR1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | RSA 2048 | SHA256-RSA | 690cc5ee7e7b6b63d15fea84d2ee02e15ab |
| SANs: pandough.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pandough.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| pandough.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 |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.clerk.dev https://*.clerk.accounts.dev https://clerk.pandough.app https://*.clerk.com https://challenges.cloudflare.com https://*.posthog.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob:; media-src 'self' blob: https:; font-src 'self' data:; connect-src 'self' https://*.convex.cloud https://*.clerk.dev https://*.clerk.accounts.dev https://clerk.pandough.app https://*.clerk.com https://challenges.cloudflare.com https://*.posthog.com wss://*.convex.cloud https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; frame-src 'self' https://js.clerk.dev https://*.clerk.accounts.dev https://clerk.pandough.app https://*.clerk.com https://challenges.cloudflare.com; worker-src 'self' blob: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| 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://pandough.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://pandough.app/api/mcp | HTTPS enforced | 308 | https://pandough.app/api/mcp |
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 →
get_flour_details ~64
Get detailed information about a specific flour by its slug. Returns full profile including protein, W strength, hydration curve, maturation profiles, and description.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Flour slug (e.g. 'caputo-pizzeria', 'manitoba-oro') |
No output schema declared.
No examples provided.
list_active_bakes ~88
List the signed-in baker's scheduled and active bakes plus live temperature-sensor readings when a device is reporting. The first call prompts the chat app to authorize a Pandough account (OAuth scope bakes:read). Needs Pro (or cancelled-Pro). Returns ids, flour, hydration, schedule, a calculator session link, and probe temps (air around the dough, not dough core).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recipes ~75
List the dough recipe styles plan_bake supports. Call this when a user names a style (Neapolitan, classica, focaccia, bread, baguette) so you pass the correct recipeSlug instead of guessing — and so you never confuse a style word like 'classica' with a flour whose name contains it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_bake ~989
Create a bake plan with ingredient calculations. Returns exact ingredient amounts in grams, an auto-sized yeast amount, a fermentation schedule, dough warnings, and a calculator URL the user can open in Pandough with all parameters prefilled. Before calling this, gather the inputs that actually determine a good plan (skip any the user already volunteered): (1) Strongly ask which oven model they use — call search_ovens and pass ovenSlug. If it is unlisted, ask for ovenType plus ovenMaxCelsius. Oven capability materially changes the hydration band and bake feasibility; if the user declines, proceed but say the result is not oven-adapted. (2) Which flour(s) do they have? — call search_flours to resolve a flourSlug (or pass flourBlend for a 2–5 flour cut, e.g. a Pulcinella base with 30% Manitoba); this is what makes hydration and warnings flour-aware. (3) Their room temperature and fridge temperature — pass roomTempCelsius/fridgeTempCelsius; temperature is the dominant driver of yeast amount and timing. (4) How they mix/knead (by hand, stand mixer, no-knead) — plan_bake does not return technique guidance, so pair it with a troubleshoot call for method advice. (5) Do they want a preferment? — pass `preferment` for a biga, poolish, tiga, cold/long biga, or a natural sourdough starter. The yeast figure accounts for the preferment, and the calculator link opens with the build already set up, so recommending a biga in prose without passing this param hands the user a direct dough. Don't interrogate a user who already gave a full brief.
| Name | Type | Req | Description |
|---|---|---|---|
| bakeTime | string | – | Target bake time as an ISO 8601 datetime (e.g. '2026-06-10T18:00:00Z'). Must be in the future. |
| flourBlend | array | – | A weighted flour blend (2–5 flours summing to 100%), e.g. [{flourSlug:'caputo-pizzeria',percent:70},{flourSlug:'manitoba-oro',percent:30}]. Mutually exclusive with flourSlug. |
| flourSlug | string | – | Flour slug from search_flours (e.g. 'caputo-pizzeria'). For a single flour. Mutually exclusive with flourBlend. |
| fridgeTempCelsius | number | – | The user's real fridge temperature in °C (0–12). Ask the user for it when a cold ferment is involved. |
| fridgeTempHours | number | – | Cold fermentation hours (0–168). Pass BOTH this and roomTempHours to lock the split. |
| hydrationPercent | number | – | Target hydration percentage (40–110) |
| locale | string | – | UI locale for the returned calculator link (e.g. 'en', 'pl', 'it'). Defaults to 'en'. |
| ovenMaxCelsius | number | – | The real maximum temperature in °C for an unlisted oven (100–600). This is what constrains hydration and bake time. |
| ovenMinCelsius | number | – | Optional minimum set temperature in °C for an unlisted oven. |
| ovenSlug | string | – | Exact oven model slug from search_ovens. Strongly preferred: the engine uses the model's real ceiling and oven class to adapt hydration and bake feasibility. Mutually exclusive with manual ovenType/o… |
| ovenType | string | – | Oven class for an unlisted model. Pass together with ovenMaxCelsius; prefer ovenSlug when search_ovens finds the model. |
| preferment | object | – | Plan the bake around a preferment (biga, poolish, tiga, sourdough…). The yeast figure returned accounts for it, and the calculator link opens with the build already set up. |
| recipeSlug | string | yes | Recipe type slug. Supported: neapolitan-pizza, classica-pizza, focaccia, artisan-bread, baguette (call list_recipes for the full list). When the user names a style like 'classica', pass that style he… |
| roomTempCelsius | number | – | The user's real kitchen temperature in °C (2–40). The single biggest driver of yeast amount and timing — ask the user for it. |
| roomTempHours | number | – | Room-temperature fermentation hours (0–168). Pass BOTH this and fridgeTempHours to lock the split; naming only a total lets the engine choose. Room legs above 14h are clamped with a warning. |
| servings | integer | – | Number of portions/pizzas (1–50, default: 4) |
No output schema declared.
No examples provided.
search_flours ~83
Search the Pandough flour database. Returns flour names, protein %, W strength, hydration ranges, and types. Use this to help users find the right flour for their bake.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Search term (name, brand, or type) |
| tag | string | – | Filter by tag (e.g. 'pizza', 'bread', 'pastry') |
No output schema declared.
No examples provided.
search_ovens ~102
Search the Pandough oven database. Returns oven specs (max temperature, type, fuel) plus recommended bake settings — top/deck heat, bake time, and deck material — computed for a Neapolitan pizza by the same heat engine the site uses.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Search term (oven name, brand) |
| type | string | – | Oven type filter (e.g. 'pizza-oven', 'home-oven', 'outdoor') |
No output schema declared.
No examples provided.
troubleshoot ~63
Search the Pandough baking knowledge base for troubleshooting advice, technique guides, and flour science. Returns curated expert content about common baking issues.
| Name | Type | Req | Description |
|---|---|---|---|
| issue | string | yes | The baking issue or question (e.g. 'sticky dough', 'no oven spring', 'cold proof technique') |
No output schema declared.
No examples provided.
What is the Pandough MCP server?
Pandough is an MCP server listed in the public MCP registry as app.pandough/mcp. Flour-first dough plans: yeast, hydration, schedule from flour you own. No API key for plan tools. This page covers its hosted endpoint (https://pandough.app/api/mcp).
Is the Pandough MCP server safe to use?
Pandough scores 75 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 Pandough MCP server expose?
Pandough exposes 7 tools: search_flours, get_flour_details, list_recipes, plan_bake, troubleshoot, and 2 more. Their descriptions and schemas cost roughly 1,464 tokens of context every time the server is loaded.
Does the Pandough MCP server require authentication?
No. We connected to Pandough without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pandough MCP server still maintained?
Pandough is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.