Skip to content

madeira.fun Hiking Permits MCP server

fun.madeira/hiking-permitsmadeira.funstreamable-httpv1.2.0Scanned

Madeira hiking permit trails: availability for 120 days, fees, booking links and reservations.

8 tools: 1 can delete or cancel things, 1 do something that can't be undone, 2 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • 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 madeira.fun Hiking Permits MCP server can do

The madeira.fun Hiking Permits MCP server is published by madeira.fun, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: confirm_reservation), do things that cannot be undone, such as sending, paying or publishing (check_trail_availability) and create or change data (2 tools: build_booking_link and start_reservation). 4 tools only read.

3 tools bring in text other people can write (get_permit_fees, start_reservation and confirm_reservation); 1 tool can send data out of your system (check_trail_availability).

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

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 1.2.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.

8 tools

Deletes or cancels 1Claude Code: deny
  • confirm_reservationStep 2 of 2: with the code the visitor got by email, madeira.fun signs them in, checks the start time live and submits the government reservation for exactly what start_reservation…Reads text others writeNo findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Step 2 of 2: with the code the visitor got by email, madeira.fun signs them in, checks the start time live and submits the government reservation for exactly what start_reservation described. The answer gives order_id and status_token. The reservation is not paid: madeira.fun then emails the government's PayPay link, and the visitor must pay the permit fee to the government within 24 hours, or before the start time if that is sooner, or it lapses. Safe to retry: calling it again with the same reservation_token returns the same order and never books twice (also after a lost answer). At most 5 reservations per email per day through apps.

    Annotations the server declares

    • title: Confirm a Permit Reservation
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Can't be undone 1Claude Code: ask
  • check_trail_availabilityDay-by-day permit availability for one trail, from today up to 119 days ahead (Madeira dates).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 "check_trail_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":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
    Day-by-day permit availability for one trail, from today up to 119 days ahead (Madeira dates). Each day is open (start times left for visitors), full (sold out for visitors), started (today only: every start time has already begun, nothing is left to book today; not sold out), closed, no_times (no start times listed) or unknown (not checked yet), with permits left for visitors and when it was last checked. Use date for one day, or from and to for a range; the default is the next 7 days. For the start times of a day, use get_start_times.

    Annotations the server declares

    • title: Check Trail Availability
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • start_reservationStep 1 of 2 to reserve a Madeira hiking permit for a visitor through madeira.fun.Reads text others writeNo findings

    Why it is in this group

    • The name "start_reservation" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Step 1 of 2 to reserve a Madeira hiking permit for a visitor through madeira.fun. Before calling, tell the visitor these three points in your own words and get their yes: (1) madeira.fun creates a madeira.fun account with the visitor's email address (or signs in the one they already have). (2) madeira.fun sends that email address and the party size to the Madeira government's Simplifica system (IFCN), which issues the permit. The name stays with madeira.fun. (3) Reserving is not paying: the government's PayPay payment link arrives by email, and the visitor must pay the permit fee to the government within 24 hours, or before the start time if that is sooner, or the reservation lapses. madeira.fun charges nothing and never collects the permit fee. This step checks the start time and emails the visitor a 6-digit code from madeira.fun; nothing is reserved yet. Then ask the visitor for the code and call confirm_reservation. Standard visitor reservations only (no Madeira residents, no Verified Permit): for those use build_booking_link. Today up to 119 days ahead. At most 3 codes per email per hour. For apps calling from a server: a call from a web page is refused.

    Annotations the server declares

    • title: Start a Permit Reservation
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • get_permit_feesThe government hiking permit fee records in force today (format MF-PRC-1.0, the same records as https://madeira.fun/hiking/permit-data), with legal references and exemptions.Reads text others writeNo findings

    Why it is in this group

    • The name "get_permit_fees" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The government hiking permit fee records in force today (format MF-PRC-1.0, the same records as https://madeira.fun/hiking/permit-data), with legal references and exemptions. Give trail to get the fee that applies to that trail. The fee is paid to the government, never to madeira.fun.

    Annotations the server declares

    • title: Get Permit Fees
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_reservation_statusWhere a reservation made with confirm_reservation stands: being reserved, waiting for payment (with the government's PayPay link, the amount and the deadline), paid, not taken, can…No findings

    Why it is in this group

    • The name "get_reservation_status" says "get": a word for reading.
    Description, as the server wrote it
    Where a reservation made with confirm_reservation stands: being reserved, waiting for payment (with the government's PayPay link, the amount and the deadline), paid, not taken, cancelled or lapsed. Needs order_id and status_token from confirm_reservation.

    Annotations the server declares

    • title: Get Reservation Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_start_timesGive trail (required without a partner key).No findings

    Why it is in this group

    • The name "get_start_times" says "get": a word for reading.
    Description, as the server wrote it
    Give trail (required without a partner key). The start times of a trail with the permits left for visitors at each one (as the trail page shows them: a number from 6 up, "few" at 1 to 5, "full" at 0), and a book_url per open start time that opens Reserve on madeira.fun at that time. Today up to 119 days ahead: give trail and date, or from and to (up to 14 days per call). Further ahead, up to 365 days: one trail and one date per call. Start times that have already begun today are never listed. Rate limited; a partner key (Authorization: Bearer mfk_...) gives higher limits, longer ranges and every trail at once (omit trail).

    Annotations the server declares

    • title: Get Start Times
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_permit_trailsList the Madeira trails that need a government hiking permit for a set start time and can be reserved on madeira.fun.No findings

    Why it is in this group

    • The name "list_permit_trails" says "list": a word for reading.
    Description, as the server wrote it
    List the Madeira trails that need a government hiking permit for a set start time and can be reserved on madeira.fun. Returns each trail's seo_slug (use it in the other tools), code (such as PR 18 or PS PR 1), name, island, official trail status, trail page and day feed links. Optional query filters by code or name, accents ignored.

    Annotations the server declares

    • title: List Permit Trails
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: 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 write3
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 29, 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 destructive, 1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://madeira.fun/api/mcp: tools/list returned 8 tools to an anonymous client, including confirm_reservation (destructive), check_trail_availability (irreversible), build_booking_link (write), start_reservation (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 2 to 4

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

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

    What this check looks for
  • The server marks "build_booking_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "build_booking_link" says "link": a word for a change.

    What this check looks for

History

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

  1. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
    • Tools that change things, listed without credentials: 2 to 4
  3. Tools3 added, 1 changed.+3 added~1 changedView diff
  4. Tools1 added, 1 changed.+1 added~1 changedView diff

Install

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

claude mcp add --transport http hiking-permits https://madeira.fun/api/mcp
claude mcp add --transport http hiking-permits https://madeira.fun/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__hiking-permits__list_permit_trails",
      "mcp__hiking-permits__get_start_times",
      "mcp__hiking-permits__get_permit_fees",
      "mcp__hiking-permits__get_reservation_status"
    ],
    "ask": [
      "mcp__hiking-permits__check_trail_availability",
      "mcp__hiking-permits__build_booking_link",
      "mcp__hiking-permits__start_reservation"
    ],
    "deny": [
      "mcp__hiking-permits__confirm_reservation"
    ]
  }
}

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 hiking-permits. Review it before you use it.

Capability tags behind 4 rules
  • mcp__hiking-permits__check_trail_availability outbound
  • mcp__hiking-permits__get_permit_fees untrusted-input
  • mcp__hiking-permits__start_reservation untrusted-input
  • mcp__hiking-permits__confirm_reservation 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/fun.madeira/hiking-permits/verify?hash=ba5d8ff930e403badc1b9a7fcad99e10ab3e82965f48cb8dfe01d14abe7ade17" | jq -e '.changed == false'

Pinned hash ba5d8ff930e4, from Nov 8, 2026, 20:18 UTC.

Watch

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

https://radar.anlyon.com/servers/fun.madeira/hiking-permits/changes.xml

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

Badge

Anlyon Radar badge for fun.madeira/hiking-permits
[![Anlyon Radar](https://radar.anlyon.com/badge/fun.madeira/hiking-permits.svg)](https://radar.anlyon.com/servers/fun.madeira/hiking-permits)

Source: MCP Registry. Synced Oct 23, 2026, 14:20 UTC.

madeira.fun Hiking Permits MCP server: questions and answers

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

Is the madeira.fun Hiking Permits MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the madeira.fun Hiking Permits MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: confirm_reservation.

Can the madeira.fun Hiking Permits MCP server do things that cannot be undone?

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

What tools does the madeira.fun Hiking Permits MCP server have?

8 tools: 1 destructive, 1 irreversible, 2 write, 4 read. confirm_reservation, check_trail_availability, build_booking_link, start_reservation, list_permit_trails, get_start_times, get_permit_fees and get_reservation_status.

Does the madeira.fun Hiking Permits MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the madeira.fun Hiking Permits 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): check_trail_availability.

Has the madeira.fun Hiking Permits MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.