Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.David-Cabeza/opencovers

NPM · @OPENCOVERS/MCP

Restaurant reservations over MCP: availability, bookings, tables and waitlist. Open source.

Available components

68 Trust /100

Last scanned (13 hours ago)

Scores higher than 39% of npm servers

Category E-commerce

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 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 Usability54
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 2450 tokens (~136/item across 18 items; 18 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 47% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 18 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
What we tested

Checks we ran (16)

  • Malware scan
  • 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

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 →

Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 34% → 47% ▲ functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 16 Nov 26 65

    First indexed and scored.

Diagnostics

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 · Analysed npm/@opencovers/mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~2,450 tokens

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 →

Tool Tokens
reservation.agenda ~39

List reservations for a venue on a specific date.

NameTypeReqDescription
datestringyesDate as YYYY-MM-DD.
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.availability ~65

List available time slots for a venue on a date for a party size, grouped by service (meal period).

NameTypeReqDescription
datestringyesDate as YYYY-MM-DD.
partySizeintegeryesNumber of guests.
venueIdstringyesThe venue id.

No output schema declared.

No examples provided.

reservation.cancel ~94

Cancel a reservation. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
idstringyes–
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.create ~401

Create a reservation and return it. Pass table ids to assign them explicitly, or omit tables to let the engine assign tables automatically for the party size. Guest fields are guestName, guestContact and consent, or the same as a guest object with name, contact and consent. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
commentarystring–A short note for staff about this booking, up to 500 characters, such as an occasion. Never put allergies, medical conditions, or diet needs here. Empty string clears it.
consentstring–Whether the guest allows being contacted after the visit. Omit if never asked.
datestringyesDate as YYYY-MM-DD.
guestobject–Same as the flat guestName, guestContact and consent fields, in the shape the HTTP API uses. Pass one or the other.
guestContactstring––
guestNamestring––
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
partySizeintegeryes–
rating––The guest's rating of the visit, 1 to 5. Omit if not given. Null clears it.
reconfirmationstring–Whether the guest reconfirmed the booking. none means not asked, requested means asked and waiting. Omit to leave it unchanged. A booking is never cancelled by it.
tablesarray–Table ids to assign. Omit to auto-assign.
timestringyesTime as HH:MM in the venue timezone.
venueIdstringyes–
zonestring–Zone to prefer (e.g. Terrace). When set, tables come from this zone.

No output schema declared.

No examples provided.

reservation.erasure ~186

Needs an admin key, a write key gets forbidden. Erase guest data for a venue, by guest id or owner principal. A guest id erases the guest record, every reservation linked to it, and the venue's waitlist entries with the same contact. An owner principal erases the reservations it owns and the guest records left with no other visit. A guest id that is not a record is read as a contact, which is deprecated. Returns counts of erased reservations, guest records, and waitlist entries. Takes no idempotency key. A retry erases nothing more and reports 0 for what the first call erased.

NameTypeReqDescription
guestIdstring–Guest record id from a reservation's guest.guestId. A contact still works for one version and is deprecated.
principalstring–Owner principal to erase.
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.events ~43

Read the reservation event feed for a venue, from a cursor.

NameTypeReqDescription
cursorstring––
limitinteger––
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.get ~30

Get a single reservation by id.

NameTypeReqDescription
idstringyes–
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.list ~23

List all reservations for a venue.

NameTypeReqDescription
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.modify ~306

Modify a reservation's party size, tables, contact consent, rating, booking note, and/or reconfirmation. Consent is consent, or guest.consent. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
commentarystring–A short note for staff about this booking, up to 500 characters, such as an occasion. Never put allergies, medical conditions, or diet needs here. Empty string clears it.
consentstring–Whether the guest allows being contacted after the visit. Omit if never asked.
guestobject–Same as the flat guestName, guestContact and consent fields, in the shape the HTTP API uses. Pass one or the other.
idstringyes–
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
partySizeinteger––
rating––The guest's rating of the visit, 1 to 5. Omit if not given. Null clears it.
reconfirmationstring–Whether the guest reconfirmed the booking. none means not asked, requested means asked and waiting. Omit to leave it unchanged. A booking is never cancelled by it.
tablesarray––
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.search ~68

Search reservations for a venue within a date range, optionally filtered by status.

NameTypeReqDescription
dateEndstringyesExclusive end date as YYYY-MM-DD.
dateStartstringyesInclusive start date as YYYY-MM-DD.
statusarray––
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.status ~134

Advance a reservation status: seat, mark attended, or mark no-show. Seating needs a table: a booking without tables fails with table_required, so assign one with reservation.modify first. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
idstringyes–
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
statusstringyes–
venueIdstringyes–

No output schema declared.

No examples provided.

reservation.walk_in ~333

Seat a guest who arrives without a reservation. Defaults the time to now in the venue timezone. Guest fields are guestName, guestContact and consent, or the same as a guest object with name, contact and consent. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
commentarystring–A short note for staff about this booking, up to 500 characters, such as an occasion. Never put allergies, medical conditions, or diet needs here. Empty string clears it.
consentstring–Whether the guest allows being contacted after the visit. Omit if never asked.
datestring–Date as YYYY-MM-DD. Defaults to today.
guestobject–Same as the flat guestName, guestContact and consent fields, in the shape the HTTP API uses. Pass one or the other.
guestContactstring––
guestNamestring––
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
partySizeintegeryes–
rating––The guest's rating of the visit, 1 to 5. Omit if not given. Null clears it.
tablesarray–Table ids. Omit to auto-assign.
timestring–Time as HH:MM. Defaults to now.
venueIdstringyes–
zonestring––

No output schema declared.

No examples provided.

venue.getConfig ~28

Read whether a venue accepts reservations and its notice address.

NameTypeReqDescription
venueIdstringyes–

No output schema declared.

No examples provided.

venue.setConfig ~289

Enable or disable reservations and set the notice address. Enabling requires a notice address. Takes no idempotency key. A retry with the same values sets the same configuration.

NameTypeReqDescription
blockedDatesarray–Dates (YYYY-MM-DD) or { from, to } ranges, inclusive, in the venue time zone, on which no bookings are taken. Replaces the list. An empty list clears it.
enabledboolean––
fromEmailstring––
lastSeatingOffsetMinutesinteger––
leadTimeMinutesinteger––
maxActivePerGuestPerDay––The most active bookings one guest, identified by contact, may hold on one date. Null turns it off.
maxAdvanceDays––Refuse bookings more than this many days ahead, counted from today in the venue time zone. Null turns it off.
noticeAddressstring––
notificationsEnabledboolean––
overbookingCeilinginteger–The most covers the venue accepts without tables at one time. 0 means every booking holds tables.
phoneCountrystring|null–ISO 3166 alpha-2 country for phone numbers without a country code. Null follows the venue time zone.
resendApiKeystring––
slotIntervalMinutesinteger––
venueIdstringyes–

No output schema declared.

No examples provided.

waitlist.add ~182

Add a guest to the waitlist when no table is available. Guest fields are guestName and guestContact, or the same as a guest object with name and contact. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
guestobject–Same as the flat guestName, guestContact and consent fields, in the shape the HTTP API uses. Pass one or the other.
guestContactstring––
guestNamestring––
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
partySizeintegeryes–
venueIdstringyes–
zonestring––

No output schema declared.

No examples provided.

waitlist.cancel ~99

Remove a guest from the waitlist. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
idstringyes–
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
venueIdstringyes–

No output schema declared.

No examples provided.

waitlist.list ~26

List the guests currently waiting for a table.

NameTypeReqDescription
venueIdstringyes–

No output schema declared.

No examples provided.

waitlist.seat ~104

Seat a waiting guest, turning the entry into a reservation. Pass the same idempotencyKey when you retry after a timeout or an error. Without it a retry is a new write and may create a duplicate.

NameTypeReqDescription
idstringyes–
idempotencyKeystring–Any unique string for this write. Send the same one again to retry it. Omit it and the server makes a new one.
venueIdstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.David-Cabeza/opencovers MCP server?

io.github.David-Cabeza/opencovers runs locally as an npm package, launched with npx -y @opencovers/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @opencovers/mcp

# add to Claude Code
claude mcp add david-cabeza-opencovers -- npx -y @opencovers/mcp
Common questions

What is the io.github.David-Cabeza/opencovers MCP server?

io.github.David-Cabeza/opencovers is an MCP server listed in the public MCP registry as io.github.David-Cabeza/opencovers. Restaurant reservations over MCP: availability, bookings, tables and waitlist. Open source. This page covers its npm package (@opencovers/mcp).

Is the io.github.David-Cabeza/opencovers MCP server safe to use?

io.github.David-Cabeza/opencovers scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.David-Cabeza/opencovers MCP server expose?

io.github.David-Cabeza/opencovers exposes 18 tools: reservation.availability, reservation.agenda, reservation.list, reservation.search, reservation.get, and 13 more. Their descriptions and schemas cost roughly 2,450 tokens of context every time the server is loaded.

Is the io.github.David-Cabeza/opencovers MCP server still maintained?

io.github.David-Cabeza/opencovers 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 licence is the io.github.David-Cabeza/opencovers MCP server under?

io.github.David-Cabeza/opencovers 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 io.github.David-Cabeza/opencovers MCP server?

VerifyMCP ran 16 checks on io.github.David-Cabeza/opencovers, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.