Ext Ops Panel
Open dashboard
Comparison

striderlabs-opentable vs io.github.chrischall/resy-mcp

striderlabs-opentable is a plugin bundle for AI coding tools published by markswendsen-code. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.chrischall/resy-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacestriderlabs-opentableio.github.chrischall/resy-mcp
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.3
Downloads/month (npm): 3 429
Downloads/week (npm): 790
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

striderlabs-opentable vs io.github.chrischall/resy-mcp
Factstriderlabs-opentableio.github.chrischall/resy-mcp
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (resy-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 2
LicenceMITMIT
Repository (differs)github.com/markswendsen-code/mcp-opentablegithub.com/chrischall/resy-mcp
Changes in the last 7 days (differs)04
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

striderlabs-opentable

In its own words, on Claude Code: claude-plugins-community:

Make restaurant reservations on OpenTable. Let AI agents search restaurants, check availability, and book tables.

io.github.chrischall/resy-mcp

In its own words, on Official MCP Registry:

Resy reservation management — search, book, cancel, favorites, and Priority Notify for Claude

How to run each

striderlabs-opentable As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install striderlabs-opentable@claude-community

io.github.chrischall/resy-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "RESY_AUTH_TOKEN=<YOUR_RESY_AUTH_TOKEN>" --env "RESY_PASSWORD=<YOUR_RESY_PASSWORD>" --transport stdio resy-mcp -- npx -y resy-mcp

Requires: RESY_AUTH_TOKEN (secret), RESY_PASSWORD (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of striderlabs-opentable publish no settings it asks for, so we do not compare settings.

What it can do: striderlabs-opentable · What it can do: io.github.chrischall/resy-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built