Stockholm Archipelago Trail MCP server
se.xcqt/stockholm-archipelago-trailxcqt.sestreamable-httpv1.3.0Scanned
Trail stages, ferry piers, timetabled day trips and A→B routes for the Stockholm Archipelago Trail.
10 tools: 1 do something that can't be undone, 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Stockholm Archipelago Trail MCP server can do
The Stockholm Archipelago Trail MCP server is published by xcqt.se, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (plan_route) and create or change data (3 tools: day_trip, check_day_trip and multi_day), but cannot delete data. 6 tools only read.
1 tool brings in text other people can write (place_details); 1 tool can send data out of your system (plan_route).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 22, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Can't be undone 1Claude Code: ask
plan_routePlan a multimodal A→B route between two trail sections (islands), or between an island and a mainland ferry hub (Strömkajen, Vaxholm, Årsta, Stavsnäs …): walk → ferry → walk, with …Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "plan_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Plan a multimodal A→B route between two trail sections (islands), or between an island and a mainland ferry hub (Strömkajen, Vaxholm, Årsta, Stavsnäs …): walk → ferry → walk, with departure/arrival times, walking distances and pier names. Use this when the user wants to travel from one island to another, out to an island from the mainland, or home from an island (or asks how to get between two places on the trail). From/to take the same identifiers as fetch (sat:section:…, slug or uid). Same section for both returns a walk-only route. Do not use for a round trip to a single island (use day_trip) or for multi-day trips (use multi_day). If the user has not named the two islands, pick two neighbouring stages with search first and then call this tool. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
Changes things 3Claude Code: ask
check_day_tripSame data as day_trip but renders NO card.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Same data as day_trip but renders NO card. Use this when you need to check or compare day trips across dates, departure hubs or stages before recommending one, or for follow-up questions where no new card is wanted. Same arguments and response as day_trip (section, date, hub, targetKm, direction, towards). Do not use for the final recommendation shown to the user (use day_trip) — call day_trip once for the trip you recommend.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
day_tripPlan a ready round-trip day trip to one trail section (island) of the Stockholm Archipelago Trail on a given date.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Plan a ready round-trip day trip to one trail section (island) of the Stockholm Archipelago Trail on a given date. Returns the best ferry hub to depart from, outbound and return ferry times, the walking time around the island and how many ferries run that day. Use this when the user wants a day-trip suggestion to a single island. Section takes the same identifiers as fetch (sat:section:…, slug or uid). Pass targetKm when the user asks for a shorter or longer walk than the full stage; the response then describes that walk and permalink opens it in the planner. Do not use for a one-way trip between two islands (use plan_route), for probing several dates or hubs before recommending one (use check_day_trip), or for multi-day trips (use multi_day). ALWAYS follow this call with show_section_map for the same section, date and targetKm so the user also sees the walk on the map — the map is the main deliverable, not optional. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
multi_dayPlan a multi-day trip on the Stockholm Archipelago Trail: an overnight stay on one island, or an island hop across up to four stages, with the ferries and the walk for each day.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Plan a multi-day trip on the Stockholm Archipelago Trail: an overnight stay on one island, or an island hop across up to four stages, with the ferries and the walk for each day. Use this when the user wants a hike over several days, an overnight stay on an island, or to combine two or more islands. Sections take the same identifiers as fetch (sat:section:…, slug or uid), in the order they should be visited. sections and date are both OPTIONAL: omit sections and the planner picks well-served stages; omit date and it uses the next Saturday — so call this tool for ANY multi-day request ("plan a 3-day hike"), never answer from search/fetch alone. Do not use for single-day trips (use day_trip) or A→B between two islands on one day (use plan_route). ALWAYS follow this call with show_section_map for the first stage of the trip (same date) so the user sees the route on a map. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
Only reads 6Show 6 read-only tools
fetchFetch the full machine-readable record (JSON-LD) for one object by identifier.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it Fetch the full machine-readable record (JSON-LD) for one object by identifier. Accepts sat-ids (sat:section:…, sat:pier:…, sat:vessel:…, sat:poi:…, sat:trail:…, sat:report:…), section slugs, legacy OSM ids (osm:node:…), Wikidata QIDs (wikidata:Q…), GTFS stop ids (gtfs:…) and Swedish AED-registry ids (shr:…). Deleted objects return a tombstone record with status "gone". Use this when you already have an object identifier — from search or an earlier response — and need its full record. Do not use for searching by name (use search) or for trip planning (use day_trip/plan_route).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
pier_departuresList the scheduled Waxholmsbolaget ferry departures (or arrivals) at one pier or harbour of the Stockholm Archipelago Trail on a given date, within a time window: departure time, l…No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List the scheduled Waxholmsbolaget ferry departures (or arrivals) at one pier or harbour of the Stockholm Archipelago Trail on a given date, within a time window: departure time, line, destination and stops on the way, arrival time at the final stop, whether advance booking is required, and which boat is the last of the day. Use this when the user asks what boats leave from or arrive at a specific pier or island ("which boats leave Grinda this afternoon?", "when is the last ferry back from Utö tonight?"). The pier can be given by name (island or pier, e.g. 'Grinda', 'Stavsnäs'), slug or id (sat:pier:…, GTFS stop id); when a name matches several piers the response lists them (kind 'ambiguous') — ask the user or pick the obvious one and call again. Renders no card. Do not use for planning a whole trip (use day_trip/plan_route) or for lodging and places (use search).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
place_detailsGet the full record for one place, stage, pier or vessel on the Stockholm Archipelago Trail by identifier: description, photo (image.contentUrl with credit/license), opening hours,…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get the full record for one place, stage, pier or vessel on the Stockholm Archipelago Trail by identifier: description, photo (image.contentUrl with credit/license), opening hours, website/phone, accessibility, SAT passport info and links. Use this when the user asks about a specific place ("tell me more about Arholma handel") and you have its id (sat:poi:…, sat:section:…, sat:pier:…) from a map card, search or an earlier response. Same data as fetch. Do not use for searching by name (use search) or for trip planning (use day_trip/plan_route).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
searchSearch the published objects of the Stockholm Archipelago Trail: trail sections (stages), the trail itself, ferry piers, ferry vessels, reviewed public reports and points of intere…No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search the published objects of the Stockholm Archipelago Trail: trail sections (stages), the trail itself, ferry piers, ferry vessels, reviewed public reports and points of interest (lodging, food, shops, nature). Returns matching objects with their permanent sat-identifiers. Use this when the user names or describes a place, stage, pier, vessel or POI category and you need to find its identifier before calling another tool. Do not use for general Sweden/Stockholm travel, gear or weather questions — those are outside this dataset.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
show_imagesShow photos of one trail section (island) of the Stockholm Archipelago Trail: the stage hero image plus photos of places (lodging, food, nature) along it, each with credit and lice…No findings
Why it is in this group
- The name "show_images" says "show": a word for reading.
Description, as the server wrote it Show photos of one trail section (island) of the Stockholm Archipelago Trail: the stage hero image plus photos of places (lodging, food, nature) along it, each with credit and license. Use this when the user wants to SEE what a section looks like. Takes the same identifiers as fetch (sat:section:…, slug or uid). Do not use for maps (use show_section_map).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
show_section_mapShow an interactive map of one trail section (stage) of the Stockholm Archipelago Trail, with the hiking route and ferry piers.No findings
Why it is in this group
- The name "show_section_map" says "show": a word for reading.
Description, as the server wrote it Show an interactive map of one trail section (stage) of the Stockholm Archipelago Trail, with the hiking route and ferry piers. Use this when the user wants to SEE a section on a map. Takes the same identifiers as fetch (sat:section:…, slug or uid). Pass targetKm (and optionally date) to draw a shorter or longer walk instead of the full stage. Do not use for comparing several stages side by side (use search/fetch). This tool renders an interactive map card itself — NEVER build your own map, chart, image or file from geojsonUrl or the coordinates; just call the tool and let the card show. IMPORTANT: every call to this tool renders a card in the conversation. Call it at most ONCE per answer, for the single option you recommend. Never use it to compare or probe alternatives. The card already shows ferry times, piers and walking times — do not restate them in your reply; add only advice, caveats and next steps.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://map.stockholmarchipelagotrail.com/mcp: tools/list returned 10 tools to an anonymous client, including plan_route (irreversible), day_trip (write), check_day_trip (write), multi_day (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnplan_route
The server marks "plan_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http stockholm-archipelago-trail https://map.stockholmarchipelagotrail.com/mcpclaude mcp add --transport http stockholm-archipelago-trail https://map.stockholmarchipelagotrail.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__stockholm-archipelago-trail__search",
"mcp__stockholm-archipelago-trail__fetch",
"mcp__stockholm-archipelago-trail__show_section_map",
"mcp__stockholm-archipelago-trail__show_images",
"mcp__stockholm-archipelago-trail__place_details",
"mcp__stockholm-archipelago-trail__pier_departures"
],
"ask": [
"mcp__stockholm-archipelago-trail__day_trip",
"mcp__stockholm-archipelago-trail__check_day_trip",
"mcp__stockholm-archipelago-trail__plan_route",
"mcp__stockholm-archipelago-trail__multi_day"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stockholm-archipelago-trail. Review it before you use it.
Capability tags behind 2 rules
- mcp__stockholm-archipelago-trail__plan_route outbound
- mcp__stockholm-archipelago-trail__place_details untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/se.xcqt/stockholm-archipelago-trail/verify?hash=5fe5243ebaca62fc6d5ba2942d5057cd1facfa9b8032b4293c5cf375e2156810" | jq -e '.changed == false'Pinned hash 5fe5243ebaca, from Nov 22, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/se.xcqt/stockholm-archipelago-trail/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/se.xcqt/stockholm-archipelago-trail)Source: MCP Registry · repository. Synced Nov 7, 2026, 23:18 UTC.
Stockholm Archipelago Trail MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Stockholm Archipelago Trail MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Stockholm Archipelago Trail MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Stockholm Archipelago Trail MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: plan_route.
What tools does the Stockholm Archipelago Trail MCP server have?
- 10 tools: 1 irreversible, 3 write, 6 read. plan_route, day_trip, check_day_trip, multi_day, search, fetch, show_section_map, show_images and 2 more.
Does the Stockholm Archipelago Trail MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Stockholm Archipelago Trail MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): plan_route.
Has the Stockholm Archipelago Trail MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 22, 2026.