Dine MCP
PYPI · DINE-MCP
Restaurant table availability across SevenRooms, TableCheck and ResDiary. Read-only; never books.
Available components
Last scanned (8 hours ago)
Scores higher than 57% of PyPI servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1071 tokens (~267/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 Management20
- Stability observed for 6 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
- 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 (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- GHSA-7xgj-8392-5q4r no longer affects this package ▲ security
- GHSA-vqqp-x5qm-5qp4 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Package version: 0.2.6 → 0.2.10 functional
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 0
- Provenance: fail → unverified ▼ security
- Schema quality: 242 → 267 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Package version: 0.2.3 → 0.2.6 functional
- Package version: 0.2.3 → 0.2.4 functional
- 30 Oct 26 51
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 · Analysed pypi/dine-mcp@0.2.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
dine_check_availability Check availability ~316
Table availability for venues over dates, a time window and a party size. Ask for missing dates and diner count before calling; state the time window used. One result per venue and channel: {venue_id, venue_name, channel, status, time_zone, slots [{start, kind, area, experience, price, requires_card, booking_link}], coverage {dates_checked, dates_not_checked}, observed_at, served_from, booking_link, opens_at, min_party, max_party, contact, note}. status: ok, none_available, not_yet_open (see opens_at), party_too_small, party_too_large, closed, contact_only, not_connected, blocked, rate_limited, unavailable, unsupported, unknown_venue, skipped_deadline. Large requests are refused with too_broad: narrow them.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | yes | First date, YYYY-MM-DD, venue local |
| date_to | – | – | Last date inclusive (default date_from); at most 7 days |
| kinds | – | – | Slot kinds to include (default bookable and request) |
| party_size | integer | – | Number of diners |
| response_format | string | – | concise: up to 6 slots per venue and day |
| time_from | string | – | Earliest time, HH:MM venue local |
| time_to | string | – | Latest time, HH:MM; earlier than time_from crosses midnight |
| venue_ids | array | yes | 1-5 venue_ids from dine_find_venue |
| Name | Type | Req | Description |
|---|---|---|---|
| query | object | yes | – |
| results | array | yes | – |
| summary | object | yes | – |
No examples provided.
dine_find_venue Find venue ~261
Identify one named restaurant and its booking channels (provider and venue on it, phone, website). Give exactly one of name (with area and country when known), url or google_place_id. Returns {venues: [{venue_id, name, address, time_zone, channels [{kind, access_mode, url, text, verified}], match {confidence, evidence}}], candidates [{name, address, google_place_id, confidence}], note}. Candidates mean "not sure which": ask which one unless the request uniquely identifies it, then call again with its google_place_id. Do not infer the venue country from the person's location. Not a cuisine or area search.
| Name | Type | Req | Description |
|---|---|---|---|
| area | – | – | Where it is: district or city ('Central', 'Shibuya') |
| country | – | – | ISO 3166-1 alpha-2 country code ('HK', 'JP') |
| google_place_id | – | – | A Google place id (ChIJ…) from a maps tool |
| limit | integer | – | Candidates to return (1-10) |
| name | – | – | The restaurant's name, any script ('Amber', '鮨 しこう') |
| url | – | – | A booking page link (SevenRooms, TableCheck, ResDiary); never fetched |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| note | – | – | – |
| venues | array | yes | – |
No examples provided.
dine_get_venue Get venue ~75
One venue in full: channels, each provider's booking rules (how many days ahead, party size limits, card or deposit), experiences or courses, booking links, opening hours and sources. Costs one provider request per channel when not cached.
| Name | Type | Req | Description |
|---|---|---|---|
| venue_id | string | yes | A venue_id from dine_find_venue |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | yes | – |
| name | string | yes | – |
| venue_id | string | yes | – |
No examples provided.
dine_status Status ~99
Version, each provider's mode, maturity, whether it is on, today's request budget and any pause after provider pushback. Default is offline; check=true runs paced, budgeted public-widget canaries with a 15-minute cooldown. For a restaurant's availability, use dine_find_venue then dine_check_availability. Health never contacts a provider.
| Name | Type | Req | Description |
|---|---|---|---|
| check | boolean | – | Run budgeted provider canaries (15-minute cooldown) |
| Name | Type | Req | Description |
|---|---|---|---|
| providers | array | yes | – |
| version | string | yes | – |
No examples provided.
How do I install the Dine MCP server?
Dine MCP runs locally as a PyPI package, launched with uvx dine-mcp --transport stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · dine-mcp
claude mcp add benjamin-di-dine-mcp -- uvx dine-mcp --transport stdio
What is the Dine MCP server?
Dine MCP is listed in the public MCP registry as io.github.benjamin-di/dine-mcp. Restaurant table availability across SevenRooms, TableCheck and ResDiary. Read-only; never books. This page covers its PyPI package (dine-mcp).
Is the Dine MCP server safe to use?
Dine MCP scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Dine MCP server expose?
Dine MCP exposes 4 tools: dine_find_venue, dine_get_venue, dine_check_availability, dine_status. Their descriptions and schemas cost roughly 751 tokens of context every time the server is loaded.
Is the Dine MCP server still maintained?
Dine MCP 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 licence is the Dine MCP server under?
Dine MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Dine MCP server?
VerifyMCP ran 15 checks on Dine MCP, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Dine MCP: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.