fun.madeira/hiking-permits
Registry code: 137709e7ed70dbed
madeira.fun publishes availability for Madeira's permit trails: the classified walking routes that need a government permit for a set start time.
Typical flow: list_permit_trails to find a trail and its seo_slug, check_trail_availability for the day or days (open, full, closed, no_times or unknown, with permits left for visitors), get_permit_fees for the government fee, and build_booking_link for the link the visitor opens.
- endpoint
- https://madeira.fun/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is fun.madeira/hiking-permits live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is fun.madeira/hiking-permits free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does fun.madeira/hiking-permits have?
- 4 tools: build_booking_link, check_trail_availability, get_permit_fees, list_permit_trails.
- Is fun.madeira/hiking-permits safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_permit_fees open 1h ago
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.
{ "type": "object", "properties": { "trail": { "type": "string", "maxLength": 120, "minLength": 1, "description": "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." } }, "additionalProperties": false }arguments 12 lineslist_permit_trails open 1h ago
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.
{ "type": "object", "properties": { "query": { "type": "string", "maxLength": 120, "description": "Optional filter: a code such as \"PR 18\" or a name such as \"Pico Ruivo\"." } }, "additionalProperties": false }arguments 11 linesbuild_booking_link unknown never probed
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 presses Reserve: madeira.fun submits the government reservation for them and emails a PayPay link to pay the government fee.
{ "type": "object", "required": [ "trail", "date" ], "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "The hike date (YYYY-MM-DD, a Madeira calendar date)." }, "lang": { "enum": [ "en", "pt", "es", "de", "fr", "ru", "lv", "it", "pl", "ro", "nl", "cs", "da", "sv", "no", "fi", "hu", "tr" ], "type": "string", "description": "Page language." }, "trail": { "type": "string", "maxLength": 120, "minLength": 1, "description": "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." }, "adults": { "type": "integer", "maximum": 60, "minimum": 0, "description": "Visitors aged 13 or over who are not Madeira residents (they pay the government fee)." }, "children": { "type": "integer", "maximum": 60, "minimum": 0, "description": "Visitors aged 12 or under who are not Madeira residents (no fee, still part of the reservation)." } }, "additionalProperties": false }arguments 57 linescheck_trail_availability unknown 1h ago
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, 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. Start times are not returned: they are on the trail page that each day's book_url opens.
{ "type": "object", "required": [ "trail" ], "properties": { "to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Last day of a range (YYYY-MM-DD, a Madeira calendar date)." }, "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "One day (YYYY-MM-DD, a Madeira calendar date)." }, "from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "First day of a range (YYYY-MM-DD, a Madeira calendar date)." }, "trail": { "type": "string", "maxLength": 120, "minLength": 1, "description": "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." } }, "additionalProperties": false }arguments 30 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id137709e7ed70dbed.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/137709e7ed70dbed/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/137709e7ed70dbed?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.