Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
madeira.fun Hiking Permits is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Madeira hiking permit trails: availability for 120 days, fees, booking links and reservations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http madeira-fun-hiking-permits-mcp https://madeira.fun/api/mcp
# 2 — ask your agent for something these tools do
# list_permit_trails, check_trail_availability, get_start_times and 5 more
madeira.fun Hiking Permits costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http madeira-fun-hiking-permits-mcp https://madeira.fun/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional filter: a code such as "PR 18" or a name such as "Pico Ruivo". |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trail | string | yes | The trail: its seo_slug from list_permit_trails (preferred), a code such as "PR 18", "PR18" or "PS PR1", or a name such as "Levada do Rei". Accents are ignored. |
| date | string | no | One day (YYYY-MM-DD, a Madeira calendar date). |
| from | string | no | First day of a range (YYYY-MM-DD, a Madeira calendar date). |
| to | string | no | Last day of a range (YYYY-MM-DD, a Madeira calendar date). |
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 d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trail | string | no | The trail: its seo_slug from list_permit_trails (preferred), a code such as "PR 18", "PR18" or "PS PR1", or a name such as "Levada do Rei". Accents are ignored. Required, except for a partner key aski |
| date | string | no | One day (YYYY-MM-DD, a Madeira calendar date). |
| from | string | no | First day of a range (YYYY-MM-DD, a Madeira calendar date). |
| to | string | no | Last day of a range (YYYY-MM-DD, a Madeira calendar date). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trail | string | no | Optional. The trail: its seo_slug from list_permit_trails (preferred), a code such as "PR 18", "PR18" or "PS PR1", or a name such as "Levada do Rei". Accents are ignored. |
Build the link a visitor opens to book a permit: https://madeira.fun/hiking/<seo_slug>?date=YYYY-MM-DD opens that date's start times on the trail page. Optional adults (visitors aged 13 or over who are not Madeira residents) and children (aged 12 or under, no fee) preset the party; lang sets the page language. The link books and stores nothing. On the page the visitor picks a start time and presse
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trail | string | yes | The trail: its seo_slug from list_permit_trails (preferred), a code such as "PR 18", "PR18" or "PS PR1", or a name such as "Levada do Rei". Accents are ignored. |
| date | string | yes | The hike date (YYYY-MM-DD, a Madeira calendar date). |
| adults | integer | no | Visitors aged 13 or over who are not Madeira residents (they pay the government fee). |
| children | integer | no | Visitors aged 12 or under who are not Madeira residents (no fee, still part of the reservation). |
| lang | string | no | Page language. |
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 (IF
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trail | string | yes | The trail: its seo_slug from list_permit_trails (preferred), a code such as "PR 18", "PR18" or "PS PR1", or a name such as "Levada do Rei". Accents are ignored. |
| date | string | yes | The hike date (YYYY-MM-DD, a Madeira calendar date). |
| start_time | string | yes | The begin of an open start time from get_start_times, HH:MM (Madeira time). |
| adults | integer | no | Visitors aged 13 or over who are not Madeira residents (each pays the government fee). |
| children | integer | no | Visitors aged 12 or under who are not Madeira residents (no fee, still part of the reservation). |
| name | string | yes | The visitor's name, for their madeira.fun reservation (madeira.fun keeps it; the government gets the email and the party size). |
| string | yes | The visitor's email: madeira.fun sends the code there, creates or signs in their madeira.fun account with it, and the government's payment link and permit go there. Not an Apple Hide My Email address. | |
| lang | string | no | Language of madeira.fun's emails (default en). |
| visitor_agreed | boolean | yes | true only after the visitor heard the three points in this tool's description and said yes. The emailed code is what confirms 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 bef
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_token | string | yes | The reservation_token start_reservation returned, unchanged. |
| code | string | yes | The code from the madeira.fun email, digits only. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | order_id from confirm_reservation. |
| status_token | string | yes | status_token from confirm_reservation. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install madeira.fun Hiking Permits or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_permit_trails | no tags | |
| check_trail_availability | no tags | |
| get_start_times | no tags | |
| get_permit_fees | no tags | |
| build_booking_link | no tags | |
| start_reservation | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| confirm_reservation | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_reservation_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish madeira.fun Hiking Permits can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.