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.

Delivery Planner by Spoke

REMOTE · DELIVERYPLANNER.COM

Plan and optimize a multi-stop delivery route, then share it with your driver.

+3 this week 76 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability50
  • 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1398 tokens (~155/item across 9 items; 6 tools + 3 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 Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% of tool parameters carry a description.Partial
  • Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1

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

  • 11 Nov 26 0
    • Tool “confirm_route” rewrote its description, which is the text the model reads security
  • 10 Nov 26 +1

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

  • 8 Nov 26 +1

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

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 · Probed https://deliveryplanner.com/api/free-route-planner/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=deliveryplanner.com CN=WE1,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA256 c9c779d2f5fb9fc80ebf8b2cc49d9624
SANs: deliveryplanner.com, *.deliveryplanner.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of deliveryplanner.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
deliveryplanner.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy object-src 'none'; base-uri 'self'; manifest-src 'self'; report-to default;
x-content-type-options nosniff
referrer-policy no-referrer-when-downgrade
permissions-policy accelerometer=(), camera=(), gyroscope=(), microphone=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://deliveryplanner.com/api/free-route-planner/mcp Verified 200
http (plaintext) http://deliveryplanner.com/api/free-route-planner/mcp HTTPS enforced 301 https://deliveryplanner.com/api/free-route-planner/mcp
MCP tools · 6 exposed · ~756 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
confirm_route ~167

Called by the address panel when the user clicks Optimize. Records the chosen addresses and route settings and returns the single-use confirmationToken that create_route takes. Not for direct model use.

NameTypeReqDescription
distanceUnitstring––
endPlaceIdstring–Omit to return to the start location.
ignoredFieldsarray–Unsupported input fields excluded from optimization, listed in the result.
startPlaceIdstringyesStart location returned by search_places.
startTime––Departure date/time with UTC offset; null when unspecified. Does not change traffic estimates.
stopPlaceIdsarrayyesUnordered delivery locations returned by search_places. Array position does not constrain visit order; the optimizer reorders these stops.
timeAtStopMinutesinteger––

No output schema declared.

No examples provided.

create_route ~170

Optimizes and saves one driving route for one driver with 1–20 delivery stops, from the addresses and settings the user confirmed in the address panel. Use this when a user asks what order to visit delivery addresses, wants an efficient driving route between multiple stops, or wants a route they can open and share. Takes the single-use token the panel issues when the user clicks Optimize route. Returns the stops in optimized order, estimated duration and distance, the route geometry, and route links. Every call creates a new route, and anyone with the returned link can view its addresses. Does not enforce delivery time windows, and not for package tracking, public transit, multiple drivers, or live-traffic estimates.

NameTypeReqDescription
confirmationTokenstring–Single-use token returned when the user clicks Optimize in the address panel.
NameTypeReqDescription
dispatchUrlstringyes–
distanceMetersnumberyes–
distanceUnitstringyes–
driverUrlstringyes–
durationMinutesnumberyes–
encodedPolylinestringyesSaved driving route overview in Google encoded polyline format (precision 5). Empty when route geometry is unavailable.
estimateNoticestringyes–
ignoredFieldsarrayyes–
routeUrlstringyes–
startTimestring|nullyes–
stopsarrayyes–
timeAtStopMinutesnumberyes–

No examples provided.

resolve_current_location ~44

Returns the nearest address for coordinates from the Use current location button in the panel, to fill the start.

NameTypeReqDescription
latitudenumberyes–
longitudenumberyes–
NameTypeReqDescription
placesarrayyes–

No examples provided.

search_places ~139

Finds Google address suggestions, with place IDs, for one address or place name. Use this when a user wants to plan deliveries, order driving stops, or optimize a multi-stop driving route and provides addresses or place names, including pasted spreadsheets, tables, CSV, or numbered lists. Suggestions come from autocomplete and are not validated addresses. Not for general place recommendations, package tracking, or public-transit directions.

NameTypeReqDescription
locationBiasobject–Optional search-area coordinates from the user or a verified location source. Biases suggestions toward this area without restricting them to it. Radius is in metres and defaults to 5000.
querystringyes–
NameTypeReqDescription
placesarrayyes–

No examples provided.

select_addresses ~151

Shows a panel where the user picks a match for each address and sets the start, finish, time at each stop and distance unit. Takes each original address with its suggested matches; addresses without suggestions let the user search again in the panel. Missing start and finish appear as empty fields, and fields in routeSettings.ignoredFields are listed as not applied. Read-only: when the user clicks Optimize, the panel issues a single-use confirmation token for route creation.

NameTypeReqDescription
addressesarrayyes–
routeSettingsobject–Initial route settings. The form collects start, end (or a return to the start), time at stop and distance unit, and adds empty start and finish fields when they are missing.
NameTypeReqDescription
addressesarrayyes–
dispatchUrlstringyes–
ignoredFieldLabelsarrayyes–
routeSettingsobjectyesInitial route settings. The form collects start, end (or a return to the start), time at stop and distance unit, and adds empty start and finish fields when they are missing.

No examples provided.

show_dispatch_options ~85

Shows a link to Spoke Dispatch, our route planner for teams, for needs this free planner does not cover: multiple drivers, enforced delivery time windows, or more than 20 delivery stops. Use this only when the user explicitly asks for one of those. It only displays the link; it does not transfer addresses or create a Dispatch account.

NameTypeReqDescription
reasonstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Delivery Planner by Spoke MCP server?

Delivery Planner by Spoke is a hosted endpoint at https://deliveryplanner.com/api/free-route-planner/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · deliveryplanner.com

# add to Claude Code
claude mcp add --transport http com-deliveryplanner-delivery-planner 'https://deliveryplanner.com/api/free-route-planner/mcp'
Common questions

What is the Delivery Planner by Spoke MCP server?

Delivery Planner by Spoke is an MCP server listed in the public MCP registry as com.deliveryplanner/delivery-planner. Plan and optimize a multi-stop delivery route, then share it with your driver. This page covers its hosted endpoint (https://deliveryplanner.com/api/free-route-planner/mcp).

Is the Delivery Planner by Spoke MCP server safe to use?

Delivery Planner by Spoke scores 76 out of 100 on VerifyMCP. 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 Delivery Planner by Spoke MCP server expose?

Delivery Planner by Spoke exposes 6 tools: search_places, create_route, confirm_route, select_addresses, show_dispatch_options, resolve_current_location. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

Does the Delivery Planner by Spoke MCP server require authentication?

No. We connected to Delivery Planner by Spoke without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Delivery Planner by Spoke MCP server still maintained?

Delivery Planner by Spoke 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 did VerifyMCP test on the Delivery Planner by Spoke MCP server?

VerifyMCP ran 14 checks on Delivery Planner by Spoke, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.