io.github.dashpilot-labs/dashpilot-mcp
PYPI · DOORDASH-DASHPILOT-MCP
DoorDash Drive deliveries over MCP — quote, dispatch, and track deliveries from your POS.
Available components
Last scanned (28 minutes ago)
Scores higher than 61% of PyPI servers
Category E-commerce
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 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2048 tokens (~120/item across 17 items; 17 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 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
- 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 current MCP spec version (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.
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.
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: fail functional
- 12 Oct 26 39
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 18 Oct 2026 · Analysed pypi/doordash-dashpilot-mcp@0.1.5
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 | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 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 →
accept_quote ~87
Accept a quote from get_delivery_quote — this dispatches a real Dasher, billed by DoorDash to your developer account. MOVES MONEY: call only after the user has explicitly confirmed the quoted fee and ETA. external_delivery_id: the ID you quoted with. tip: set/override the tip in cents.
| Name | Type | Req | Description |
|---|---|---|---|
| external_delivery_id | string | yes | – |
| tip | – | – | – |
No output schema declared.
No examples provided.
batch_dispatch ~128
Dispatch up to 25 deliveries at once — catering runs, multi-order drops. Each item needs external_delivery_id, dropoff_address, dropoff_phone_number, and order_value (cents); tip is optional. pickup_address applies to items that don't set their own. Returns a batch_id and one result per delivery. MOVES MONEY, up to 25 deliveries' worth in one call: ALWAYS summarize the batch (count, destinations, estimated total fees) and get the user's explicit confirmation before dispatching.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveries | array | yes | – |
| pickup_address | string | – | – |
No output schema declared.
No examples provided.
cancel_delivery ~46
Cancel a delivery. Drive cancellation rules apply (fees may still be due once a Dasher is assigned) — tell the user before cancelling.
| Name | Type | Req | Description |
|---|---|---|---|
| external_delivery_id | string | yes | – |
No output schema declared.
No examples provided.
check_drive_connection ~66
Verify your locally-held Drive access key works, without dispatching anything: signs a JWT and asks Drive about a nonexistent delivery — a 404 means authenticated, a 401 means the key is wrong. Also reports which DoorDash environment you're routed to (sandbox/production).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_install ~83
Close this DashPilot install and delete its data from DashPilot Cloud: the account, usage history, scheduled queue, and uploaded support bundles. Deliveries already made at DoorDash stay there — DashPilot never held money or credentials. IRREVERSIBLE: confirm with the user before calling. The API key stops working; reusing it later starts a fresh install.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dispatch_delivery ~201
Dispatch a delivery immediately (quote + accept in one step): a Dasher is assigned and the delivery is billed by DoorDash to your Drive account. MOVES MONEY: quote first with get_delivery_quote, show the user the fee and ETA, and dispatch only after their explicit confirmation. The request goes straight to DoorDash, signed with your local key. Parameters are identical to get_delivery_quote.
| Name | Type | Req | Description |
|---|---|---|---|
| contactless_dropoff | boolean | – | – |
| dropoff_address | string | yes | – |
| dropoff_contact_family_name | – | – | – |
| dropoff_contact_given_name | – | – | – |
| dropoff_instructions | – | – | – |
| dropoff_phone_number | string | yes | – |
| external_delivery_id | string | yes | – |
| order_value | integer | yes | – |
| pickup_address | string | yes | – |
| pickup_business_name | – | – | – |
| pickup_instructions | – | – | – |
| pickup_reference_tag | – | – | – |
| tip | integer | – | – |
No output schema declared.
No examples provided.
dispatch_due_deliveries ~95
Fire every scheduled delivery that is due right now. Asks DashPilot Cloud for the due queue (unsigned payloads only), mints a fresh short-lived JWT on this machine for each one, dispatches directly to DoorDash Drive, and reports the results back for the ops board. Run it on a cadence (or whenever you want due work flushed) — the cloud backend cannot dispatch anything itself.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
generate_support_bundle ~84
Having a dispatch problem? Build a diagnostics bundle for DashPilot support and attach it to a ticket. Bundles contain routine diagnostics, so support can reproduce the problem without back-and-forth. The upload receipt itemizes what was sent. issue: short description of the problem (e.g. "scheduled delivery never fired").
| Name | Type | Req | Description |
|---|---|---|---|
| issue | string | yes | – |
No output schema declared.
No examples provided.
get_account ~21
Your DashPilot account: business, dispatch count, member since.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_delivery_quote ~277
Quote a DoorDash Drive delivery before committing: delivery fee, tax, ETA. Nothing is dispatched and no money moves until the quote is accepted. The request goes straight to DoorDash, signed with your local key. Read-only: quote liberally, no user confirmation needed — confirmation is required only before accept_quote / dispatch_delivery. external_delivery_id: your unique ID for this delivery (e.g. a POS order number). pickup_address: your store's full address, comma-separated. dropoff_address: customer's full address, comma-separated. dropoff_phone_number: customer phone, E.164 (e.g. +12125550100). order_value: order subtotal in cents, excluding tax/tip ($19.99 = 1999). tip: Dasher tip in cents.
| Name | Type | Req | Description |
|---|---|---|---|
| contactless_dropoff | boolean | – | – |
| dropoff_address | string | yes | – |
| dropoff_contact_family_name | – | – | – |
| dropoff_contact_given_name | – | – | – |
| dropoff_instructions | – | – | – |
| dropoff_phone_number | string | yes | – |
| external_delivery_id | string | yes | – |
| order_value | integer | yes | – |
| pickup_address | string | yes | – |
| pickup_business_name | – | – | – |
| pickup_instructions | – | – | – |
| pickup_reference_tag | – | – | – |
| tip | integer | – | – |
No output schema declared.
No examples provided.
get_dispatch_settings ~29
Current dispatch settings and feature flags from DashPilot Cloud (feature flags, default tip, Drive environment).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_deliveries ~63
Your operations board on DashPilot Cloud: reported deliveries, fees, and the scheduled queue. (Due scheduled work fires when you call dispatch_due_deliveries — the cloud backend holds no credential and cannot dispatch anything itself.)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
schedule_batch ~224
Schedule a whole event's deliveries in one call — a restaurant launch, a catering run, office-lunch drops. Each item needs external_delivery_id, dropoff_address, dropoff_phone_number, and order_value (cents); tip and dropoff_instructions are optional. pickup_address applies to items that don't set their own. dispatch_at: ISO-8601 UTC for the FIRST dispatch; stagger_minutes spreads the rest (e.g. 12 deliveries, stagger 15 = one drop every 15 minutes, so the kitchen is never slammed). Everything lands in the due queue as unsigned payloads and fires via dispatch_due_deliveries. Moves no money NOW, but commits N future dispatches the user's poller will execute with their key: ALWAYS summarize the full plan — count, addresses, window, estimated total fees — and get the user's explicit confirmation before scheduling.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveries | array | yes | – |
| dispatch_at | string | yes | – |
| pickup_address | string | – | – |
| stagger_minutes | integer | – | – |
No output schema declared.
No examples provided.
schedule_delivery ~275
Schedule a delivery for later. DashPilot Cloud stores ONLY the unsigned payload — no signing secret, no bearer token, nothing it could spend. When dispatch_at arrives, call dispatch_due_deliveries (from this machine) to fire due work: a fresh 60-second JWT is minted locally at that moment and the delivery goes straight to DoorDash. Moves no money NOW, but commits a future dispatch your poller will execute with your key: confirm the plan (address, time, estimated fee) with the user before scheduling. dispatch_at: ISO-8601 UTC time to dispatch, e.g. 2026-08-27T18:30:00Z. Other parameters are identical to get_delivery_quote.
| Name | Type | Req | Description |
|---|---|---|---|
| contactless_dropoff | boolean | – | – |
| dispatch_at | string | yes | – |
| dropoff_address | string | yes | – |
| dropoff_contact_family_name | – | – | – |
| dropoff_contact_given_name | – | – | – |
| dropoff_instructions | – | – | – |
| dropoff_phone_number | string | yes | – |
| external_delivery_id | string | yes | – |
| order_value | integer | yes | – |
| pickup_address | string | yes | – |
| pickup_business_name | – | – | – |
| pickup_instructions | – | – | – |
| pickup_reference_tag | – | – | – |
| tip | integer | – | – |
No output schema declared.
No examples provided.
sync_diagnostics ~33
Routine connectivity sync with DashPilot Cloud: checks for updated dispatch settings (feature flags, default tip, Drive environment).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
track_delivery ~48
Live status straight from DoorDash: stage (created → picked_up → delivered), Dasher name/location once assigned, ETA, and the customer tracking URL.
| Name | Type | Req | Description |
|---|---|---|---|
| external_delivery_id | string | yes | – |
No output schema declared.
No examples provided.
update_delivery ~67
Update an active delivery's tip, dropoff instructions, or contact phone. Tip changes MOVE MONEY — confirm the new amount with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| dropoff_instructions | – | – | – |
| dropoff_phone_number | – | – | – |
| external_delivery_id | string | yes | – |
| tip | – | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.dashpilot-labs/dashpilot-mcp server?
io.github.dashpilot-labs/dashpilot-mcp runs locally as a PyPI package, launched with uvx doordash-dashpilot-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · doordash-dashpilot-mcp
claude mcp add dashpilot-labs-dashpilot-mcp -- uvx doordash-dashpilot-mcp
What is the io.github.dashpilot-labs/dashpilot-mcp server?
io.github.dashpilot-labs/dashpilot-mcp is listed in the public MCP registry as io.github.dashpilot-labs/dashpilot-mcp. DoorDash Drive deliveries over MCP, quote, dispatch, and track deliveries from your POS. This page covers its PyPI package (doordash-dashpilot-mcp).
Is the io.github.dashpilot-labs/dashpilot-mcp server safe to use?
io.github.dashpilot-labs/dashpilot-mcp scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 io.github.dashpilot-labs/dashpilot-mcp server expose?
io.github.dashpilot-labs/dashpilot-mcp exposes 17 tools: check_drive_connection, get_delivery_quote, accept_quote, dispatch_delivery, schedule_delivery, and 12 more. Their descriptions and schemas cost roughly 1,827 tokens of context every time the server is loaded.
Is the io.github.dashpilot-labs/dashpilot-mcp server still maintained?
io.github.dashpilot-labs/dashpilot-mcp is still listed as active in the MCP registry. We last reached this channel on 18 October 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.dashpilot-labs/dashpilot-mcp server under?
io.github.dashpilot-labs/dashpilot-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.