Skip to content

Hüttentouren MCP server

org.huettentouren/tourshuettentouren.orgstreamable-httpv1.0.0Scanned

Hut-to-hut hiking tours in the Alps with live availability from multiple booking systems.

3 tools: 1 do something that can't be undone and 2 only read.

Tools: 0 delete, 1 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 1 finding

Sign-in required, no OAuth metadata. 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.
Govern this server →

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 Hüttentouren MCP server can do

The Hüttentouren MCP server is published by huettentouren.org, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (recommend_tours), but cannot delete data. 2 tools only read.

1 tool can send data out of your system (recommend_tours).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in.

Last scanned Nov 18, 2026, version 1.0.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.

3 tools

Can't be undone 1Claude Code: ask
  • recommend_toursRecommend fitting hut-to-hut tours using structured tour data and fresh availability rules.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 "recommend_tours" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Recommend fitting hut-to-hut tours using structured tour data and fresh availability rules. Each result includes `url`, the canonical huettentouren.org detail page — link users there, not to any upstream source.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
Only reads 2Show 2 read-only tools
  • fetchFetch compact, curated details for one published hut-to-hut tour.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch compact, curated details for one published hut-to-hut tour. The returned `url` is the canonical huettentouren.org detail page — link users there.

    Annotations the server declares

    • readOnlyHint: true
    • 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 or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
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
  • WarnThe whole server

    The endpoint asks for credentials (HTTP 401) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.

    Matched text

    https://www.huettentouren.org/api/mcp: initialize answered HTTP 401, with a WWW-Authenticate header

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "recommend_tours" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tours https://www.huettentouren.org/api/mcp
claude mcp add --transport http tours https://www.huettentouren.org/api/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tours__search",
      "mcp__tours__fetch"
    ],
    "ask": [
      "mcp__tours__recommend_tours"
    ],
    "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 tours. Review it before you use it.

Capability tags behind 1 rule
  • mcp__tours__recommend_tours outbound

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/org.huettentouren/tours/verify?hash=bdd1ffda465cf013a20f1d16e91055b71233aefff214e91c6a65f47c3da67604" | jq -e '.changed == false'

Pinned hash bdd1ffda465c, from Nov 18, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.huettentouren/tours/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.huettentouren/tours
[![Anlyon Radar](https://radar.anlyon.com/badge/org.huettentouren/tours.svg)](https://radar.anlyon.com/servers/org.huettentouren/tours)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

Hüttentouren MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hüttentouren MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 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 Hüttentouren MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hüttentouren MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: recommend_tours.

What tools does the Hüttentouren MCP server have?

3 tools: 1 irreversible, 2 read. recommend_tours, search and fetch.

Does the Hüttentouren MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and no OAuth protected resource metadata was found.

Does the Hüttentouren 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): recommend_tours.

Has the Hüttentouren MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.