Dusty's Pizza
REMOTE · MCP.DUSTYSPIZZA.CO.UK
Dusty's Pizza, Cardiff: menu, opening times, table requests and orders for collection.
Available components
Last scanned (9 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_table_booking). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 1366 tokens (~227/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (11)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 21 Nov 26 59
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 21 Nov 2026 · Probed https://mcp.dustyspizza.co.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dustyspizza.co.uk | CN=WE1,O=Google Trust Services,C=US | 21 Nov 2026 | 19 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | ca7e780129c5d23b131ba8bf9fbab5ac |
| SANs: dustyspizza.co.uk, mcp.dustyspizza.co.uk, *.mcp.dustyspizza.co.uk | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.dustyspizza.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| co.uk. | DS published | 11810 | 8 | Verified |
| dustyspizza.co.uk. | 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=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.dustyspizza.co.uk/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.dustyspizza.co.uk/mcp | Inconclusive | 405 |
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_menu Dusty's menu ~62
Returns Dusty's menu as it is right now: pizzas, sides, dips and desserts with prices in pounds, what is in each, vegan, vegetarian and spicy marks, the pizza of the day and of the week, and anything sold out. Availability changes during service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_opening_info Opening times and how to eat ~79
Returns where Dusty's is, how to reach it, whether it is open for collection at this moment, how long an order takes right now and the earliest collection time, the collection times on offer, the days and times for tables, the ways to eat (collect an order, walk in, or book a table) and the booking rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_table_availability Free table times ~112
Returns the table times on one day and whether a party of this size can be seated at each. Tables can be requested up to two weeks ahead. An empty list means the restaurant is closed that day or the day is out of range.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The day, as YYYY-MM-DD, on the restaurant clock (Europe/London). |
| party_size | integer | yes | How many people, from 1 to 12. For more than 12, the person should call the restaurant. |
No output schema declared.
No examples provided.
request_table_booking Ask for a table ~231
Sends Dusty's a request for a table on a given day and time, with the person's name, phone number and email address. The restaurant answers the person by email; the table is not confirmed until it does. The time must be one of the restaurant's table times for that day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The day, as YYYY-MM-DD, on the restaurant clock (Europe/London). |
| string | yes | The person's email address: the confirmation is sent there. | |
| name | string | yes | The person's name, for the booking. |
| notes | string | – | Anything the restaurant should know, e.g. a special request. Optional. |
| party_size | integer | yes | How many people, from 1 to 12. For more than 12, the person should call the restaurant. |
| phone | string | yes | The person's phone number, so the restaurant can reach them. |
| time | string | yes | The time, as HH:MM on the 24-hour restaurant clock, e.g. 18:30. One of the restaurant's table times for that day. |
No output schema declared.
No examples provided.
send_message Send Dusty's a message ~135
Sends Dusty's a message from a person, with their name, phone number and email address: a question, a special request, or something about a booking or an order. It goes to the restaurant's inbox and the restaurant replies to the person by email. It is not answered at once, and it does not book a table.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The person's email address: the restaurant replies there. | |
| message | string | yes | The message, in plain words. |
| name | string | yes | The person's name. |
| phone | string | yes | The person's phone number, so the restaurant can ring if that is quicker. |
No output schema declared.
No examples provided.
start_order Start an order for collection ~189
Checks a list of menu items, and a collection time if one is given, against the menu and the kitchen as they are right now, and returns a link to a ready-filled basket on Dusty's website with the total. Nothing is ordered or charged by this tool: the person opens the link, checks it and pays on the website. Pizzas come as 'Classic' or with a 'Hot honey' crust. Changes to a pizza (for example no basil) are made by the person on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_time | string | – | When the person wants to collect, as HH:MM on the 24-hour restaurant clock (18:30 for half past six in the evening). Left out, the order is for as soon as possible. Orders are taken for the next open… |
| items | array | yes | What the person wants. |
No output schema declared.
No examples provided.
How do I install the Dusty's Pizza MCP server?
Dusty's Pizza is a hosted endpoint at https://mcp.dustyspizza.co.uk/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 · mcp.dustyspizza.co.uk
claude mcp add --transport http uk-co-dustyspizza-mcp-dustys-pizza 'https://mcp.dustyspizza.co.uk/mcp'
What is the Dusty's Pizza MCP server?
Dusty's Pizza is an MCP server listed in the public MCP registry as uk.co.dustyspizza.mcp/dustys-pizza. Dusty's Pizza, Cardiff: menu, opening times, table requests and orders for collection. This page covers its hosted endpoint (https://mcp.dustyspizza.co.uk/mcp).
Is the Dusty's Pizza MCP server safe to use?
Dusty's Pizza scores 59 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 Dusty's Pizza MCP server expose?
Dusty's Pizza exposes 6 tools: get_menu, get_opening_info, get_table_availability, request_table_booking, start_order, send_message. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
Does the Dusty's Pizza MCP server require authentication?
No. We connected to Dusty's Pizza without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dusty's Pizza MCP server still maintained?
Dusty's Pizza is still listed as active in the MCP registry. We last reached this channel on 21 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 Dusty's Pizza MCP server?
VerifyMCP ran 11 checks on Dusty's Pizza, covering TLS certificate, Authorization, HSTS header, DNSSEC and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Dusty's Pizza: HTTPS and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.