MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

Stockholm Archipelago Trail

Trail stages, ferry piers, timetabled day trips and A→B routes for the Stockholm Archipelago Trail.

Checks passed
13 / 22

1 failed · 8 not measured

Median response
115 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
10

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 115 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name sat-objects.

  • Pass
    Lists tools

    tools/list returned 10 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 115 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 115 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    42 of 42 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Fail
    Website matches publisher

    The website host does not match the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-07T22:44:00.78856Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Stockholm Archipelago Trail

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http stockholm-archipelago-trail https://map.stockholmarchipelagotrail.com/mcp

Capabilities

Tools 10

check_day_trip

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.

Discovered
day_trip

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.

Discovered
fetch

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).

Discovered
multi_day

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.

Discovered
pier_departures

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).

Discovered
place_details

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).

Discovered
plan_route

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.

Discovered
search

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.

Discovered
show_images

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).

Discovered
show_section_map

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected115 ms10