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.

BondSeat

NPM · @BONDSEAT/MCP · SCANNED SEP 26

Snag hard-to-get Resy tables with automatic cancellation monitoring and scheduled release attempts.

Available components

66 Trust /100
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
  • 35 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 576 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.Pass
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the BondSeat MCP server?

BondSeat runs locally as an npm package, launched with npx -y @bondseat/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 · @bondseat/mcp

# add to Claude Code
claude mcp add saintmarksventures-bondseat -- npx -y @bondseat/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "saintmarksventures-bondseat": {
      "command": "npx",
      "args": [
        "-y",
        "@bondseat/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "saintmarksventures-bondseat": {
      "command": "npx",
      "args": [
        "-y",
        "@bondseat/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add saintmarksventures-bondseat -- npx -y @bondseat/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "saintmarksventures-bondseat": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@bondseat/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add saintmarksventures-bondseat --command npx --arg -y --arg @bondseat/mcp
# ~/.hermes/config.yaml
mcp_servers:
  saintmarksventures-bondseat:
    command: "npx"
    args: ["-y", "@bondseat/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "saintmarksventures-bondseat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@bondseat/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add saintmarksventures-bondseat -t stdio -c npx -a -y @bondseat/mcp
// mcp.json
{
  "mcpServers": {
    "saintmarksventures-bondseat": {
      "command": "npx",
      "args": [
        "-y",
        "@bondseat/mcp"
      ]
    }
  }
}
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.

  • 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
  • 20 Sept 26 66

    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 26 Sept 2026 · Analysed npm/@bondseat/mcp@0.1.2

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 100 packages
Packages resolved 100
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~576 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
bondseat_connect ~33

Restore access to existing bookings without starting or resuming a request. Show setupUrl to the diner, then use status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bondseat_request ~207

Start one persistent booking request using a restaurant name plus city/neighborhood, a Resy URL, or a returned restaurantId. BondSeat resolves missing venues automatically; ambiguous matches return choices without starting work. Existing user instructions can authorize it; do not ask again when a table appears. Show any setupUrl to the diner, then schedule status checks to finish setup and report the booking outcome; this connector does not push updates. Identical dining details reuse the original request. Never use this tool to repair a payment or credential problem.

NameTypeReqDescription
cancelFeeProtectionHoursinteger––
citystring––
confirmedbooleanyes–
datestringyes–
endTimestringyes–
executeAtstring––
modestring––
partySizeintegeryes–
restaurantstring––
restaurantIdstring––
restaurantUrlstring––
startTimestringyes–

No output schema declared.

No examples provided.

bondseat_requests ~34

List existing booking requests. Follow nextCursor with cursor.

NameTypeReqDescription
cursorstring––
kindstring––

No output schema declared.

No examples provided.

bondseat_restaurants ~87

Find restaurants by name and city/neighborhood, or a Resy URL. BondSeat uses its venue lookup and adds missing verified venues automatically. Check name and location; clarify ambiguous matches. Empty input lists the directory; follow nextCursor with cursor.

NameTypeReqDescription
citystring––
cursorstring––
qstring––
urlstring––

No output schema declared.

No examples provided.

bondseat_resume ~49

Resume the same unfinished monitor after user authorization. If credentials are required, show nextAction to reconnect first. Never resumes successful bookings.

NameTypeReqDescription
idstringyes–
kindstringyes–

No output schema declared.

No examples provided.

bondseat_status ~96

Read booking status. Without an ID, finish pending setup. Schedule follow-up calls after pollAfterSeconds until terminal or user action is needed, then notify the diner. Follow agentInstruction. This tool does not run background checks. If the runtime cannot schedule follow-ups, say so. Credentials are managed automatically. FIRED monitor outcome or SUCCEEDED scheduled status means booked.

NameTypeReqDescription
idstring––
kindstring––

No output schema declared.

No examples provided.

bondseat_stop ~70

Stop future attempts when requested. This cannot cancel a restaurant reservation; an in-flight booking may finish. Follow agentInstruction and nextAction: verify_provider means ask the diner to check their reservations with the provider, without claiming no booking exists.

NameTypeReqDescription
idstringyes–
kindstringyes–

No output schema declared.

No examples provided.

Common questions

What is the BondSeat MCP server?

BondSeat is an MCP server listed in the public MCP registry as io.github.saintmarksventures/bondseat. Snag hard-to-get Resy tables with automatic cancellation monitoring and scheduled release attempts. This page covers its npm package (@bondseat/mcp).

Is the BondSeat MCP server safe to use?

BondSeat scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 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 BondSeat MCP server expose?

BondSeat exposes 7 tools: bondseat_restaurants, bondseat_request, bondseat_status, bondseat_requests, bondseat_stop, and 2 more. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.

Is the BondSeat MCP server still maintained?

BondSeat is still listed as active in the MCP registry. We last reached this channel on 26 September 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 BondSeat MCP server under?

BondSeat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.