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.markswendsen-code/doordash

NPM · @STRIDERLABS/MCP-DOORDASH · SCANNED SEP 20

MCP server for DoorDash - let AI agents order food delivery autonomously with browser-based ordering

0 this week 84 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
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 455 tokens (~50/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Install

How do I install the io.github.markswendsen-code/doordash MCP server?

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

npm · @striderlabs/mcp-doordash

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

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

  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.77 functional
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 20 Sept 2026 · Analysed npm/@striderlabs/mcp-doordash@0.4.1

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 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~455 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
doordash_add_to_cart ~90

Add a menu item to the cart. Must be on a restaurant page first (use doordash_menu).

NameTypeReqDescription
itemNamestringyesName of the menu item to add
quantitynumberQuantity to add (default: 1)
restaurantIdstringyesThe restaurant ID
specialInstructionsstringSpecial instructions for the item (optional)

No output schema declared.

No examples provided.

doordash_auth_check ~39

Check if user is logged in to DoorDash. Returns login status and instructions if not authenticated. Call this before any other DoorDash operations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doordash_auth_clear ~28

Clear stored DoorDash session cookies. Use this to log out or reset authentication state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doordash_cart ~23

View current cart contents, including items, quantities, and totals.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doordash_checkout ~55

Proceed to checkout and optionally place the order. Set confirm=false to preview order details, confirm=true to actually place the order.

NameTypeReqDescription
confirmbooleanyesSet to true to actually place the order, false to just preview

No output schema declared.

No examples provided.

doordash_menu ~41

Get the full menu for a specific restaurant. Returns categories and items with prices.

NameTypeReqDescription
restaurantIdstringyesThe restaurant ID (from search results)

No output schema declared.

No examples provided.

doordash_search ~72

Search for restaurants on DoorDash. Can search by restaurant name, food type, or cuisine.

NameTypeReqDescription
cuisinestringFilter by cuisine type (e.g., 'pizza', 'chinese', 'mexican')
querystringyesSearch query (restaurant name, food type, or cuisine)

No output schema declared.

No examples provided.

doordash_set_address ~54

Set the delivery address for DoorDash orders. Must be set before searching for restaurants.

NameTypeReqDescription
addressstringyesFull delivery address (e.g., '123 Main St, San Francisco, CA 94102')

No output schema declared.

No examples provided.

doordash_track_order ~53

Track the status of an order. Shows delivery progress, estimated time, and dasher info if available.

NameTypeReqDescription
orderIdstringOrder ID to track (optional - defaults to most recent active order)

No output schema declared.

No examples provided.

Common questions

What is the io.github.markswendsen-code/doordash MCP server?

io.github.markswendsen-code/doordash is an MCP server listed in the public MCP registry as io.github.markswendsen-code/doordash. MCP server for DoorDash - let AI agents order food delivery autonomously with browser-based ordering. This page covers its npm package (@striderlabs/mcp-doordash).

Is the io.github.markswendsen-code/doordash MCP server safe to use?

io.github.markswendsen-code/doordash scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 io.github.markswendsen-code/doordash MCP server expose?

io.github.markswendsen-code/doordash exposes 9 tools: doordash_auth_check, doordash_auth_clear, doordash_set_address, doordash_search, doordash_menu, and 4 more. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.

Is the io.github.markswendsen-code/doordash MCP server still maintained?

io.github.markswendsen-code/doordash is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.markswendsen-code/doordash MCP server under?

io.github.markswendsen-code/doordash declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.