Stovefront
REMOTE · APP.STOVEFRONT.COM
Find US home kitchens on Stovefront, read their menus and pickup times, and build order links.
Available components
Last scanned (6 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 701 tokens (~175/item across 4 items; 4 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 72
First indexed and scored.
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://app.stovefront.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.stovefront.com | CN=YR1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | 62519932b6cba3ef55b753fdec4888128b0 |
| SANs: app.stovefront.com | ||||||
| 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 app.stovefront.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| stovefront.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.stovefront.com/mcp | Verified | 200 | |
| http (plaintext) | http://app.stovefront.com/mcp | HTTPS enforced | 308 | https://app.stovefront.com/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 →
build_order_link Build an order link ~124
Checks that the given dishes can be ordered now in those quantities (stock, cutoff, quantity rules, one shared pickup time) and returns a link to the kitchen's own storefront with them already in the cart. It does not place an order or take payment: the customer reviews and submits the order request on the storefront, and the cook confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| kitchen | string | yes | Kitchen slug or storefront link, e.g. "stephanie-s-bite-of-heaven" or "https://app.stovefront.com/<slug>" |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| estimatedSubtotalCents | – | yes | Before any delivery fee |
| instruction | string | yes | – |
| items | array | yes | – |
| kitchen | object | yes | – |
| notes | array | yes | – |
| orderModel | string | yes | – |
| pickup | – | yes | – |
| url | string | yes | The kitchen's storefront with these items in the cart |
No examples provided.
get_menu Get a kitchen's menu ~157
Returns one kitchen's menu: the dishes and meal packages that can be ordered now, with price, dietary tags, allergen notes, stock, order cutoff, next pickup or delivery time, quantity rules and any required options. Also returns the payment methods the kitchen accepts and its order model (orders are requests the cook confirms).
| Name | Type | Req | Description |
|---|---|---|---|
| include_unavailable | boolean | – | Also list sold-out and closed offers, with the reason. Default false |
| kitchen | string | yes | Kitchen slug or storefront link, e.g. "stephanie-s-bite-of-heaven" or "https://app.stovefront.com/<slug>" |
| week | string | – | Only this menu week (its Monday, YYYY-MM-DD, as listed in weeks) |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| fulfillmentModel | string | yes | – |
| kitchen | object | yes | – |
| notes | array | yes | – |
| offerCount | integer | yes | Offers matching the request; offers may list fewer |
| offers | array | yes | – |
| orderModel | string | yes | – |
| orderModelNote | string | yes | – |
| paymentMethods | array | yes | – |
| weeks | array | yes | Menu weeks with something open for ordering; pass one as week to narrow the list |
No examples provided.
get_pickup_windows Get pickup and delivery times ~102
Returns a kitchen's upcoming pickup and delivery times that are open for ordering, each with its order cutoff and the pickup place name. Kitchens with scheduled times list each slot; kitchens with weekly pickup list each pickup time and the dishes it serves. Street addresses are never included.
| Name | Type | Req | Description |
|---|---|---|---|
| kitchen | string | yes | Kitchen slug or storefront link, e.g. "stephanie-s-bite-of-heaven" or "https://app.stovefront.com/<slug>" |
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | – | yes | Weekly-pickup kitchens: whether the cook delivers. Scheduled-slot kitchens list delivery times in windows. |
| kitchen | object | yes | – |
| model | string | yes | – |
| notes | array | yes | – |
| windows | array | yes | – |
No examples provided.
search_kitchens Search kitchens ~242
Finds published Stovefront kitchens and the dishes they have open for ordering. Matches words against kitchen names, dish names and categories, and can filter by dietary tags, pickup date and the area a kitchen serves. Returns each kitchen's name, storefront link, short description, service area and up to 8 matching dishes with price, dietary tags, stock and next pickup. Sample storefronts and kitchens hidden from search are not included.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | City or neighborhood, matched against the area each kitchen says it serves |
| cursor | string | – | nextCursor from the previous page |
| dietary | array | – | Every dish returned has all of these tags |
| limit | integer | – | Kitchens per page, default 10 |
| pickup_date | string | – | Only dishes that can be picked up or delivered on this kitchen-local date |
| pickup_from | string | – | Start of a date range (use with pickup_to, at most 31 days) |
| pickup_to | string | – | End of a date range, inclusive |
| query | string | – | Words to match in kitchen names, dish names and categories, e.g. "tamales" |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| nextCursor | string|null | yes | Pass as cursor for the next page; null when there are no more |
| orderModel | string | yes | – |
| orderModelNote | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the Stovefront MCP server?
Stovefront is a hosted endpoint at https://app.stovefront.com/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 · app.stovefront.com
claude mcp add --transport http com-stovefront-stovefront 'https://app.stovefront.com/mcp'
What is the Stovefront MCP server?
Stovefront is an MCP server listed in the public MCP registry as com.stovefront/stovefront. Find US home kitchens on Stovefront, read their menus and pickup times, and build order links. This page covers its hosted endpoint (https://app.stovefront.com/mcp).
Is the Stovefront MCP server safe to use?
Stovefront scores 74 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 Stovefront MCP server expose?
Stovefront exposes 4 tools: search_kitchens, get_menu, get_pickup_windows, build_order_link. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Does the Stovefront MCP server require authentication?
No. We connected to Stovefront without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stovefront MCP server still maintained?
Stovefront 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.
What did VerifyMCP test on the Stovefront MCP server?
VerifyMCP ran 13 checks on Stovefront, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.