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 (11 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 →
active_incidents ~276
What emergency services (civil protection, ANEPC) are responding to right now in Portugal, closest first. Live occurrences of every kind: fires, road collisions, fallen trees, floods, rescues, with their status (e.g. "Em Curso"), time started and resources on scene. Updated every few minutes. Police-only activity (PSP/GNR) is not published anywhere and is not included. Args: near: a postal code ("4450-208") or municipality ("Matosinhos") to search around; any other text (a parish or village) filters by the incident's location name instead. lat, lon: search around these coordinates (best when the user shares their location). radius_km: search radius around the point (default 10, max 100). kind: "all", "fire", "road", "weather" (trees, floods, wind, landslides) or "rescue". limit: max incidents listed (counts always cover every match). With no place at all, returns the national picture (counts by kind and district, biggest first).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| near | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bpstat_search ~171
Find Banco de Portugal statistical series by keyword. Examples: "euribor 12 meses", "taxa de juro novos empréstimos habitação", "dólar", "dívida pública", "depósitos particulares", "preços habitação". The search picks the most likely statistical domains (or the one you pass as domain_id) and searches the series inside them; it also lists every domain so you can retry with a specific domain_id. The first search of a domain takes a few seconds to a minute; then it is cached for a week. Args: lang: "PT" or "EN" (labels are richer in PT).
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | – | – | – |
| lang | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
bpstat_series ~123
Observations of Banco de Portugal series (ids from bpstat_search). Args: series_ids: one or more series ids (max 10), e.g. [12559924]. last_n: latest observations per series (1-500). Ignored when `since` is given. since: "YYYY-MM-DD" — return every observation from this date. lang: "PT" or "EN".
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| last_n | integer | – | – |
| series_ids | array | yes | – |
| since | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
broadband_coverage ~147
Which fixed broadband technologies reach a place in Portugal, according to ANACOM: fibre, coaxial cable (DOCSIS 3.1 / 3.0) and copper with ADSL, with the date of the data. Args: near: a postal code ("1100-148"; the full 7 digits is the most precise) or a municipality; or pass lat/lon for an exact point. It does not say which operator offers it, and mobile coverage is not included (ANACOM publishes that per operator only as a map at geo.anacom.pt).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| lon | – | – | – |
| near | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bus_find_stops ~244
Find Carris Metropolitana bus stops by name and/or near a coordinate. Use this first whenever the user names a place, street, station or gives a location, to get the stop_id needed by bus_next_arrivals. Results include the lines serving each stop. Args: query: Text to match in the stop name (accent/case-insensitive, all words must match), e.g. "Gare do Oriente", "Cacilhas terminal". A 6-digit stop id also works. lat, lon: A coordinate (WGS84). Results are sorted by straight-line distance from it. Note: buses inside Lisbon city are mostly run by Carris (a different company, not covered here); Carris Metropolitana serves the wider region. radius_m: Only stops within this many metres of lat/lon. Default 500 when no query is given; unlimited when a query is given. limit: Max stops to return (default 10, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| query | – | – | – |
| radius_m | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bus_line_info ~201
Details of a Carris Metropolitana line: name, route ends, directions, municipalities. Use for "where does line 4715 go?", "which bus goes from Cacilhas to Almada?", or to check whether a line passes a stop (include_stops=True). If `line` is not an exact line number it is treated as text (e.g. "Oriente Setubal") and the matching lines are listed instead. trips_today = 0 means the line does not run today (some lines are seasonal or weekday-only). Departure times past midnight are written "24:30", "25:10" (same service day). Args: line: 4-digit line number ("4715") or free text matched against line names. include_stops: Also list every stop (id + name) in order for each direction.
| Name | Type | Req | Description |
|---|---|---|---|
| include_stops | boolean | – | – |
| line | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
bus_next_arrivals ~199
Upcoming buses at a Carris Metropolitana stop, real-time where available. Use for "when is the next bus at X?" (get stop_id from bus_find_stops first). Each arrival says whether it is "realtime" (live GPS estimate) or "scheduled" (timetable only: the bus may not have started its trip yet). minutes_from_now uses the real-time estimate when present. Times are Europe/Lisbon. Only today's operational day is covered, so late at night the list may be short or empty. Args: stop_id: 6-digit stop id, e.g. "060361". line_id: Optional 4-digit line number to keep only that line, e.g. "2794". limit: Max arrivals to return (default 10, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| line_id | – | – | – |
| stop_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
bus_service_alerts ~203
Service alerts (detours, works, strikes, stops not served) for Carris Metropolitana. Use before recommending a trip, or when the user asks "is line X disrupted?". Filter by line and/or stop; with no filter, returns all current alerts (there are often ~100). Alerts are mostly published in Portuguese only. Args: line_id: 4-digit line number, e.g. "4407". stop_id: 6-digit stop id, e.g. "160584". include_upcoming: Also return alerts that start in the future (default True). language: Preferred language ("pt" or "en"); falls back to what exists. limit: Max alerts to return (default 20, max 100).
| Name | Type | Req | Description |
|---|---|---|---|
| include_upcoming | boolean | – | – |
| language | string | – | – |
| limit | integer | – | – |
| line_id | – | – | – |
| stop_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bus_vehicle_positions ~103
Live GPS positions of the buses currently running on a Carris Metropolitana line. Use for "where is the 3508 right now?" or to see how many buses are out on a line. Each vehicle includes its position, heading, speed, the stop it is at / heading to, and how many seconds old the fix is. Args: line_id: 4-digit line number, e.g. "3508".
| Name | Type | Req | Description |
|---|---|---|---|
| line_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
diario_republica ~111
What the latest Diário da República issue published, with a link to each act. Args: series: 1 (laws, decree-laws, ordinances, government resolutions; default) or 2 (dispatches, notices, appointments, tenders: hundreds per day). query: optional words to filter titles and summaries, e.g. "IRS", "habitação", "Saúde".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | – | – | – |
| series | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
earthquakes ~102
Recent earthquakes recorded by IPMA. Args: region: "mainland" (mainland Portugal and Madeira) or "azores". days: look back this many days (max 30). min_magnitude: only quakes at or above this magnitude. limit: max rows (newest first).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
| min_magnitude | number | – | – |
| region | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
election_results ~279
Official results of a Portuguese election for the country, a district, a municipality or a parish. Args: election: "legislativas2025" (default), "legislativas2024", "legislativas2022", "autarquicas2025", "autarquicas2021", "europeias2024", "presidenciais2021"; or just "autarquicas", "europeias"... for the latest of that kind. place: None for Portugal; a municipality ("Sintra", "Lisboa"), "municipality, parish" ("Lisboa, Arroios"), a district written as "distrito de Braga" (the electoral circle in legislative elections), or "Açores" / "Madeira" for the whole region. body: local elections only: "CM" (câmara, default), "AM" (assembleia municipal) or "AF" (assembleia de freguesia, use with a parish). Returns turnout, blank and null votes, and votes, % and seats per list, plus the previous election of the same kind for that place (lists are not matched: coalitions change).
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| election | string | – | – |
| limit | integer | – | – |
| place | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
electricity_grid ~95
How much electricity mainland Portugal used on a day, the peak, and how much wind, solar and hydro the distribution grid generated (E-REDES, 15-minute data, usually one day behind). Args: day: "YYYY-MM-DD" (default: the latest complete day, usually yesterday). Big power stations feed the transmission grid (REN) and show here only as one total.
| Name | Type | Req | Description |
|---|---|---|---|
| day | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
electricity_local ~129
Electricity in one place (mainland Portugal): billed consumption per month, and how often and for how long the power went out there in recent years compared with the average municipality. Args: municipality: a concelho, e.g. "Sintra". postal_code: "2710" or "2710-123" (consumption is published per 4-digit area); its municipality is used for the outage figures. months: how many recent months of consumption (max 60).
| Name | Type | Req | Description |
|---|---|---|---|
| months | integer | – | – |
| municipality | – | – | – |
| postal_code | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
electricity_price ~119
Portugal's day-ahead wholesale electricity price (OMIE), per 15-minute period, in €/MWh. Useful for indexed ("dynamic") tariffs: when is electricity cheapest to run the washing machine or charge the car. Not the retail price on a normal bill. Args: day: ISO date, e.g. "2026-11-10". Default: the most recent day OMIE has published. cheapest: also list this many cheapest periods (max 12).
| Name | Type | Req | Description |
|---|---|---|---|
| cheapest | integer | – | – |
| day | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ev_charger_detail ~126
Everything about one MOBI.E charging site: all its points with live status, power, connectors and price, plus operator contact, opening hours and accepted authentication (app, RFID card, credit card...). Use after ev_chargers. Accepts a site_id (e.g. "EZC-AMD-00051"), a point_id (e.g. "AMD-00051-1") or an EVSE id (e.g. "PT*EZC*E*AMD*00051*1").
| Name | Type | Req | Description |
|---|---|---|---|
| site_or_point_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ev_chargers ~397
Public EV charging sites near a point in Portugal (MOBI.E network), nearest first, with live status and the price the network publishes for each charging point. Use for "where can I charge near X?", "fast chargers near me", "is there a free CCS charger nearby?". Needs coordinates; if the user gives a place name, use known coordinates for it. Covers mainland Portugal, Azores and Madeira. Args: lat, lon: Point to search around (WGS84). radius_km: Search radius (default 5, max 100). min_power_kw: Only points that can deliver at least this power, e.g. 50 for fast DC. connector: "CCS" (CCS2), "Type 2", "CHAdeMO", "CEE", or "DC" / "AC". available_only: Only points whose live status is "available" right now. limit: Max sites to return (default 10, max 50). Each site: operator, address, distance_km, opening hours and its matching points, each with status (available, in use, out of order...), max power, connectors and price (per_kwh / per_minute / per_session in EUR, from the feed). IMPORTANT: these are the charging operator's published fees and may not be the whole bill: see `price_note` and tell the user. `data_freshness` says how old the inventory and live status are. The first call of the day downloads ~220 MB from MOBI.E and can take 1-3 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| available_only | boolean | – | – |
| connector | – | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| min_power_kw | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_medicine_near ~218
One-shot answer to "I need medicine X in city Y — what do I do?" in Portugal. Runs medicine_availability(medicine) and pharmacies(city or lat/lon), and returns: the shortage status (compact), the pharmacies on duty today and the ones open now (nearest first when lat/lon are given), the help lines (Linha 1400, SNS 24, 112) and next steps. It never says a pharmacy has the medicine: stock is not public. Args: medicine: Brand name or active substance, e.g. "quetiapina", "Brufen 400". city: Municipality or town, e.g. "Lisboa". Or give lat/lon instead. lat, lon: Optional user position (sorts pharmacies by distance). limit: Max pharmacies returned (default 8).
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| medicine | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fire_risk ~103
Wildfire danger (RCM, risco de incêndio rural) for a municipality, today or tomorrow. Args: municipality: concelho name, e.g. "Sintra", "Monchique". day: 0 = today, 1 = tomorrow. Scale: 1 reduzido, 2 moderado, 3 elevado, 4 muito elevado, 5 máximo.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | – |
| municipality | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fuel_prices ~462
Cheapest fuel stations in Portugal for one fuel type, cheapest first (official DGEG prices). Use for "where is diesel/petrol/LPG cheapest in Lisboa / near me / in Braga?". Give an area as a district, a municipality, or a point (lat + lon, with radius_km); with no area it searches all of Portugal. Names are case- and accent-insensitive ("evora" works). Args: fuel_type: A DGEG fuel name or id, e.g. "Gasóleo simples" (regular diesel, 2101), "Gasolina simples 95" (regular 95 petrol, 3201), "Gasolina 98", "GPL Auto" (LPG), or plain words: "diesel", "petrol", "95", "98", "lpg", "cng". See fuel_types() for the full list. district: Portuguese district, e.g. "Lisboa", "Porto", "Faro". municipality: Municipality (concelho), e.g. "Sintra", "Vila Nova de Gaia". Overrides district. lat, lon: A point (WGS84). Results get distance_km and are limited to radius_km. radius_km: Search radius around lat/lon (default 10). brand: Only this brand (substring match), e.g. "Galp", "Prio", "Intermarché". limit: How many stations to return (default 10, max 50). Each station: price_eur (per litre, or per kg/m3 for gas), brand, name, address, municipality, distance_km (with lat/lon), coordinates and last_update (the station's last price update). Also returns how many stations matched and the min/median/max price. Always mention the source (DGEG) and the last_update when quoting prices.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| district | – | – | – |
| fuel_type | string | yes | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| municipality | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
fuel_station_detail ~66
Full details of one fuel station: every fuel it sells with price and last update, opening hours, services (car wash, shop, tyre air...) and payment methods. Use after fuel_prices, with a station `id` from its results.
| Name | Type | Req | Description |
|---|---|---|---|
| station_id | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fuel_types ~62
List DGEG fuel types (id, name, unit) and the districts accepted by fuel_prices. Only needed when unsure which fuel name to pass; fuel_prices also understands "diesel", "petrol", "95", "98", "lpg".
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
ine_indicator ~177
Values of an INE indicator, latest periods first. Args: varcd: 7-digit indicator code from ine_search, e.g. "0008074". place: geography name to keep, e.g. "Portugal", "Lisboa", "Norte", "Porto". Default: "Portugal" when present, otherwise all geographies. periods: how many of the latest reference periods to return (1-24). category: keep only rows whose category labels contain this text (e.g. "Total", "Mulheres"). lang: "PT" or "EN". limit: max rows.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| lang | string | – | – |
| limit | integer | – | – |
| periods | integer | – | – |
| place | – | – | – |
| varcd | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ine_search ~120
Find INE indicators by keyword (e.g. "inflação", "desemprego", "população", "rendas", "turismo"). Searches INE's catalogue of key indicators. Returns varcd codes to pass to ine_indicator. Any other INE indicator can be read with ine_indicator if you know its code (from www.ine.pt). Args: lang: "PT" (more complete wording) or "EN".
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lisbon_events ~184
What's on in Lisbon: the city's official cultural agenda (exhibitions, concerts, theatre, dance, cinema, guided visits, kids, festivals). Args: day: ISO date, e.g. "2026-11-14". Default today. until: ISO date to look at a range from `day` (max 31 days). query: words in the title, venue or description, e.g. "fado", "Gulbenkian", "jazz". category: e.g. "música", "teatro", "exposições", "visitas guiadas", "crianças". free_only: only free events.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| day | – | – | – |
| free_only | boolean | – | – |
| limit | integer | – | – |
| query | – | – | – |
| until | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lisbon_metro_status ~66
Is the Lisbon Metro running normally right now? Status of the four lines (Amarela, Azul, Verde, Vermelha) as Metropolitano de Lisboa publishes it, with the disruption text if any. For timetables use transit_departures with operator "metro".
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
lisbon_recycling ~147
The nearest recycling points in Lisbon of a given kind. Args: lat, lon: where you are. kind: "ecoponto" (paper, plastic, glass), "vidrao" (glass), "papel", "oleo" (used cooking oil), "reee" (small electronics), "alimentar" (food waste), "ecoilha", "ecocentro" (large items). radius_m: search radius in metres (max 3000).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| radius_m | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lisbon_street_works ~184
Street works and public-space occupations in Lisbon: what is (or will be) blocking a street. Two official sources: licensed temporary occupations of public space (filming, events, scaffolding, containers...) and the city's road and pavement works in progress or planned. Args: parish: freguesia, e.g. "Arroios", "Santa Maria Maior", "Belém". street: part of a street name (works only), e.g. "Avenida da República". lat, lon: within radius_m metres of a point (max 3000). day: ISO date the occupation must cover; default today.
| Name | Type | Req | Description |
|---|---|---|---|
| day | – | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| parish | – | – | – |
| radius_m | integer | – | – |
| street | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
local_accommodation ~218
Look up the national register of local accommodation (Alojamento Local, RNAL). Answers "is this flat/guesthouse registered?" and "how many AL are on my street?". Args: registration: the RNAL number, e.g. "12345/AL" or "12345". name: part of the registered name, e.g. "InSuites". address: part of the street address, e.g. "Rua de Santa Catarina". postal_code: "1200-290", or "1200" for the whole area. municipality: e.g. "Lisboa", "Porto", "Albufeira". lat, lon: registered accommodation within radius_m metres (max 2000) of a point.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| municipality | – | – | – |
| name | – | – | – |
| postal_code | – | – | – |
| radius_m | integer | – | – |
| registration | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
medicine_availability ~278
Is a medicine in shortage in Portugal? Checks Infarmed's published availability information. Use when someone can't find a medicine, or asks whether X is in shortage ("rutura", "esgotado", "falta"). Searches by brand or active substance (Portuguese names work best, e.g. "quetiapina", "Ozempic", "ácido acetilsalicílico"; dose and form narrow it, e.g. "quetiapina 300 mg libertação prolongada"). Checks, all from www.infarmed.pt (latest versions are found automatically): - shortages Infarmed is actively monitoring (with its circulars and advice); - the monthly list of medicines whose export is temporarily suspended because of shortage / supply risk in Portugal; - the quarterly prior-notification list (LNP) of medicines with availability concerns. status is one or more of: monitored_shortage, export_suspended, prior_notification, no_issue_in_published_lists. "No issue" does not prove the medicine is available: Infarmed's full shortage search is not queried (see not_checked). Args: medicine: Brand name or active substance, optionally with strength/form. limit: Max rows returned per list (default 15).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| medicine | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
medicine_help ~74
Verified help lines in Portugal for medicine problems: 112, SNS 24, Linha 1400, Infarmed. Use when someone can't find a medicine, needs urgent advice, or asks who to call. Each line has its number, what it is for, hours where published, and the page it was checked on.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
municipality ~42
A municipality (concelho): district, INE code, area, parishes, 2021 census, town-hall contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
notable_trees ~112
Classified trees of public interest (arvoredo de interesse público, ICNF): species, size, age. Args: municipality: list a municipality's trees (e.g. "Sintra"), or near / lat / lon: the trees around a place, closest first, within radius_km (max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| municipality | – | – | – |
| near | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
open_data_dataset ~35
Details and downloadable files of one dados.gov.pt dataset (id or slug from open_data_search).
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
open_data_preview ~77
First rows of a CSV or JSON file hosted on dados.gov.pt (reads at most 512 KB). Args: url: a resource url from open_data_dataset (must be on dados.gov.pt). rows: how many rows to return (1-100).
| Name | Type | Req | Description |
|---|---|---|---|
| rows | integer | – | – |
| url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
open_data_search ~137
Search the datasets of Portugal's national open-data portal (dados.gov.pt). Args: query: e.g. "acidentes rodoviários", "escolas", "qualidade do ar", "alojamento local". organization: optional publisher to filter by, e.g. "INE", "Lisboa" or "Câmara Municipal de Cascais" (a town name finds its town hall's datasets: Lisboa, Porto, Cascais, Oeiras...). limit: max results (1-50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| organization | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
parliament_deputies ~139
Members of Parliament (deputados): party, constituency (círculo), status. Seats per party included. Args: name: part of the parliamentary or full name. party: group acronym, e.g. "PSD", "PS", "CH". constituency: e.g. "Lisboa", "Porto", "Açores", "Europa". include_inactive: also list deputies who left or were replaced. Default false.
| Name | Type | Req | Description |
|---|---|---|---|
| constituency | – | – | – |
| include_inactive | boolean | – | – |
| legislature | – | – | – |
| limit | integer | – | – |
| name | – | – | – |
| party | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
parliament_initiative ~77
Full record of one initiative: every phase with dates, every vote with each group's position, text link. Args: initiative_id: the `id` from parliament_search (e.g. "356403"), or a reference like "Proposta de Lei 3".
| Name | Type | Req | Description |
|---|---|---|---|
| initiative_id | string | yes | – |
| legislature | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
parliament_search ~219
Search initiatives in the Portuguese Parliament: bills, resolutions, inquiries. Args: query: words in the title, e.g. "habitação", "IRS", "imigração". type: e.g. "Projeto de Lei", "Proposta de Lei" (Government bills), "Projeto de Resolução". author: party acronym ("PS", "PSD", "CH", "IL", "L", "PCP", "BE", "CDS-PP", "PAN", "JPP") or "Governo". result: "aprovado" or "rejeitado" — keeps initiatives whose latest vote had this result. since: "YYYY-MM-DD" — submitted on or after this date. legislature: Roman numeral, default the current one (XVII). limit: max results, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| author | – | – | – |
| legislature | – | – | – |
| limit | integer | – | – |
| query | – | – | – |
| result | – | – | – |
| since | – | – | – |
| type | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
parliament_votes ~121
Recent plenary votes, with how each parliamentary group voted. Args: party: show this group's position on each vote (e.g. "PS", "CH"); only votes where it is recorded. query: words in the initiative title. since: "YYYY-MM-DD". result: "aprovado" or "rejeitado". limit: max votes, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| legislature | – | – | – |
| limit | integer | – | – |
| party | – | – | – |
| query | – | – | – |
| result | – | – | – |
| since | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pharmacies ~334
Pharmacies in a Portuguese municipality, with which ones are on duty today and open now. Use for "farmácia de serviço em X", "pharmacy open now near me", or to list pharmacies to call. Each pharmacy has name, address, phone, coordinates, today's hours, open_now, on_duty (official duty roster for the duty day 09:00-09:00) and the duty type (e.g. "Permanente - Aberta 24h"). Results are sorted: on duty first, then open now, then distance (when lat/lon are given). Stock is not public: never say a pharmacy has a medicine. Args: city: Municipality or town/parish, e.g. "Lisboa", "Porto", "Cascais", "Alvalade, Lisboa" (add ", <municipality>" to disambiguate a town). lat, lon: Optional user position: adds distance_km and allows radius_km. With no city, the municipality is found from the coordinate. radius_km: Keep only pharmacies within this distance of lat/lon. on_duty_only: Only pharmacies on the duty roster today. open_now_only: Only pharmacies open right now. limit: Max pharmacies returned (default 20, max 100).
| Name | Type | Req | Description |
|---|---|---|---|
| city | – | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| on_duty_only | boolean | – | – |
| open_now_only | boolean | – | – |
| radius_km | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
porto_road_closures ~204
Streets in Porto with traffic or parking restrictions active on a day (default today). Args: near: a street name ("Rua de Santa Catarina", matches part of it) or a Porto postal code ("4000-457"); or pass lat/lon. radius_km: around a postal code or point (default 0.5, max 5). day: "YYYY-MM-DD" (default today); planned restrictions are known weeks ahead. kind: "all", "planned" (works, events, loading, scaffolding) or "unplanned" (accidents, burst pipes, fallen trees...). With no place, returns a city summary by reason plus the restrictions on the main streets.
| Name | Type | Req | Description |
|---|---|---|---|
| day | – | – | – |
| kind | string | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| near | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
porto_sensors ~142
Latest readings of Porto's street sensors: air quality, noise and weather. Args: kind: "air" (PM2.5, PM10, NO2, O3, CO in µg/m³), "noise" (LAeq in dB(A)), "weather" (temperature, humidity, rain, wind) or "all". near: a Porto postal code, or pass lat/lon, to sort sensors by distance. Only readings from the last 3 hours are returned; sensors that stopped reporting are counted.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| lat | – | – | – |
| lon | – | – | – |
| near | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
post_offices ~149
CTT post offices, postal agents and post boxes near a place, closest first (ANACOM register). Args: near: a postal code or municipality; or pass lat/lon. kind: "stations" (post offices, with hours and services), "agents" (postos de correios in shops and parish councils), "boxes" (post boxes, with last collection times) or "all". radius_km: search radius (default 1, max 10).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lon | – | – | – |
| near | – | – | – |
| radius_km | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
postal_code ~54
Look up a Portuguese postal code (código postal, 'XXXX-XXX' or 'XXXX'). Returns district, municipality, locality and the streets the code covers, plus a central point.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
power_cuts ~145
Planned power cuts (E-REDES maintenance works) for a postal code, municipality or parish. Args: postal_code: "2795-082" for that street, or "2795" for the whole postal area. municipality: e.g. "Sintra", "Vila Nova de Gaia". parish: e.g. "Algés" (matches part of the parish name). days: how far ahead to look (max 60). With nothing given, returns a national summary by municipality.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
| municipality | – | – | – |
| parish | – | – | – |
| postal_code | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
protected_areas ~130
Is this place in a protected area or Natura 2000 site? (mainland Portugal, ICNF) Args: near: a postal code or municipality (its centre is used); for a precise answer pass lat/lon. Checks the National Network of Protected Areas (natural parks, reserves, protected landscapes), Natura 2000 (SIC/ZEC for habitats, ZPE for birds), Ramsar wetlands and biosphere reserves, and returns each designation that covers the point, with its classifying act and area.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | – | – | – |
| lon | – | – | – |
| near | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
public_contracts ~211
Search Portuguese public contracts (Portal BASE) for one year. Args: query: words in the contract object, e.g. "software", "limpeza", "ambulâncias". buyer: public body name or 9-digit NIF, e.g. "Município de Lisboa", "SPMS". supplier: company name or NIF. procedure: e.g. "Ajuste Direto", "Concurso público", "Consulta Prévia". min_value, max_value: contract price range in euros. year: contract-file year (default: this year; 2012 onwards). sort: "value" (largest first) or "date" (newest first). limit: max rows.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | – | – | – |
| limit | integer | – | – |
| max_value | – | – | – |
| min_value | – | – | – |
| procedure | – | – | – |
| query | – | – | – |
| sort | string | – | – |
| supplier | – | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
public_contracts_summary ~111
Totals for one buyer or supplier in a year: number of contracts, total value, by procedure, top partners. Args: entity: name or 9-digit NIF of a public body or a company. role: "buyer", "supplier" or "any". year: default this year. top: how many top counterparties to list.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| role | string | – | – |
| top | integer | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
public_holidays ~125
Portugal's public holidays for a year (default: this year), with weekday. Always lists the national holidays. Pass `municipality` (a concelho, e.g. "Braga", "Lisboa", "Funchal") to add its own municipal holiday and, in the Azores or Madeira, the regional ones: that answers "is tomorrow a holiday in Braga?". Carnival is listed as optional: it is usually a day off by government decision, not by law.
| Name | Type | Req | Description |
|---|---|---|---|
| municipality | – | – | – |
| upcoming_only | boolean | – | – |
| 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.