Portugal (public data)
REMOTE · MCP.THIAGOLANNES.COM · 2 COMPONENTS
Portugal public data: weather, INE, Parliament, contracts, SNS, fuel, transit, power cuts.
Available components
Last scanned (12 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 72 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 14565 tokens (~202/item across 72 items; 72 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 72 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 73 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 72 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 12798 → 14565 ▼ functional
- Server version: 0.8.0 → 0.10.1 functional
- New tool “protected_areas” functional
- New tool “broadband_coverage” functional
- New tool “diario_republica” functional
- New tool “election_results” functional
- New tool “notable_trees” functional
- New tool “post_offices” functional
- New tool “reservoir_levels” functional
- New tool “school_stats” functional
- 14 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.7.0 → 0.8.0 functional
- New tool “electricity_grid” functional
- New tool “porto_sensors” functional
- New tool “porto_road_closures” functional
- New tool “lisbon_metro_status” functional
- New tool “electricity_local” functional
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “public_holidays” rewrote its description, which is the text the model reads security
- Server version: 0.6.2 → 0.7.0 functional
- New tool “web_archive_search” functional
- New tool “web_archive_page” functional
- New tool “web_archive_history” functional
- “public_holidays” added an optional parameter “municipality” cosmetic
- 12 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.thiagolannes.com/portugal
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thiagolannes.com | CN=WE1,O=Google Trust Services,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | b44ad43804279de00eb9fed2fc2e2129 |
| SANs: thiagolannes.com, mcp.thiagolannes.com, *.mcp.thiagolannes.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.thiagolannes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| thiagolannes.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.thiagolannes.com/portugal | Verified | 200 | |
| http (plaintext) | http://mcp.thiagolannes.com/portugal | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
reservoir_levels ~106
How full mainland Portugal's reservoirs are, per river basin, in the latest month published. Args: basin: optional, e.g. "Tejo", "Douro", "Guadiana", "Sado", "Ribeiras do Algarve", "Arade". Each basin has its % of capacity, the historical average for that month, the same month a year before and the capacity in hm³; plus the capacity-weighted mainland total.
| Name | Type | Req | Description |
|---|---|---|---|
| basin | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
school_stats ~187
Statistics for schools in mainland Portugal (InfoEscolas, Ministry of Education). Args: school: part of a school's name ("Pedro Nunes", "Marquês de Pombal") or its DGEEC code. municipality: list that municipality's schools (e.g. "Braga"). level: "1ciclo", "2ciclo", "3ciclo", "secundario" (science-humanities, default) or "profissional" (vocational). Each school has its students, retention or dropout rate per grade, the share finishing the cycle on time next to the national figure for students with a similar profile, and (3rd cycle) direct-success paths. The national totals come with every answer.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | – |
| limit | integer | – | – |
| municipality | – | – | – |
| school | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sea_forecast ~108
Coastal sea forecast: wave height and period, wave direction, sea temperature (IPMA). Args: place: coastal spot, e.g. "Nazaré", "Peniche", "Faro", "Funchal". Or pass lat/lon for the nearest one. day: 0 = today, 1 = tomorrow, 2 = the day after.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | – |
| lat | – | – | – |
| lon | – | – | – |
| place | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sns_consultation_wait_stats ~259
Hospital outpatient consultations per month and the % of FIRST specialist consultations (referred by a family doctor via CTH/SIGA) held within the guaranteed maximum time (TMRG). Use for "how long is the wait for a first hospital appointment at X?", "is hospital Y on time with first consultations?", "how many consultations did the Centro region do?". Official monthly statistics (latest month usually 2-3 months back, provisional); there is no breakdown by specialty in the open data. Per period (latest first): consultations_in_month / _year_to_date (total, first, subsequent) and first_consultations_within_max_time_pct for the month and year-to-date. Args: institution: Hospital or ULS name; mapped to its ULS. region: Norte | Centro | LVT (Lisboa) | Alentejo | Algarve. Ignored if institution is given. period: Latest month to include, "YYYY-MM" (default: newest available). months: How many months back (default 6, max 24).
| Name | Type | Req | Description |
|---|---|---|---|
| institution | – | – | – |
| months | integer | – | – |
| period | – | – | – |
| region | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sns_emergency_stats ~367
Emergency-department (urgência) visits per month: by type and by Manchester triage colour. Use for "how busy is the ER at X?", "how many emergency visits in the Algarve last month?", "what share of ER visits are green/blue (non-urgent)?". OFFICIAL MONTHLY STATISTICS ONLY — not the live queue (the latest month is usually 2-3 months back and provisional). For live waiting times send the user to https://tempos.min-saude.pt. Not medical advice: in an emergency call 112; SNS 24 (808 24 24 24) for advice. Scope: one institution, one region, or (neither) all of mainland Portugal's SNS hospitals. Per period (latest first): visits_in_month and visits_year_to_date by type (general, paediatric, obstetric, psychiatric, total), triage_in_month by colour (red = immediate, orange = very urgent, yellow = urgent, green = less urgent, blue = non-urgent, white = not clinical / other) and triage_share_in_month_pct. Args: institution: Hospital or ULS name, accent-insensitive ("Santa Maria", "São João", "Hospital de Faro"). A hospital is mapped to its ULS; check `scope`. region: Norte | Centro | LVT (Lisboa) | Alentejo | Algarve. Ignored if institution is given. period: Latest month to include, "YYYY-MM" (default: newest available). months: How many months back to return (default 6, max 24).
| Name | Type | Req | Description |
|---|---|---|---|
| institution | – | – | – |
| months | integer | – | – |
| period | – | – | – |
| region | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sns_find_institutions ~331
Find SNS hospitals / local health units (ULS) by name, or the nearest ones to a coordinate. Use this first when the user names a hospital or a place ("hospitals near Lisbon", "is there an emergency department near 38.72,-9.14?"), then pass `stats_entity` to sns_emergency_stats / sns_surgery_wait_stats / sns_consultation_wait_stats. Each result: name, its parent ULS, coordinates, distance_km (when lat/lon given), whether it reports emergency / consultation / surgery data on tempos.min-saude.pt, and `stats_entity` — the name under which the official statistics report it (statistics are per ULS / hospital group, not per building). This list does NOT contain live waiting times; for live emergency waits send the user to https://tempos.min-saude.pt. Args: query: Part of the name, accent-insensitive, e.g. "Santa Maria", "Faro", "ULS Algarve". lat, lon: Sort by distance from this point (WGS84), e.g. Lisbon 38.7223, -9.1393. Without `query`, umbrella ULS entries are skipped (they duplicate a hospital's location). emergency_only: Only places that report emergency-department data. limit: Max results (default 10, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| emergency_only | boolean | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sns_query_dataset ~346
Run an ODSQL query on any SNS Transparency portal dataset (Opendatasoft Explore API v2.1). Use after sns_search_datasets for anything the curated tools don't cover. Clauses are ODSQL: - where: `instituicao like "santa maria" and tempo >= date'2026-01-01'` (`like` is a case- and accent-insensitive "contains"; dates use date'YYYY-MM-DD') - select: `tempo, instituicao, total_urgencias` or aggregates `sum(total_urgencias) as total` - group_by: `regiao` or `tempo` (combine with aggregates in select) - order_by: `tempo desc` Most hospital-activity datasets (field `tempo`, monthly) store YEAR-TO-DATE CUMULATIVE values: December is the annual total; a single month = this month minus the previous one. Many datasets have a `regiao` and an `instituicao` (or `entidade`) field. Official statistics, not live data. Args: dataset_id: e.g. "ocupacao-do-internamento" (from sns_search_datasets). where, select, group_by, order_by: ODSQL clauses (optional). limit: Rows to return (default 20, max 100). offset: Skip rows, for paging.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| group_by | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| order_by | – | – | – |
| select | – | – | – |
| where | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sns_search_datasets ~197
Search the ~150 datasets of the SNS Transparency portal (titles and descriptions are in Portuguese). Use when the curated tools don't cover the question — e.g. hospital bed occupancy ("ocupação"), births/caesareans ("partos"), INEM pre-hospital calls, SNS 24 calls, family doctor coverage ("médico de família", "inscritos"), medicines spending, staff ("trabalhadores"), cancer screening ("rastreios"). Then call sns_query_dataset with the dataset_id and the field names returned here. Portuguese keywords work best; matching is accent-insensitive. Args: query: Keywords, e.g. "ocupação internamento", "partos", "urgência". Empty = list all (id + title). limit: Max results (default 10, max 50; ignored when listing all).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
sns_surgery_wait_stats ~352
Surgery access indicators per month: surgical waiting list, % within the guaranteed maximum time, mean days from admission to surgery, and surgeries performed. Use for "how long is the wait for surgery at X?", "how many people are on the surgery list in the Norte region?", "how many operations did hospital Y do?". Official monthly statistics (latest month usually 2-3 months back, provisional). The open data has NO breakdown by specialty or procedure — say so if asked for one. Per period (latest first): - waiting_list: patients on the surgical waiting list (LIC) at month end, how many are still within the legal maximum guaranteed response time (TMRG, 180 days for normal priority since 2018) and the % within it. - mean_days_before_surgery_in_month / _year_to_date: average days between hospital admission and the operation for scheduled inpatient surgery (this is NOT the time on the waiting list). - surgeries_in_month / surgeries_year_to_date: scheduled (= inpatient + day surgery) and urgent. Args: institution: Hospital or ULS name ("Santa Maria", "Coimbra", "IPO Porto"); mapped to its ULS. region: Norte | Centro | LVT (Lisboa) | Alentejo | Algarve. Ignored if institution is given. period: Latest month to include, "YYYY-MM" (default: newest available). months: How many months back (default 6, max 24).
| Name | Type | Req | Description |
|---|---|---|---|
| institution | – | – | – |
| months | integer | – | – |
| period | – | – | – |
| region | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
tourism_places ~193
Official tourism places in Portugal, near a point or in a municipality/region. Args: kind: one of blue_flag_beaches, surf_spots, golf, spas, unesco, historic_villages, schist_villages, wine_villages, mountain_villages, marinas, walking_routes, santiago_ways, hotels. place: municipality, parish, district or region name, e.g. "Cascais", "Algarve", "Peniche". name: part of the name, e.g. "Nazaré", "Pestana". lat, lon: closest first, within radius_km (max 200).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| name | – | – | – |
| place | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
transit_departures ~243
Scheduled departures from a station or stop (official timetable, not live). Args: stop: station or stop name, e.g. "Lisboa Oriente", "Cais do Sodré", "Baixa-Chiado", "Prazeres". operator: an operator id (see transit_operators) or a city/region: "porto", "coimbra", "braga", "aveiro", "cascais", "barreiro", "algarve", "faro", "madeira", or "intercity" (FlixBus coaches and CP). Default: CP and the Lisbon operators. when: ISO date-time in Lisbon time, e.g. "2026-11-03T08:00". Default: now. window_minutes: how far ahead to look (max 720). line: keep only a line or destination, e.g. "28E", "Sintra", "Azul".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| line | – | – | – |
| operator | – | – | – |
| stop | string | yes | – |
| when | – | – | – |
| window_minutes | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
transit_find_stops ~188
Find train stations, metro stations or bus/tram stops by name, or the nearest to a point. Args: query: e.g. "Oriente", "Porto Campanhã", "Marquês de Pombal", "Prazeres". operator: an operator id (see transit_operators) or a city/region: "porto", "coimbra", "braga", "aveiro", "cascais", "barreiro", "algarve", "faro", "madeira", or "intercity" (FlixBus coaches and CP). Default: CP and the Lisbon operators. lat, lon: find the nearest instead of (or as well as) by name.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| operator | – | – | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
transit_operators ~24
Which transport operators have timetables here, and what each one covers.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
transit_trips_between ~224
Direct services between two stations (no changes), with departure, arrival and duration. Examples: CP "Lisboa Oriente" → "Porto Campanhã"; Fertagus "Roma-Areeiro" → "Setúbal"; Metro "Alameda" → "Aeroporto" (same line only). Scheduled times, not live. Args: operator: an operator id (see transit_operators) or a city/region: "porto", "coimbra", "braga", "aveiro", "cascais", "barreiro", "algarve", "faro", "madeira", or "intercity" (FlixBus coaches and CP). Default: CP and the Lisbon operators. when: ISO date-time in Lisbon time; default now. window_minutes: departures within this window (max 1440).
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| limit | integer | – | – |
| operator | – | – | – |
| origin | string | yes | – |
| when | – | – | – |
| window_minutes | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
transit_vehicles ~185
Where the buses (and Lisbon trams) are right now: live positions reported by the vehicles. Args: operator: "stcp" (Porto buses), "smtuc" (Coimbra buses) or "carris" (Lisbon buses and trams). City names work too: "porto", "coimbra", "lisboa". line: keep one line, e.g. "500", "205", "28E", "103". lat, lon: keep the vehicles near this point (within radius_km), closest first. For Greater-Lisbon buses use bus_vehicle_positions / bus_next_arrivals (Carris Metropolitana).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| limit | integer | – | – |
| line | – | – | – |
| lon | – | – | – |
| operator | string | yes | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
weather_forecast ~118
5-day weather forecast for a place in Portugal (IPMA, official). Args: place: district capital or island town, e.g. "Lisboa", "Porto", "Faro", "Funchal", "Ponta Delgada". lat, lon: use instead of place for anywhere else; the nearest IPMA forecast location is used. Returns daily min/max temperature, rain probability, weather type, wind, and today's UV index.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| lon | – | – | – |
| place | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
weather_warnings ~94
Active IPMA weather warnings (rain, wind, heat, cold, snow, fog, sea, thunderstorms). Args: area: optional district or island group, e.g. "Lisboa", "Madeira", "Açores". Omit for the whole country. include_green: also list green (no-warning) entries. Default false.
| Name | Type | Req | Description |
|---|---|---|---|
| area | – | – | – |
| include_green | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
web_archive_history ~93
When was a web address captured by Arquivo.pt, and how often did its content change? Returns the first and last capture, captures per year and up to `max_versions` versions where the content changed (spread over the period), each with a link to the archived copy.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | – |
| max_versions | integer | – | – |
| to_date | – | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
web_archive_page ~113
The text of a web page as Arquivo.pt saved it closest to a date. `when` takes a year, "YYYY-MM" or "YYYY-MM-DD" (default: the latest copy). Returns the capture date, the page title, its readable text (cut at `max_chars`, up to 8000) and the archive link. Quote it briefly; the archive link shows the full page.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| url | string | yes | – |
| when | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
web_archive_search ~142
Search old versions of Portuguese websites in Arquivo.pt (full text, since 1996). `site` limits to one domain (e.g. "publico.pt", "cm-porto.pt"). `from_date`/`to_date` take a year, "YYYY-MM" or "YYYY-MM-DD". Each result has the capture date, title, a short snippet and a link to the archived copy. Good for "what did the news say about X in 2010?".
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| site | – | – | – |
| to_date | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
where_is ~42
Which parish, municipality and district a coordinate is in, plus altitude, land use and hazard maps.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
wildfires ~224
Burnt areas from wildfires in Portugal, mapped by satellite (EFFIS / Copernicus). Not a live list of fires in progress: EFFIS maps burnt areas from satellite a day or more later, and small fires can be missing. Args: period: "today", "week", "month" or "season" (this year so far). Ignored when `year` is given. year: a past year from 2016, for the whole year. place: keep fires whose region or parish contains this, e.g. "Algarve", "Monchique", "Viseu". min_hectares: only fires at least this large. sort: "area" (largest first) or "date" (newest first). limit: max fires listed (totals always cover every match).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_hectares | number | – | – |
| period | string | – | – |
| place | – | – | – |
| sort | string | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Portugal (public data) MCP server?
Portugal (public data) is a hosted endpoint at https://mcp.thiagolannes.com/portugal, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.thiagolannes.com
claude mcp add --transport http thiagojacoblannes-portugal-mcp 'https://mcp.thiagolannes.com/portugal'
What is the Portugal (public data) MCP server?
Portugal (public data) is an MCP server listed in the public MCP registry as io.github.ThiagoJacobLannes/portugal-mcp. Portugal public data: weather, INE, Parliament, contracts, SNS, fuel, transit, power cuts. This page covers its hosted endpoint (https://mcp.thiagolannes.com/portugal).
Is the Portugal (public data) MCP server safe to use?
Portugal (public data) scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Portugal (public data) MCP server expose?
Portugal (public data) exposes 72 tools: weather_forecast, weather_warnings, fire_risk, sea_forecast, earthquakes, and 67 more. Their descriptions and schemas cost roughly 12,084 tokens of context every time the server is loaded.
Does the Portugal (public data) MCP server require authentication?
No. We connected to Portugal (public data) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Portugal (public data) MCP server still maintained?
Portugal (public data) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Portugal (public data) MCP server?
VerifyMCP ran 11 checks on Portugal (public data), covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Portugal (public data): Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.