com.stopful/road-trip-planner
REMOTE · STOPFUL.COM · SCANNED SEP 21
Plot an AI-planned road trip onto an editable Stopful map — drive times, hotels & EV chargers.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 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 1368 tokens (~684/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the com.stopful/road-trip-planner MCP server?
com.stopful/road-trip-planner is a hosted endpoint at https://stopful.com/api/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 · stopful.com
claude mcp add --transport http com-stopful-road-trip-planner 'https://stopful.com/api/mcp'
{
"mcpServers": {
"com-stopful-road-trip-planner": {
"url": "https://stopful.com/api/mcp"
}
}
} {
"servers": {
"com-stopful-road-trip-planner": {
"type": "http",
"url": "https://stopful.com/api/mcp"
}
}
} [mcp_servers.com-stopful-road-trip-planner] url = "https://stopful.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-stopful-road-trip-planner": {
"type": "remote",
"url": "https://stopful.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-stopful-road-trip-planner --url 'https://stopful.com/api/mcp' --transport streamable-http
mcp_servers:
com-stopful-road-trip-planner:
url: "https://stopful.com/api/mcp" {
"McpServers": {
"com-stopful-road-trip-planner": {
"Transport": "http",
"Url": "https://stopful.com/api/mcp"
}
}
} assistant mcp add com-stopful-road-trip-planner -t streamable-http -u 'https://stopful.com/api/mcp'
{
"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.
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.
- 19 Sept 26 0
- Resource “Stopful trip map” now points somewhere else: ui://stopful/map-5.0.0.html → ui://stopful/map-5.2.0.html security
- 18 Sept 26 0
- Resource “Stopful trip map” now points somewhere else: ui://stopful/map-4.44.0.html → ui://stopful/map-5.0.0.html security
- “plot_trip” reworded the description of “focusDay” cosmetic
- 17 Sept 26 0
- “plot_trip” reworded the description of “stops” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 8 Sept 26 0
- Resource “Stopful trip map” now points somewhere else: ui://stopful/map-4.37.0.html → ui://stopful/map-4.44.0.html security
- 7 Sept 26 0
- Resource “Stopful trip map” now points somewhere else: ui://stopful/map-4.27.0.html → ui://stopful/map-4.37.0.html security
- Schema quality: 544 → 626 ▼ functional
- Server version: 2.46.0 → 2.47.0 functional
- “plot_trip” added an optional parameter “focusDay” cosmetic
- “plot_trip” reworded the description of “id” cosmetic
- 6 Sept 26 0
- Resource “Stopful trip map” now points somewhere else: ui://stopful/map.html → ui://stopful/map-4.27.0.html security
- Server version: 2.44.0 → 2.46.0 functional
- 5 Sept 26 0
- Server version: 2.42.0 → 2.44.0 functional
- “plot_trip” reworded the description of “days” cosmetic
- “plot_trip” reworded the description of “id” cosmetic
- 30 Aug 26 +7
- Stability: fail → pass ▲ security
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 Sept 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=YR1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | RSA 2048 | SHA256-RSA | 56be55f7c7815caa6323021e9aebeb947ac |
| SANs: stopful.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
plot_trip ~1,070
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 an estimate of what the trip will cost before anything is booked, 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).
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | – | 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… |
| focusDay | integer | – | Optional. Open the map on this day of the itinerary, 1 = the first day. The map shows ONE DAY at a time: the chosen day's stops, activities and driving, with the rest of the route greyed. Use it WITH… |
| guests | object | – | Optional party size. |
| id | string | – | Id of a trip returned by an earlier call. SEND IT whenever this call is about a trip already plotted in this conversation — showing one of its days, fixing a stop, changing the route. WITHOUT `id` a… |
| name | string | – | Optional trip name (e.g. 'Lisbon → Pyrenees'). Defaults to first → last stop. |
| startDate | string | – | Optional trip start as ISO yyyy-mm-dd. |
| stops | array | yes | The 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| assumed | array | – | Stops placed from their name alone because no coordinates were given — approximate pins. |
| days | array | – | The day-by-day itinerary. Activities may include ones the traveller added in the planner rather than through this tool. |
| focusDay | integer | – | Set when the call asked for one day: the map opens on that day of the itinerary, 1 = the first day. |
| id | string | – | The trip's id. Pass it back as the `id` argument to apply a later change to this same trip. |
| keptByTraveller | array | – | Stops left where the traveller placed them on the map, so the coordinates supplied in this call were not applied. |
| notFound | array | – | Stops that were requested but could not be placed, so they are absent from the map and the route. |
| trip | object | yes | The trip as rendered, after geocoding and (on a continuation) merging the traveller's own map edits. |
| unchanged | boolean | – | True when the call only read the saved trip and changed nothing — an `id` sent with no `stops`. |
| url | string | yes | Link that opens this trip on the map at stopful.com. |
| warnings | array | – | Stops whose supplied coordinates are far from where their name resolves, with the distance and the resolved position. |
No examples provided.
What is the com.stopful/road-trip-planner MCP server?
com.stopful/road-trip-planner is an MCP server listed in the public MCP registry as com.stopful/road-trip-planner. Plot an AI-planned road trip onto an editable Stopful map, drive times, hotels & EV chargers. This page covers its hosted endpoint (https://stopful.com/api/mcp).
Is the com.stopful/road-trip-planner MCP server safe to use?
com.stopful/road-trip-planner scores 87 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 com.stopful/road-trip-planner MCP server expose?
com.stopful/road-trip-planner exposes 1 tool: plot_trip. Their descriptions and schemas cost roughly 1,070 tokens of context every time the server is loaded.
Does the com.stopful/road-trip-planner MCP server require authentication?
No. We connected to com.stopful/road-trip-planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.stopful/road-trip-planner MCP server still maintained?
com.stopful/road-trip-planner is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.