Ext Ops Panel
Open dashboard
Comparison

io.github.openvancamp/openvan-travel vs Stayspan Schengen Days

io.github.openvancamp/openvan-travel is an MCP server published by openvancamp. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Stayspan Schengen Days is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.openvancamp/openvan-travelStayspan Schengen Days
Official MCP Registry Listed
Version: 0.12.1
Downloads/month (npm): 3 223
Downloads/week (npm): 994
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
No figure published
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.12.1
Downloads/month (npm): 3 223
Downloads/week (npm): 994
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.openvancamp/openvan-travel vs Stayspan Schengen Days
Factio.github.openvancamp/openvan-travelStayspan Schengen Days
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)2026-11-08Not published
Where it runs (differs)Remote server or your machineRemote server (schengen-days.zovo.one/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/openvancamp/openvan-camp-public-apiNot stated
Changes in the last 7 days (differs)30
First seen (differs)2026-10-122026-10-22
Endpoint at the last check (differs)Responded 8 h agoResponded 17 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.openvancamp/openvan-travel

In its own words, on Official MCP Registry:

Vanlife & RV data: roadbooks, fuel, tolls, ferries, visas, holidays, hazards, weather. openvan.camp

Stayspan Schengen Days

In its own words, on Official MCP Registry:

Plan Schengen short stays with a rolling 90/180 rule calculator and a daily CSV download.

How to run each

io.github.openvancamp/openvan-travel As a remote MCP server

Claude Code
claude mcp add --transport http openvan-travel https://mcp.openvan.camp/mcp

Stayspan Schengen Days As a remote MCP server

Claude Code
claude mcp add --transport http schengen-days https://schengen-days.zovo.one/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of Stayspan Schengen Days nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.openvancamp/openvan-travel · What it can do: Stayspan Schengen Days · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built