Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.stopful/road-trip-planner

REMOTE · STOPFUL.COM · SCANNED AUG 3

Plot an AI-planned road trip onto an editable Stopful map — drive times, hotels & EV chargers.

Available components

remote · stopful.com 75
+8 this week 75 Trust /100
Trust breakdown (6 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 →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 971 tokens (~485/item across 2 items; 1 tools + 1 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 Management23
  • Stability observed for 7 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · stopful.com

# add to Claude Code
claude mcp add --transport http com-stopful-road-trip-planner https://stopful.com/api/mcp
# ~/.codex/config.toml
[mcp_servers.com-stopful-road-trip-planner]
url = "https://stopful.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-stopful-road-trip-planner": {
      "type": "remote",
      "url": "https://stopful.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-stopful-road-trip-planner --url https://stopful.com/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-stopful-road-trip-planner:
    url: "https://stopful.com/api/mcp"
// mcp.json
{
  "mcpServers": {
    "com-stopful-road-trip-planner": {
      "type": "http",
      "url": "https://stopful.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 2 Aug 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.

  • 31 Jul 26 +3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “plot_trip” rewrote its description, which is the text the model reads security
    • Tool “plot_trip” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 2.13.0 → 2.29.0 functional
    • “plot_trip” reworded the description of “days” cosmetic
    • “plot_trip” reworded the description of “stops” cosmetic
    • “plot_trip” reworded the description of “id” cosmetic
  • 29 Jul 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “plot_trip” rewrote its description, which is the text the model reads security
    • Schema quality: 257 → 425 ▼ functional
    • Server version: 2.10.0 → 2.13.0 functional
    • “plot_trip” added an optional parameter “days” cosmetic
    • “plot_trip” added an optional parameter “id” cosmetic
    • “plot_trip” made “stops” optional cosmetic
  • 28 Jul 26 +3
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “plot_trip” rewrote its description, which is the text the model reads security
    • Schema quality: 156 → 257 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 2.1.0 → 2.10.0 functional
  • 27 Jul 26 67

    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 3 Aug 2026 · Probed https://stopful.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stopful.com CN=YR2,O=Let's Encrypt,C=US 18 Jun 2026 16 Sept 2026 RSA 2048 SHA256-RSA 562b5bb9b8f063a7edd1630f788c7674bdc
SANs: stopful.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of stopful.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
stopful.com. absent 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=63072000
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stopful.com/api/mcp Verified 200
http (plaintext) http://stopful.com/api/mcp HTTPS enforced 308 https://stopful.com/api/mcp
MCP tools — 1 exposed · ~688 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.

Tool Tokens
plot_trip ~688

Creates a road trip on Stopful, or updates one plotted earlier, and returns an interactive map of it — adding, removing, reordering or renaming stops, changing nights, dates or party size, and redrawing the route. Renders a multi-stop driving route as an interactive map and returns a link to it, plus an inline map in clients that support one. Takes a list of stops in driving order, each with a place name, optional decimal lat/lon and number of nights; a stop without coordinates is geocoded from its name, and coordinates that fall far from where the name resolves are reported back in the result. Accepts an optional trip name, start date, party size, and a day-by-day itinerary that becomes a day view over the map. The map shows per-leg drive times and distances, and is editable: the traveller can drag a pin to move a stop or drag the route to add one, and their changes are saved to the trip. Covers road trips and other multi-stop routes; a single destination or a route with no stops to draw has nothing to render. The result contains the map link, the trip as structured data, and the trip's `id` (see the `id` parameter for updating an existing trip).

NameTypeReqDescription
daysarray—The day-by-day itinerary: one entry per calendar day of the trip, in order, each with a title and the day's activities. It renders as a tappable day view over the map, and selecting a day highlights…
guestsobject—Optional party size.
idstring—Optional. Id of a trip returned by an earlier call, identifying which trip this call applies to. To change an existing trip, send its `id` together with the COMPLETE new `stops` and `days` — the call…
namestring—Optional trip name (e.g. 'Lisbon → Pyrenees'). Defaults to first → last stop.
startDatestring—Optional trip start as ISO yyyy-mm-dd.
stopsarrayyesThe route in driving order, 1 to 40 entries (the first is the origin). Required for a normal call — the only call that omits it is `id` on its own, which re-reads a saved trip unchanged. Each entry n…
NameTypeReqDescription
assumedarray—Stops placed from their name alone because no coordinates were given — approximate pins.
daysarray—The day-by-day itinerary, when one was supplied.
editTokenstring—Capability token the map widget uses to save the traveller's own changes. It is not an argument of this tool and never needs sending back — updating a trip needs only its `id`.
idstring—The trip's id. Pass it back as the `id` argument to apply a later change to this same trip.
keptByTravellerarray—Stops left where the traveller placed them on the map, so the coordinates supplied in this call were not applied.
notFoundarray—Stops that were requested but could not be placed, so they are absent from the map and the route.
tripobjectyesThe trip as rendered, after geocoding and (on a continuation) merging the traveller's own map edits.
unchangedboolean—True when the call only read the saved trip and changed nothing — an `id` sent with no `stops`.
urlstringyesLink that opens this trip on the map at stopful.com.
warningsarray—Stops whose supplied coordinates are far from where their name resolves, with the distance and the resolved position.

No examples provided.